Oman E-Invoicing 2026: Fawtara Compliance Guide for VAT-Registered Businesses

Oman is restructuring how businesses issue, transmit, and store invoices through Fawtara, the national e-invoicing program run by the Oman Tax Authority (OTA). The program requires VAT-registered entities to generate invoices in a structured, machine-readable format rather than paper or static PDF documents, and to transmit them through a supervised digital network rather than exchanging them directly.

The legal and technical foundation for this shift was set in early 2026. On 7 January 2026, the OTA was formally approved as a Peppol Authority, making Oman the third GCC country to mandate e-invoicing after Saudi Arabia and the United Arab Emirates. In April 2026, the OTA published the PINT OM technical specification through OpenPeppol, establishing the exact data structure, validation rules, and exchange format that Omani businesses must follow.

Compliance Timeline

Fawtara is being introduced in four stages between 2026 and 2028, with taxpayer size determining when each business must comply.

1. Phase 1
2. Effective Date: August 2026
3. Businesses Covered: 144 large taxpayers already notified by the OTA (pilot group)
4. Phase 2
5. Effective Date: February 2027
6. Businesses Covered: All large VAT-registered taxpayers
7. Phase 3
8. Effective Date: August 2027
9. Businesses Covered: Remaining VAT-registered taxpayers, including SMEs
10. Phase 4
11. Effective Date: Date not yet announced
12. Businesses Covered: Government institutions and entities (B2G)

No permanent exemptions apply once a business reaches its designated phase.

Who Must Comply, and Who Currently Falls Outside the Mandate

Every VAT-registered business must eventually issue tax invoices in the OTA's structured electronic format, transmit them through an OTA-accredited service provider or a compliant in-house system, and include mandatory fields such as VATIN, invoice number, invoice date, VAT amount, and total payable. B2B invoices require real-time transmission, while B2C invoices may be issued within a 24 hour window.

Coverage narrows in a few specific situations. Businesses that fall below the VAT registration threshold are not required to join Fawtara at all. Foreign suppliers with no Omani VAT registration also sit outside the mandate; in these cases, the Omani buyer self-accounts for VAT under reverse charge rules, and no e-invoice is required from the supplier. Exempt supplies, such as certain financial services or residential leasing, are currently outside Fawtara's scope, though the OTA has signalled this could change later. Zero-rated supplies, by contrast, remain fully in scope because they are still part of the VAT system.

Self-billing arrangements are addressed directly in the PINT OM Self-Billing specification. This applies where the buyer, not the supplier, issues the invoice, most commonly for imported services subject to reverse charge. No turnover-based exemption has been set for small businesses; VAT-registered SMEs are simply brought in later, at Phase 3.

How an Invoice Moves Through the System

Fawtara runs on the Peppol five-corner model, which separates invoice creation, validation, delivery, and tax reporting into distinct steps rather than routing everything through one central government portal.

The supplier first generates the invoice as a structured XML file, built to the UBL 2.1 standard under the PINT OM specification, directly from their ERP or billing system. This file is sent via API to the supplier's OTA-accredited service provider, which checks it against structural rules (XSD), business logic, and OTA code lists before allowing it to proceed. Once validated, the invoice travels across the Peppol network to the buyer's own accredited service provider, which delivers it to the buyer in machine-readable form ready for automated processing.

At the same time this exchange is happening between the two businesses, the supplier's service provider separately submits a Tax Data Document, a compact tax report derived from the invoice, directly to the OTA. This gives the tax authority a real-time view of the transaction without waiting for a periodic VAT return. Where a B2C buyer is not connected to the Fawtara network, the seller's service provider still reports the Tax Data Document to the OTA, and the seller can hand the buyer a human-readable invoice with a QR code outside the formal network. B2B invoices must move through this entire chain in real time; B2C invoices are allowed the 24 hour window mentioned earlier.

Data Format and Validation Rules

Accepted invoice formats are XML (UBL 2.1), structured to the PINT OM specification, and PDF/A-3. JSON has not been confirmed by the OTA as an official format, and businesses should not build toward it.

Each invoice must carry buyer and seller identification, VATINs, itemised line data, VAT rate and amount, and timestamps, arranged in the schema the PINT OM specification defines. Every invoice also needs a unique identifier (UUID) and must pass Schematron validation checks before it is accepted into the network.

One point deserves particular attention because it changed mid-development. The November 2025 draft data dictionary included QR codes, digital signatures, and invoice hashes as expected fields. None of the three survived into the final PINT OM specification published in April 2026, and none are mandatory today. Businesses that built compliance logic around the earlier draft should revisit their build against the current specification rather than the November version.

