Oman E-Invoicing FAQs: All You Need to Know About Fawtara

Oman's e-invoicing mandate (Fawtara) by the Oman Tax Authority (OTA), is reshaping how VAT-registered businesses issue, exchange, and report invoices. Whether you are a CFO mapping out your compliance roadmap, an IT head evaluating integration options, or a finance controller trying to understand what changes on the ground, the questions are largely the same. This guide compiles the most important FAQs on Oman e-invoicing, drawn directly from OTA's published guidance, so you have one reliable reference.

Key Takeaways

• Fawtara uses a 5-corner model, where invoices flow through Accredited Service Providers (ASPs) before reaching the buyer and the OTA simultaneously.
• The rollout is phased across four groups, starting with approximately 150 large VAT-registered companies in August 2026 as phase 1, and to all VAT-registered taxpayers by August 2027 as phase 2.
• B2B e-invoices must be submitted in real time; B2C timelines are still under OTA review and will be announced separately.
• Archiving obligations under Oman VAT law require records to be kept for a minimum of 10 years (15 years for real estate), and records must be accessible from within the Sultanate.

Generic Oman e-Invoicing FAQs

1. What is e-invoicing under Oman's Fawtara system?

E-invoicing, under the Fawtara initiative, means issuing invoices electronically in a standardised digital format that is transmitted automatically between the seller, the buyer, and the Oman Tax Authority (for validation). It replaces paper invoices and static PDF documents with structured, machine-readable data that travels through a certified network in real time.

2. What is the main objective of the Fawtara mandate?

OTA has stated three primary objectives: improving business transaction efficiency, ensuring transparency and tax compliance, and preventing fraudulent invoices. For businesses, the practical benefits include reduced operating costs, simplified auditing, improved data accuracy, integration with ERP and accounting systems, secure archiving, and real-time reporting for better decision-making.

3. What is the difference between a paper invoice and a Fawtara e-invoice?

Paper invoices are issued manually and require physical signatures and stamps. A Fawtara e-invoice is issued digitally, is electronically certified, and carries a unique verification code. Critically, it is issued and sent to the buyer and the OTA instantly, stored electronically, and available for instant verification and reporting.

4. Does e-invoicing apply to out-of-scope supplies?

Issuing e-invoices will not be mandatory for out-of-scope supplies. However, OTA recommends awaiting further clarification from the legislation to confirm this position definitively.

5. How does a Fawtara e-invoice get issued?

Invoices are issued through an electronic operating model that links taxpayers, service providers, the OTA system, and recipients. The flow works as follows:

• Corner 1: The supplier generates the invoice in their system.
• Corner 2: The supplier's accredited service provider validates and transmits it.
• Corner 3: The buyer's accredited service provider receives and processes it.
• Corner 4: The buyer receives the validated invoice.
• Corner 5: The OTA system receives the tax data simultaneously.

Acknowledgements are sent back at each stage to confirm delivery and validation.

Timeline and Deadlines

1. What are the implementation phases and who is covered?

OTA has structured the rollout across four phases:

2. How were Phase 1 companies selected?

Selection was based on criteria including revenue size, annual invoice volume, and technical readiness. If you are unsure whether your company falls within Phase 1, OTA has published an e-Invoicing Rollout Checking Tool on the TMS portal. You enter your full VATIN (beginning with OM) and the tool returns your applicable rollout period.

3. Will SMEs be included in the mandate?

Yes. SMEs are covered under Phase 3, which begins in August 2027. This phase captures all remaining VAT-registered taxpayers not already covered by Phases 1 and 2.

4. Can a company not yet in scope adopt Fawtara voluntarily?

Yes. Optional early adoption is permitted, and OTA has confirmed that necessary support will be provided to companies that choose to onboard ahead of their mandatory phase. Importantly, e-invoicing penalties will not apply for violations relating to invoices issued voluntarily by persons not yet required to implement on a mandatory basis.

Formats of e-Invoicing

