Infinite IT Solutions Blog | EDI | e-Invoicing Compliance

E-Invoicing in Oman: The Complete Guide to the Fawtara Mandate

Written by Admin | Aug 27, 2026, 11:01:41 AM

E-invoicing in Oman is now a live regulatory programme. Through its national system, Fawtara, the Oman Tax Authority (OTA) is requiring VAT-registered businesses to issue, exchange and report invoices as structured electronic documents, with the first mandatory wave beginning in August 2026. This guide explains what the mandate is, who it affects, when each group has to comply, how the underlying Peppol technology works, and the concrete steps your business should take to be ready in time.

In short: Oman is rolling out mandatory e-invoicing in four phases between 2026 and 2028, using a Peppol-based five-corner model. Invoices must be issued as structured XML in the PINT OM format and routed through an OTA-accredited service provider. There are no permanent exemptions planned for VAT-registered businesses.

What is e-invoicing in Oman?

E-invoicing in Oman refers to the mandatory issuance and exchange of invoices in a structured, machine-readable electronic format that is validated and reported to the tax authority in real time. It is not the same as emailing a PDF or uploading a document to a portal. A true e-invoice under the Oman regime is a structured data file (XML) that software can read, validate and process automatically without manual re-keying.

The programme is branded Fawtara, from the Arabic word for "invoice", and is administered by the Oman Tax Authority (OTA). The national telecom operator, Omantel, is the primary technology partner responsible for building and operating the platform.

With this move, Oman becomes the third Gulf Cooperation Council (GCC) country to mandate e-invoicing, after Saudi Arabia and the United Arab Emirates. Its adoption of an internationally interoperable model signals a broader regional shift toward real-time digital tax reporting.

Suggested internal link: [What is a structured e-invoice? XML vs PDF explained]

Why is Oman introducing e-invoicing?

The OTA's stated objectives mirror those of tax authorities worldwide that have adopted continuous transaction controls. The mandate is designed to:

  • Reduce VAT fraud and invoice manipulation by giving the tax authority real-time visibility of transactions.
  • Improve tax compliance and transparency across the economy.
  • Streamline the invoicing process, cutting the manual effort, errors and reconciliation disputes associated with paper and PDF invoices.
  • Lower operating costs for businesses through automation and system-to-system exchange.
  • Align Oman with international best practice, supporting both domestic and cross-border trade through a globally recognised framework.

For businesses, the shift is significant: e-invoicing changes how invoices are created, transmitted, validated and stored, and touches ERP systems, billing software, master data and finance processes alike.

Who has to comply with the Oman e-invoicing mandate?

The mandate applies to VAT-registered businesses in Oman. Scope is being widened progressively, but the direction of travel is clear: every VAT-registered taxpayer will eventually need a compliant e-invoicing solution, regardless of size, sector or transaction volume.

Key points on scope:

  • Large taxpayers go first. An initial cohort of the largest VAT-registered companies was directly notified by the OTA and forms the pilot group.
  • SMEs are included later, but they are still in scope. No permanent size-based exemption has been announced.
  • Non-VAT-registered businesses below the registration threshold are not required to join the Fawtara network.
  • Government transactions (B2G) are brought in through a dedicated later phase.
  • Exempt supplies are currently outside the scope of the mandate, though the OTA has indicated they may be included at a later stage.
  • Voluntary early adoption is available for businesses not yet in scope, with support from the OTA.

The mandate covers B2B, B2G and (in later phases) B2C flows, making it broad in transaction coverage.

The Oman e-invoicing timeline: the four phases

The OTA has confirmed a four-phase rollout. The pilot phase launched on schedule in August 2026, and the remaining phases extend the mandate across the economy through 2027 and into 2028.

Phase Who is covered Go-live
Phase 1 The ~100 largest VAT-registered companies (pilot group, already notified) August 2026
Phase 2 All remaining large VAT-registered companies February 2027
Phase 3 All other VAT-registered taxpayers, including SMEs August 2027
Phase 4 Government institutions and entities (B2G) February, year to be announced (~2028)

Taxpayers are selected for each wave based on criteria such as revenue size, annual invoice volume and technical readiness. Businesses in later phases can watch for direct notification from the OTA, but should not wait for it to begin preparing — technical integration typically takes months.

Note: Regulatory dates can shift. Always confirm your phase and go-live date against the latest official guidance published by the Oman Tax Authority before finalising project plans.

How the Fawtara system works: the Peppol five-corner model

