Oman Fawtara E-Invoicing: The 5-Corner Model Explained

From four corners to five — why Oman added the tax authority

The classic Peppol network is a four-corner model: a supplier, the supplier's Access Point, the buyer's Access Point and the buyer. It moves a structured invoice from seller to buyer with no central gatekeeper. Oman's Fawtara programme keeps that exchange but adds a fifth corner — the Oman Tax Authority (OTA) — turning it into a continuous transaction control (CTC) regime.

If you want the underlying Peppol concepts first, see how e-invoicing works over Peppol. This article explains what the Oman Fawtara 5-corner model adds on top.

The five corners, applied to Oman

Corner	Role	Oman example
C1	Supplier (issues the invoice)	A Muscat manufacturer
C2	Supplier's certified Access Point	A pre-approved Fawtara service provider
C3	Buyer's certified Access Point	The buyer's AP
C4	Buyer (receives the invoice)	An Omani wholesaler or agency
C5	Oman Tax Authority (Fawtara)	Receives the Tax Data Document

Corners C1–C4 are ordinary Peppol. Corner C5 is the addition: for every in-scope transaction, a Tax Data Document (TDD) is submitted to the OTA. That single extra hop is what distinguishes a CTC model from open Peppol exchange.

PINT OM — the invoice format

Oman does not use the European BIS Billing profile directly. It uses Peppol PINT OM, the Oman specialisation of the Peppol International (PINT) model:

Invoices and credit notes: urn:peppol:pint:billing-1@om-1.
Self-billing variants with their own customisation identifiers.
Validation against the official OpenPeppol PINT OM Schematrons — nine compiled XSLTs in total.

For the identifier detail, see the PINT OM CustomizationID reference, and for how PINT differs from the European BIS baseline, Peppol vs PINT.

The Tax Data Document — corner five in detail

The TDD (urn:peppol:taxdata:om-1) is the tax-relevant projection of a PINT OM invoice that Fawtara actually ingests. It carries what the tax authority needs — parties, totals, the tax breakdown and document references — without shipping the entire commercial document.

Crucially, a well-designed provider derives the TDD deterministically from the PINT OM invoice rather than asking the customer to maintain a second data model. Our Oman TDD deep-dive walks through the structure field by field.

Clearance vs post-audit — where Oman sits

Regimes fall on a spectrum:

Post-audit (traditional Europe): invoices exchanged freely; the tax authority inspects later.
Clearance / CTC (Oman, and much of the Gulf and Latin America): the tax authority receives a tax view around the time of exchange.

Oman's Fawtara sits firmly in the CTC camp. The TDD submission gives the OTA near-real-time visibility. The commercial invoice still flows buyer-to-buyer over Peppol; the tax view flows to corner five in parallel.

Rollout cohorts and timeline

The OTA is sequencing the mandate by taxpayer cohort:

Wave 1 — approximately 144 large taxpayers across roughly 60 sectors.
Subsequent waves — mid-market and smaller taxpayers through 2026–2027.

Each cohort gets a published go-live date. For the engineering view of what onboarding and testbed conformance involve, see the Oman Fawtara readiness checklist, and for provider status, GoRoute's OTA pre-approval.

What "ready" looks like

A Fawtara-ready Omani taxpayer has:

[ ] A pre-approved Fawtara service provider (Peppol AP + SMP) contracted.
[ ] Its participant identifier (0248:OM<VATIN>) registered and discoverable.
[ ] PINT OM issuance passing the official Schematrons on error.
[ ] Deterministic TDD generation from the invoice, submitted to the OTA.
[ ] An inbound reception path for received PINT OM documents.
[ ] Audit retention meeting Omani tax-law requirements.

How GoRoute helps

GoRoute (POP000991) operates a certified Peppol Access Point and self-hosted SMP, compiles the official PINT OM Schematrons at build time, and generates the Oman TDD from the PINT OM invoice in a single workflow — one API call covers issuance, validation, Peppol transmission and CTC submission. GoRoute is pre-approved by the OTA (reference SPA-04720170). Book a demo to scope a Fawtara rollout against your cohort.

Sources: Oman Tax Authority; OpenPeppol PINT; Peppol network directory.

Frequently asked questions

What is the Oman Fawtara 5-corner model?

It is Oman's e-invoicing architecture. It extends the classic Peppol four-corner model — supplier, supplier's Access Point, buyer's Access Point, buyer — with a fifth corner, the Oman Tax Authority, which receives a Tax Data Document for each transaction as part of a continuous transaction control (CTC) regime.

What is the fifth corner in Oman e-invoicing?

The fifth corner is the Oman Tax Authority (OTA). In addition to the invoice travelling from supplier to buyer over Peppol, a Tax Data Document (TDD) derived from that invoice is submitted to the OTA's Fawtara platform for tax reporting and clearance.

What is the Oman Tax Data Document (TDD)?

The TDD (CustomizationID urn:peppol:taxdata:om-1) is the tax-relevant projection of a PINT OM invoice that the Fawtara platform ingests. It carries the fields the tax authority needs — parties, totals, tax breakdown and references — without requiring the full commercial invoice.

What invoice format does Oman use?

Oman uses Peppol PINT OM — the Oman specialisation of the Peppol International (PINT) model. Invoices and credit notes use CustomizationID urn:peppol:pint:billing-1@om-1, with self-billing variants, validated by the official OpenPeppol PINT OM Schematrons.

Is Oman e-invoicing clearance or post-audit?

Oman's model is a continuous transaction control regime with a clearance-style tax reporting step. The TDD is submitted to the OTA around the time the invoice is exchanged, giving the tax authority near-real-time visibility rather than relying purely on periodic post-audit.

When does the Oman e-invoicing mandate go live?

The Oman Tax Authority is sequencing the rollout by taxpayer cohort. The initial wave covers roughly 144 large taxpayers across many sectors, with subsequent cohorts following through 2026 and 2027. Each cohort receives a published go-live date.

Do I need separate providers for Peppol and TDD submission?

No. A provider like GoRoute operates the certified Peppol Access Point and SMP and generates the TDD from the PINT OM invoice in one workflow, so a single integration covers issuance, validation, transmission and CTC submission.