1. What invoice types are supported under Fawtara?

The OTA data dictionary and business rules define multiple invoice types, including: 

• Standard Tax Invoice
• Standard Credit Note
• Simplified Tax Invoice (B2C)
• Simplified Credit Note
• Simplified Debit Note
• Self-Billed Invoice
• Self-Billed Credit Note
• Prepayment Invoice
• Simplified Prepayment Invoice
• Debit Note
• Export Invoice
• Reverse Charge Invoice
• Zero-Rated Invoice
• Exempt Invoice
• Out-of-Scope Invoice
• B2C Simplified Invoice

Each type has its own set of mandatory, conditional, and optional fields as defined in the OTA Oman E-Invoicing Data Dictionary.

2. Is a QR code required on e-invoices?

Currently, a QR code is expected to be mandatory only for simplified (B2C) invoices. The specific details of the QR code process, including what information it must contain and where it leads, is yet to be released by OTA. 

3. What happens if an invoice is sent to the wrong buyer?

Issue a credit note to the incorrect buyer, then issue a new invoice to the correct buyer. The invoice will not be automatically corrected within the network; the correction must follow this two-step process.

4. How are credit and debit notes handled?

Where the invoice type code is a credit note (381) or debit note (383 or 261), a credit or debit note reason code (BTOM-032) must be provided. This is a mandatory field under Oman-specific business rule IBR-023-OM.

Transmission Channels

1. How does the 5-corner model work for transmission?

The Fawtara network operates on a 5-corner model, an internationally recognised structure for secure, standardised invoice exchange. Service providers at Corners 2 and 3 are responsible for validating and exchanging e-invoices between taxpayers (Corners 1 and 4), while also reporting specific tax data to OTA's system at Corner 5.

All invoice attachments related to a single invoice must be sent through the same channel; it is not permitted to submit attachments through a separate channel such as email.

2. What is the submission timeframe for B2B and B2C invoices?

For B2B invoices, submission is required in real time. For B2C invoices, there is no stipulated timeframe yet; OTA has confirmed this is still under discussion and the decision will be announced separately.

3. Can a company act as its own service provider?

Yes. Any company that meets the service provider criteria and passes OTA's prescribed tests can be accredited and subsequently serve as its own service provider.

4. What are the requirements to become an accredited service provider (ASP)?

OTA has published formal accreditation criteria. Key requirements include:

• Commercial registration in mainland Oman, with the relevant activity listed.
• Paid-up capital of at least OMR 6,000, evidenced by the latest audited financial statements.
• Operational history of at least 1 year (for Riyada card holders) or at least 2 years (all other cases).
• Declaration of no bankruptcy, insolvency, or criminal proceedings, notarised by the Omani court or OCCI.
• No active tax debt collection process (verified by OTA via TMS records).
• Technical and security requirements, including: 
  • ISO/IEC 27001 certification
  • Multi-factor authentication (MFA)
  • Encryption at rest and in transit
  • A documented security monitoring programme (SOC/SIEM)

5. What is the VAT group rule for e-invoicing?

All companies under the same VAT group, sharing one VAT number, must follow e-invoicing procedures and must use a single, shared service provider. Further details for VAT groups will be provided by OTA in due course.

Archiving

1. How long must e-invoices be retained?

Under Oman VAT law, all taxpayers are required to keep VAT records, including invoices, for a minimum of 10 years after each tax period. For invoices and records relating to real estate and property, the minimum retention period is 15 years from the date of purchase.

2. Where must records be stored?

Records must be maintained inside the Sultanate of Oman. They may be physical documents or stored electronically, provided the conditions specified in the VAT Regulations are met, and must be made available to the Tax Authority on request. This applies equally to non-resident taxpayers; in their case, the designated tax representative is responsible for records maintenance. Companies that centralise record keeping outside Oman must maintain a terminal inside the Sultanate where their Oman-related VAT records are accessible.

3. Can records be provided in English?

