Odoo e-invoicing in Oman: Fawtara
The Oman e-invoicing picture in full: the scheme, the authority behind it, who it binds, and every requirement we map before a build is quoted.
Fawtara (ููุชุฑุฉ), the Oman Tax Authority e-invoicing system
Authority: Oman Tax Authority (OTA)
Nothing is mandatory yet. As of 22 August 2026 the OTA is running a voluntary pilot with about 100 selected large VAT-registered companies, and Decision 189/2026 (issued 9 August 2026) fixes the binding dates at 1 April 2027 and 1 October 2027.
VAT-registered taxable persons. Decision 189/2026 obliges those with annual supplies above OMR 5 million from 1 April 2027, and those at or below OMR 5 million from 1 October 2027. Before those dates participation is voluntary and in practice limited to the OTA's invited pilot group of about 100 large taxpayers.
Every requirement, in full
6 requirements. Each one has to end up as a field, a document layout, a stored response, or an API call in your Odoo build. This is the list an e-invoicing project in Oman gets costed against.
- 1 Structured XML invoices built to the PINT OM specification. Three documents are published: PINT OM Billing, PINT OM Self-Billing, and the Oman Tax Data Document (TDD) used to report invoice data to the OTA. Paper invoices, PDFs and emailed images stop counting as tax invoices once the obligation applies.
- 2 Exchange over Peppol. The OTA was approved as a Peppol Authority on 7 January 2026 and publishes an Oman SMP API specification, so invoices move through an accredited service provider rather than being posted to the tax authority directly.
- 3 A five-corner model: supplier, supplier's service provider, buyer's service provider, buyer, and the OTA. Invoice data reaches the OTA at the same time as the buyer. This is continuous reporting, not per-invoice pre-clearance where the invoice is held until the authority signs it.
- 4 Amended Article 143 of the VAT Executive Regulations requires each invoice to be issued in an approved, secured electronic format that keeps it intact and stored, with a unique number per invoice.
- 5 Accredited service provider registration opened in March 2026. The OTA portal publishes a Service Provider Registration User Manual alongside the SMP API specification.
- 6 The draft data dictionary grew from 53 mandatory invoice fields in the November 2025 OTA draft to 73 in the PINT OM framework, so field-level mapping is real work and should not be underestimated.
Checked Localization notes on this page checked on 22 August 2026.
Rates, formats, thresholds and submission windows change. We configure against the rules in force at build time and confirm every figure with your accountant or tax advisor before sign-off. If a rule moves after go-live, it is a support ticket, not a rebuild. Read more on our Odoo localization service.
How we build e-invoicing for Oman
The delivery method behind the list above. The same four steps on a 10-user rollout and on a multi-company programme, with the depth scaled to the scope.
- 1 Requirements first, code second. Each line above becomes a field, a report, or an API call on a written mapping sheet. Anything with no home in Odoo is quoted as a build before the project starts.
- 2 Numbering is settled on day one. Invoice sequences are the part that breaks quietly and costs the most to unwind after go-live, so they are signed off before the first test document.
- 3 Submission runs from a queue. Retries, idempotency keys, stored responses and an audit trail. A failed send becomes a ticket with evidence, not a missing invoice you find at month end.
- 4 Your finance team signs it off. Real documents, in a test database, checked with your accountant or tax advisor before cutover, with a rollback plan in writing.
What we need from you to quote it
Bring these to the first call and you get a scoped, priced e-invoicing plan for Oman instead of a range.
- โ Your tax registration details and the entity each one belongs to.
- โ A sample of every document type you issue: invoice, credit note, debit note, self-billing if you use it.
- โ Any registration, certificate or portal credential the authority has already issued you.
Services behind this work
The rest of the Oman localization detail
Each topic has its own page with the full item list, the same way this one does.
E-invoicing in other markets we cover
Running the same rollout across borders? These pages carry the same depth for each market, so you can compare before scoping a multi-country phase.
Scope e-invoicing for your Oman rollout.
Send us the list above with your answers against it. We come back with what is configuration, what is a connector, and what is a build, priced before the project starts.