Oman e-invoicing: Fawtara is now law — April and October 2027.
Oman's Fawtara system combines Peppol's five-corner exchange model with clearance by the Oman Tax Authority — structured XML invoices, exchanged through accredited service providers, with the OTA in the loop. Tax Authority Decision 189/2026 (Official Gazette 1660, 9 August 2026) makes it mandatory from 1 April 2027 for businesses with annual supplies above OMR 5 million and from 1 October 2027 for every other VAT-registered business; a voluntary pilot of 100 large companies runs from end-August 2026. This guide covers the model, the timeline, and what to do before your date.
Updated and re-verified — 18 August 2026
Earlier versions of this page gave the rollout as February 2027 (all large taxpayers) and August 2027 (all VAT-registered businesses), taken from the OTA’s FAQ. On 9 August 2026 the Tax Authority put the dates in law: Decision No. 189/2026, amending the VAT Executive Regulations, published in Official Gazette No. 1660 — 1 April 2027 where annual supplies exceed OMR 5,000,000 and 1 October 2027 for everyone else. The 100-company pilot proceeds voluntarily from end-August 2026. Every date on this page has been re-verified against the Decision text; the FAQ schedule it replaces was guidance, never law.
Two legal dates, six months apart.
Oman's rollout is compressed: from the first legal date to full coverage of every VAT-registered business takes six months. Businesses in the second wave inherit the benefit of a tested system — and the disadvantage of less time to prepare once the pattern is set.
- June 2026 — preparation window Accreditation standards for service providers are published and the pilot cohort prepares. The window in which integration and master-data work is still unhurried.
- 9 August 2026 — the dates become law Tax Authority Decision No. 189/2026, amending the VAT Executive Regulations, is published in Official Gazette No. 1660: electronic tax invoices in an approved, secure format become a statutory obligation (Art. 143), and the Authority will announce the licensed service providers (Art. 143 bis).
- End-August 2026 — voluntary pilot 100 large companies selected by the OTA begin issuing through Fawtara ahead of any legal duty.
- 1 April 2027 — annual supplies above OMR 5 million The first legal date. Every taxable person whose annual supplies exceed OMR 5,000,000 must issue electronic tax invoices.
- 1 October 2027 — all other VAT-registered businesses Every remaining VAT-registered business in Oman is in scope, completing the rollout six months after the first legal date. Limited, time-bound exemptions exist only on application to the Authority.
Who must do what, when.
Fawtara is a hybrid: Peppol's five-corner architecture carries the invoice between service providers, and the Oman Tax Authority clears it. That puts Oman in a distinctive position in the GCC — it exchanges like the UAE and clears like Saudi Arabia, in one system.
Annual supplies above OMR 5 million: legally in scope from 1 April 2027 (Decision 189/2026). If you are among the 100 companies in the voluntary pilot from end-August 2026, you will know; the practical question is whether your ERP can produce compliant structured XML and whether your service-provider arrangements are in place with time to test against the OTA's clearance flow before the date.
All other VAT-registered businesses: 1 October 2027. Limited exemptions exist on application (Art. 143 bis 2). The OTA has published accreditation standards for service providers, so the provider market is forming now — which means the second wave can evaluate providers on evidence from the pilot and the first wave rather than on promises.
For businesses that also operate in Saudi Arabia or the UAE, the hybrid model is the planning point: master data and integration architecture built properly for one GCC mandate carries most of the weight for the others, but the clearance step and the exchange step each have their own failure modes and need their own testing.
- Exchange: Peppol five-corner — invoices move between sender and receiver through accredited service providers
- Clearance: the OTA validates the invoice as part of the flow
- Format: structured XML
- Providers: OTA accreditation standards published; the provider market is forming now
Fawtara is not ZATCA, and it is not PINT AE.
Groups that already run Saudi or UAE compliance reach for the design they have. It does not transfer. Oman uses PINT OM — published by OpenPeppol at version 1.0.0 on 23 June 2026 — alongside an Oman Tax Data Document, on a five-corner model with Tax Authority clearance. Three jurisdictions, three designs, one set of master data.
The difference that catches people first is B2C. In the UAE, business-to-consumer is explicitly out of scope until a further decision. In Oman it is not deferred at all — the OTA states B2C is implemented at the same time as B2B and B2G. What differs is the submission window: B2B is real time, B2C is within 24 hours.
The second difference is the QR code. UAE invoices are XML and carry none. Oman requires a QR code on B2C transactions, full or simplified. If you are porting a UAE design into Oman, that is a gap you will find late.
Two smaller rules with real operational weight: consolidated invoices are not permitted for B2C, and after implementation paper survives only for B2C alongside the prescribed electronic format. Exports leave the network on a C1→C2→C5 flow. The OTA has also stated there are no industry exceptions.
- Oman: PINT OM + Oman Tax Data Document · clearance · B2C in scope from the start, 24-hour window · QR on B2C
- Saudi: UBL 2.1 KSA profile · clearance for B2B, reporting for B2C · QR with nine fields in Phase 2 · invoice hash chain
- UAE: PINT AE · five-corner exchange through Accredited Service Providers · B2C excluded for now · no QR code
- What is shared: your customer, item and tax master data — and almost nothing else
What the OTA has not published — and why that matters.
A great deal of Oman guidance in circulation states things the Tax Authority has never actually published. Planning against those numbers is how a programme discovers, late, that its assumptions had no source.
The pilot has no revenue threshold; the mandate does. The OTA describes pilot selection by criteria — revenue size, annual invoice volume, technical readiness, maturity, and coverage across sectors — not by a figure in rials. The legal waves are different: Decision 189/2026 splits them at OMR 5,000,000 of annual supplies. It does not say which twelve-month period is measured, so ask which document a "threshold" claim came from and whether it is talking about the pilot or the law.
No penalty amounts have been published. The OTA's position is that penalties will apply according to regulations. Anyone quoting specific rial figures is citing commentary, not the authority.
The legal basis now exists; the technical decisions follow. Decision 189/2026 amends the VAT Executive Regulations (Articles 143, 143 bis, 143 bis 1, 143 bis 2, 146 and 147). Formats, exemption periods and the provider list are left to the Authority to specify — the detail arrives alongside, not before.
There is no separate government phase in the Decision. The OTA FAQ once listed a fourth phase for government entities in "February, year to be announced"; the Decision names only the two dates above. Any source still quoting a government-phase year has supplied it themselves.
None of this is a reason to wait. It is a reason to design for change: the organisations that will cope best are the ones whose master data and integration layer do not have to be rebuilt when the regulation lands.
- You get notice. The OTA states it contacts rollout participants at least six months before their onboarding date
- You can start early. Optional early adoption is permitted, with support provided — the cheapest place in the programme to be wrong
- Providers are not on a clock. The OTA states there is no deadline for service providers to apply for accreditation
- Testing exists. Conformance runs through the Peppol Testbed, including a PINT OM test suite for the C2–C3 leg
One caution we would rather state than hide: the OTA's own programme page and its FAQ still show the older phase lists (four undated phases on the programme page; four dated phases ending with government entities on the FAQ) and neither had been updated for Decision 189/2026 when we last checked. Where they differ from the Decision, the Decision governs — it is the law; the pages are guidance. Dates on this page are verified against the Decision text (Official Gazette No. 1660, 9 August 2026) and the OTA e-invoicing FAQ. Last checked 18 August 2026.
Six things to do before your date.
- 01Place yourself in the rollout. Annual supplies above OMR 5 million: 1 April 2027. Everyone else VAT-registered: 1 October 2027 (Decision 189/2026). Your date sets your runway — confirm which side of the threshold you are on rather than assume it.
- 02Assess your ERP's structured-XML capability now. Fawtara requires structured XML invoices. Establish what your current system can emit, what needs mapping, and what needs middleware — before the provider market gets busy.
- 03Watch the accredited provider list form. The OTA has published accreditation standards. Evaluate providers on exit terms, data-export rights, and Peppol track record — not on brochure features.
- 04Clean counterparty master data. VAT numbers, legal names, addresses, and tax codes drive validation outcomes in every clearance system. The work is identical whether you do it calmly now or urgently later.
- 05Treat B2G as a first-class flow. Government buyers may expect structured invoices through Fawtara ahead of your own legal date, especially where they are in the pilot. If you supply government entities, your effective deadline may be the earliest one regardless of your own size.
- 06Coordinate with your other GCC obligations. If KSA Wave 24 or the UAE's 30 October 2026 ASP deadline also applies to your group, sequence the three projects on one shared data foundation rather than running them in isolation.
Peppol infrastructure, local delivery.
Fawtara is built on the network ClayDesk already operates on: our certified Peppol Access Point, GoRoute, runs under ID POP000991, and our technology partner network serves the Oman market for customer-facing delivery. For Omani businesses that means Peppol-grade infrastructure — AS4 exchange, structured-XML validation, audit trails — combined with local engagement.
The pre-wave work we deliver now: ERP capability assessment, structured-XML field mapping, master-data remediation, and clearance-flow test planning — the same sequence we run across GCC mandates, adapted to the OTA's requirements. Delivery model, timelines, and engagement tiers are on the e-invoicing practice page.
Asked on most Oman discovery calls.
Is Fawtara a clearance system or a Peppol exchange system?
Both. Invoices travel the Peppol five-corner route between accredited service providers, and the Oman Tax Authority clears them as part of the flow. Practically, that means you need both halves working: a compliant exchange connection and a clean pass through OTA validation.
We are not one of the largest taxpayers. When do we need to act?
Tax Authority Decision 189/2026 (Official Gazette 1660, 9 August 2026) sets two legal dates: 1 April 2027 if your annual supplies exceed OMR 5,000,000, and 1 October 2027 if they do not. The whole market is in scope within six months of the first legal date — a compressed schedule by regional standards. ERP assessment and master-data work done in 2026 turns your eventual deadline into an administrative event rather than a crisis.
We sell to government entities. Does that change our timeline?
It can. The legal dates are set by annual supplies, not by customer type — 1 April 2027 above OMR 5,000,000, 1 October 2027 otherwise — but government buyers, especially those in the voluntary pilot from end-August 2026, may expect structured invoices through Fawtara earlier. Your practical readiness date may be set by your customers rather than by your own wave. Check with your government counterparties early.
Who can act as a service provider in Oman?
The OTA has published accreditation standards for service providers, and the market is forming against them. When evaluating providers, ask about Peppol track record, exit terms, and data-export rights — the questions that distinguish infrastructure operators from resellers.
We also operate in Saudi Arabia and the UAE. Three projects?
One foundation, three activations. KSA clears, the UAE exchanges, Oman does both — but all three consume the same validated master data and the same integration layer. Sequencing them as one programme is materially cheaper than running three unrelated projects, and Oman's hybrid model is the natural stress test of the shared foundation.
Related thinking.
Deadlines move. We will tell you when.
Short, source-checked notes when a GCC mandate actually changes — a wave announced, a specification revised, a date moved. Written by the people doing the implementations. No sequence, and you can leave in one click.
We use it to send mandate updates and nothing else. See our privacy policy.
Fawtara is coming. Which wave are you?
Tell us your taxpayer category, your ERP, and your invoice volume. We confirm your wave, your readiness gaps, and what implementation will cost — with a written fixed-fee quote within 24 hours.