Taxpayers are required to be able to provide any data, records, and documents related to VAT in the Arabic language if requested by the Tax Authority. Failure to keep or produce the required records may result in a penalty.

E-Reporting

1. What tax data is reported to OTA through the Fawtara network?

Service providers at Corner 2 are responsible for reporting specific tax data to OTA's system at Corner 5 as part of the invoice exchange process. This happens simultaneously with the delivery of the invoice to the buyer, ensuring OTA has real-time visibility of transaction data.

2. Who is responsible if a reported invoice is non-compliant?

Compliance responsibility rests ultimately with the taxpayer. However, OTA will monitor the performance of service providers and take necessary actions if compliance requirements are not met. The taxpayer cannot transfer their compliance obligation to the ASP.

3. How are imports and RCM transactions handled?

For imports, businesses report the bayan (customs declaration) number. Self-billed invoices must be raised for imports of both goods and services. For reverse charge mechanism (RCM) transactions, self-billed e-invoices must be issued; a specific transaction type for RCM exists within the OTA data dictionary.

Data Dictionary

1. What is the Oman E-Invoicing Data Dictionary?

The OTA has published an Oman E-Invoicing Data Dictionary that defines all mandatory, conditional, and optional fields for each invoice type. It provides the mapping guidance needed for ERP and billing system integration, including field names, data types, validation rules, and business rules (schematron rules).

The current version shared is a draft for consultation with Phase 1 taxpayers and prospective service providers. OTA will release a final, official version after incorporating feedback from its consultation sessions.

2. Are mandatory fields fully defined?

Yes. Mandatory, optional, and conditional requirements are defined in the Data Dictionary and Business Rules. The current version is a draft for consultation; the final version will be released by OTA after the consultation process concludes.

3. What is the difference between a UUID and an Invoice Hash?

Both a UUID and an invoice hash can be considered unique invoice identifiers, but they serve different purposes, including during audit trails. OTA has confirmed that additional guidance on both identifiers and the differences between them will be shared shortly.

Additional FAQs

1. What are the benefits of Fawtara for businesses specifically?

OTA has outlined the following direct benefits for companies: 

• Reduced operating costs
• Simplified auditing
• Improved data accuracy
• Inventory management
• Reduced errors
• Integration with ERP and accounting systems
• Secure archiving 
• real-time reporting for better decision-making

For the government, Fawtara provides real-time access to transaction data, better compliance monitoring, and improved fraud detection.

2. What are the obligations for companies under Fawtara?

Companies subject to the mandate must: issue invoices electronically using OTA-approved formats; use a certified, OTA-accredited service provider or a compatible ERP solution; and ensure timely reporting of invoices to OTA.

3. Will OTA provide mapping guidance for ERP integration?

Yes. The shared draft e-invoicing data dictionary and business rules provide the necessary mapping guides for ERPs and other billing systems. The final version will be released after OTA's consultation sessions with Phase 1 taxpayers and prospective service providers.

4. What support does OTA provide to taxpayers?

OTA has published FAQs, service provider criteria, a rollout checking tool, and a draft data dictionary on the TMS portal. For further clarification, OTA directs taxpayers to the Fawtara Support Team via the portal. Voluntary adopters are also eligible for OTA support.

Fawtara is not a distant compliance exercise; for the ~150 large taxpayers in Phase 1, August 2026 is the live date. For everyone else on the VAT register, the clock is running toward August 2027. The questions answered here cover the mandate's scope, the 5-corner transmission model, invoice formats, archiving obligations, and the data dictionary, all drawn from OTA's published guidance.

The practical next step is to check your rollout phase using OTA's VATIN lookup tool, assess your ERP's readiness against the draft data dictionary, and engage an OTA-accredited service provider early enough to complete integration and testing before your phase goes live.

If you need help navigating Fawtara compliance, from ERP integration to ASP selection and VAT return reconciliation, ClearTax Oman's team is ready to support you. Fill in the form below and a specialist will be in touch.