Oman e-invoicing: Fawtara starts August 2026.
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. The first wave of around 100 of the largest VAT taxpayers, including B2G, goes live on August 2026; every VAT-registered business follows by August 2027. This guide covers the model, the timeline, and what to do before your wave.
Three waves in twelve months.
Oman's rollout is compressed: from the first wave to full coverage of every VAT-registered business takes one year. Businesses in the later waves 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 first wave is preparing for go-live. This is the window in which integration and master-data work is still unhurried.
- August 2026 — first wave Around 100 of the largest VAT taxpayers, including B2G transactions, begin issuing through Fawtara.
- February 2027 — all large taxpayers The mandate extends to all large taxpayers, six months after the first wave.
- August 2027 — all VAT-registered businesses Every VAT-registered business in Oman is in scope, completing the rollout twelve months after wave one.
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.
The largest VAT taxpayers — around 100 of them, including B2G: live from August 2026. If you are in this group, 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 large taxpayers: February 2027. All VAT-registered businesses: August 2027. The OTA has published accreditation standards for service providers, so the provider market is forming now — which means the later waves can evaluate providers on evidence from 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.
There is no revenue threshold for Phase 1. The OTA describes selection by criteria — revenue size, annual invoice volume, technical readiness, maturity, and coverage across sectors and taxpayer types — not by a published figure in rials. If a plan says "we are under the threshold", ask which document that threshold came from.
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 enabling regulation is still unissued. As of the OTA's most recent published FAQ, the e-invoicing regulation is to be released in due course. Phase 1 begins in August 2026 regardless — the detail arrives alongside, not before.
Phase 4 has no year. The OTA gives February, year to be announced, for government institutions and entities. Any source stating a specific 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 do not fully agree. The programme page lists four undated phases ending in a full rollout of all VAT-registered entities; the FAQ lists four dated phases ending with government entities. We have followed the FAQ, which is the more recent and more specific. Verified against the OTA e-invoicing FAQ and its Fawtara FAQ document updated 30 June 2026. Last checked 28 July 2026.
Six things to do before your wave.
- 01Place yourself in the rollout. Around 100 of the largest taxpayers go first on August 2026; all large taxpayers follow in February 2027; everyone VAT-registered by August 2027. Your wave sets your runway — confirm it 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 transactions are in the first wave. 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?
All large taxpayers join in February 2027, and every VAT-registered business by August 2027. The full rollout takes twelve months from the first wave — 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. B2G transactions are part of the first wave from August 2026. If government buyers expect structured invoices through Fawtara from that date, your practical readiness date may be set by your customers rather than by your own wave assignment. 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.