The practical effect of this architecture is a move from periodic, after-the-fact tax reporting to continuous reporting at the point of transaction. For businesses with multiple entities or VAT registrations, this tends to surface data inconsistencies and VAT mismatches much earlier than an annual or quarterly review would, which gives finance teams a chance to correct them before they become audit findings.

Example: A distribution company operating three branches under separate cost centres but a single VATIN may currently reconcile VAT across branches only at return filing time. Under Fawtara, each branch's invoices are validated and reported to the OTA as they are issued, so a coding error in one branch, for instance a VAT rate applied incorrectly to a specific product line, would appear as a mismatch within days rather than being discovered months later during quarter-end reconciliation.

Retention and Archiving Obligations

Archiving is not optional or purely operational; it is a legal requirement under Article 70 of Oman's VAT Law (Royal Decree No. 121/2020), which obliges taxable persons to keep tax invoices, accounting records, and customs documents for 10 years from the end of the tax year in which the related VAT return was filed. Invoices tied to real estate transactions must be kept for 15 years.

Fawtara splits the standard 10 year period into two distinct phases: five years of in-system storage, held within the Fawtara platform or the service provider's OTA-certified environment, followed by five years in an electronic archive maintained either by the business itself or by an accredited storage provider. Throughout both phases, the archived invoice must remain traceable to the party that issued it, unchanged in content from the moment it was issued, and readable by a human reviewer, not just a machine.

Meeting this obligation is as much a systems question as a storage question. Businesses should confirm in writing whether their service provider actually manages archiving for the first five year period, and what the handover process looks like when that period ends. Archived invoices also need to stay linked to the underlying ERP transaction; storing an invoice separately from its accounting entry creates a reconciliation gap that auditors are likely to flag. Access controls and tamper-evidence, ideally aligned with ISO/IEC 27001, help demonstrate that archived data has not been altered. For businesses operating as a VAT group, the archiving obligation runs across every entity under the shared VATIN and its designated service provider, not just the parent company.

Business Impact

Beyond meeting a legal requirement, structured e-invoicing changes several operational dynamics at once. Paper handling, physical storage, and manual re-keying of invoice data are removed, which lowers processing cost per invoice. Because invoices are validated at the point of creation, transcription errors and mismatches between purchase orders, invoices, and VAT returns, a frequent trigger for audit queries, are reduced substantially.

Real-time reporting also changes the rhythm of tax compliance itself. Instead of assembling a VAT position retrospectively at return time, a business's VAT data is continuously reconciled as transactions occur, which lowers the risk of late discrepancies and the penalties that follow them. On the commercial side, automated exchange between trading partners tends to shorten accounts payable and receivable cycles, giving finance teams clearer visibility into working capital. The 10 year archive, maintained in tamper-evident structured format, also means audit requests can be answered with a searchable record rather than a manual document search.

Preparing for Fawtara

Businesses should start by testing whether their existing ERP or billing system can actually produce UBL 2.1 XML output that conforms to the PINT OM specification; the specification's data model, validation rules, and code lists are the right reference point for this gap check, not the earlier draft documents. Selecting an OTA-accredited service provider that connects cleanly to the existing accounting system, and that offers real validation and secure storage rather than just transmission, is the next practical step.

Internally, finance and IT teams need training on the new issuance, correction, and archiving workflows, along with a clear procedure for what happens when a transmission fails or the system is down. Master data, VAT numbers, contact details, VAT rates, is worth auditing now, since incorrect data is the most common cause of invoice rejection once validation is live. Archiving should be planned deliberately rather than left to whichever system happens to store the invoice by default, and legal or tax advisors should be brought in early to confirm how the phased timeline, exemptions, and penalty framework apply to the specific business.

Key-Takeaways

Fawtara marks a structural shift in how Omani businesses manage invoicing, VAT reporting, and audit readiness, not simply a change in file format. Continuous validation and real-time reporting to the OTA are designed to close the gap between when a transaction happens and when it is reported, which should reduce both fraud and the administrative burden of periodic reconciliation.

For businesses working through Phase 1 or Phase 2 readiness, the practical challenge is less about understanding the mandate and more about executing it correctly across ERP systems, service provider integration, and long-term archiving. Accqrate supports this transition by helping businesses align their invoicing and archiving infrastructure with the PINT OM specification as each phase of the Fawtara rollout takes effect.