Oman has adopted the Peppol five-corner model, a decentralised architecture in which invoices are exchanged through accredited service providers rather than uploaded to a single government portal. The OTA became a formally recognised Peppol Authority in January 2026, cementing Peppol as the backbone of Fawtara.

A defining feature of the model is that direct ERP-to-OTA connectivity is not permitted. Both the seller and the buyer must connect through an OTA-accredited service provider that operates as a certified Peppol Access Point. As the invoice travels to the buyer, the relevant tax data is reported to the OTA's central platform in parallel.

Here is what each "corner" does:

Corner Party Role
Corner 1 Supplier Generates a structured XML invoice in PINT OM format from ERP or billing software
Corner 2 Supplier's Accredited Service Provider (ASP) Validates the invoice, converts the format if needed, and routes it to the Peppol network; also extracts and reports the tax data to the OTA
Corner 3 Peppol network Securely transmits the document between the two access points
Corner 4 Buyer's ASP → Buyer The buyer's access point receives the validated invoice and delivers it for automated processing
Corner 5 Oman Tax Authority (Fawtara) The central platform receives the tax data in real time for validation, reporting and oversight

Because the model is decentralised, there is no single bottleneck portal — but it does mean choosing the right accredited service provider is one of the most important compliance decisions your business will make.

Learn more about Peppol model

Technical requirements: formats, PINT OM and the Tax Data Document

Invoice formats

Under Fawtara, only two formats are valid:

  • XML (UBL 2.1), structured according to the PINT OM specification — this is the true, machine-readable e-invoice.
  • PDF/A-3, an archival PDF format that can embed the structured XML for human readability.

Manual invoices and ordinary PDF invoices are being phased out for in-scope transactions.

PINT OM

The technical heart of the system is PINT OM (Peppol International – Oman), the Omani adaptation of the international Peppol PINT standard, published through OpenPeppol in April 2026. PINT OM incorporates local tax requirements while remaining compatible with the global Peppol network and the European EN 16931 semantic standard. It defines the data structures, mandatory fields, validation rules and exchange processes for Omani e-invoicing across billing, self-billing and tax-reporting scenarios (for both invoices and credit notes).

The Tax Data Document (TDD) and transaction codes

The tax-reporting package introduces the Tax Data Document (TDD) — the artifact through which invoice tax data is reported to the OTA (Corner 5). Alongside it, the transaction type code is the central mechanism that drives validation in PINT OM: it tells the system which set of business rules applies to each invoice scenario. Getting these codes right is one of the more common stumbling blocks for ERP and integration teams.

Businesses with international operations will also need to configure multi-currency invoicing with exchange rates and, where applicable, dual VAT reporting.

The role of accredited service providers (ASPs)

Because direct connection to the OTA is prohibited, an OTA-accredited service provider (ASP) is a mandatory part of every compliant setup. Acting as certified Peppol Access Points, ASPs handle:

  • Secure invoice exchange — Peppol connectivity, encryption and routing.
  • Format conversion — transforming your ERP data into the mandated structured formats.
  • Fawtara API integration — connecting your systems to the OTA infrastructure.
  • Tax data reporting — extracting and submitting the TDD to the OTA in real time.
  • Data residency — ensuring archiving and hosting meet Omani data sovereignty requirements.

The Fawtara Portal is already live for service providers to apply for accreditation, and a sandbox test environment is available for integration testing. When selecting a provider, prioritise one that supports PINT OM-compliant invoice generation, Peppol network transmission and long-term archiving within a single integrated platform.

Archiving and record-keeping

Archiving responsibility sits with the taxpayer, in line with Oman's VAT legislation — not with the service provider by default. Under the Oman VAT Law:

  • Tax invoices and related records must generally be retained for 10 years.
  • A longer 15-year retention period applies to real-estate-related records.

Archived e-invoices should be stored in a tamper-evident, retrievable format (typically the structured XML, often alongside a PDF/A-3 rendering) and must satisfy data residency and local hosting rules. Confirm exactly how archiving is handled in your contract with your ASP, since responsibility for storage and the legal obligation to retain records are two different things.

Special cases: B2C, exempt supplies and timing

  • B2B invoices must be submitted in real time through the five-corner flow.
  • B2C invoices benefit from a 24-hour reporting window. Where the buyer is not connected to the Fawtara network, the seller's ASP handles the Corner 5 reporting only, and the seller can provide a human-readable copy (with a QR code / verification code) to the consumer outside the network.
  • Exempt supplies are currently outside the scope of the mandate, but may be brought in later.
  • Each compliant e-invoice carries a unique verification code, enabling instant validation and traceability.

How Oman compares to Saudi Arabia and the UAE

Oman's mandate is best understood in its GCC context:

  • Saudi Arabia was first, with its ZATCA "Fatoora" system built on a centralised clearance model, where invoices are cleared through a government platform.
  • The UAE followed with a Peppol-based decentralised (five-corner) model.
  • Oman has aligned with the decentralised Peppol approach, closer to the UAE, but retains a degree of central governance — including a single centralised SMP (Service Metadata Publisher), certification of service providers and local establishment requirements, with the Fawtara platform acting as the fifth corner.

For multinational groups operating across the Gulf, this means e-invoicing compliance is not one-size-fits-all: the underlying models, formats and reporting mechanics differ by country even where the goals converge.

Suggested internal link: [GCC e-invoicing compared: Saudi Arabia vs UAE vs Oman]

How to prepare for e-invoicing in Oman: a compliance checklist

Whether you are in Phase 1 or a later wave, the preparation work is substantial. Use this checklist to structure your readiness project:

  1. Confirm your scope and phase. Determine whether your entity or group has been notified and identify your go-live date.
  2. Appoint an OTA-accredited service provider operating as a certified Peppol Access Point. Start early — provider selection and onboarding take time.
  3. Assess your ERP and billing systems. Confirm they can generate structured XML in PINT OM format and map to the required semantic model.
  4. Map your invoice data to all mandatory PINT OM fields, and configure the correct transaction type codes for every scenario you operate.
  5. Handle multi-currency and dual VAT reporting where applicable.
  6. Set up compliant archiving for the required retention period (10 years generally; 15 years for real-estate records), meeting data residency rules.
  7. Test in the sandbox environment before go-live.
  8. Train finance and IT teams and update internal processes and invoice templates.
  9. Coordinate with trading partners to ensure counterparties are ready to send and receive e-invoices.

Risks of non-compliance

Once a business enters its rollout phase, its systems, master data, invoice templates and reporting logic need to be ready from day one. Invoices delivered outside the Peppol network will not meet the Fawtara requirements. Beyond the direct compliance exposure, businesses that delay risk integration failures, blocked invoicing and disrupted cash flow if they cannot issue valid invoices when their deadline arrives. Because there are no permanent exemptions planned, "waiting to see" is not a viable long-term strategy for any VAT-registered business.

Frequently asked questions

What is Fawtara? Fawtara is Oman's national e-invoicing system, administered by the Oman Tax Authority. It requires invoices to be issued as structured electronic documents, exchanged through accredited service providers over the Peppol network, and reported to the tax authority in real time.

When does e-invoicing become mandatory in Oman? The first mandatory phase began in August 2026 for the ~100 largest VAT-registered companies. It expands to all large taxpayers in February 2027, to all remaining VAT-registered businesses (including SMEs) in August 2027, and to government entities in a fourth phase (date to be announced, expected around 2028).

Who has to comply? All VAT-registered businesses in Oman will eventually be in scope, phased in by size. Businesses below the VAT registration threshold are not required to join.

What format must Oman e-invoices use? Structured XML (UBL 2.1) aligned to the PINT OM specification, or PDF/A-3 with embedded structured data. Ordinary PDFs and manual invoices are not compliant for in-scope transactions.

Do I need a service provider? Yes. Direct ERP-to-OTA connection is not allowed. You must use an OTA-accredited service provider that acts as a certified Peppol Access Point.

How long must e-invoices be archived? Generally 10 years, with 15 years for real-estate-related records, in line with the Oman VAT Law. Archiving responsibility rests with the taxpayer.

Is Oman using the same system as Saudi Arabia? No. Saudi Arabia uses a centralised clearance model, while Oman has adopted a decentralised Peppol five-corner model, closer to the UAE's approach but with central governance elements.

Are B2C transactions included? B2C invoices can currently be reported within a 24-hour window, and full B2C inclusion is expected to expand over time. Exempt supplies are currently outside scope.

Key takeaways

E-invoicing in Oman has moved from consultation to active rollout. The Fawtara mandate, built on the Peppol five-corner model and the PINT OM standard, applies to all VAT-registered businesses on a phased schedule that began in August 2026 and extends through 2027 and into 2028. Compliance requires structured XML invoicing, an accredited service provider, correct data mapping and validation, and long-term archiving. Because integration typically takes months and no permanent exemptions are planned, the safest approach — whatever your phase — is to start scoping your readiness project now.

 

Want to connect to Fawtara platform? Contact us!