Oman E-Invoicing (Fawtara) 2027: Dates, PINT OM and What Breaks
Short answer: Oman’s Fawtara e-invoicing mandate is now law. Businesses with annual supplies above OMR 5 million must comply from 1 April 2027; every other VAT-registered business follows on 1 October 2027. Invoices must be structured data on the PINT OM specification, exchanged over the Peppol network — a PDF will not do.
The part that decides whether this is painful is not the software. It is whether your customer records, item master and tax codes are clean enough to produce a valid structured invoice at all.
Already live: the pilot cohort
Before the statutory dates below, there is a phase already in force. The Tax Authority launched the Fawtara pilot on 1 August 2026, and around 100 selected large VAT-registered taxpayers have been issuing Peppol e-invoices since then, covering their B2B taxable transactions — including where the buyer is not yet connected to the network.
If your business was notified as part of that cohort, your obligation started in August 2026, not 2027. Check whether you were selected before assuming the April date applies to you. Other taxpayers may also join voluntarily ahead of their deadline, which is worth considering: testing against real customer invoices while there is no penalty for getting it wrong is considerably cheaper than doing it in the first compliant week.
The dates that bind — and why you may have seen different ones
Oman’s Tax Authority issued Decision No. 189/2026, published in Official Gazette No. 1660 on 9 August 2026, amending the Executive Regulations of the VAT Law to require tax invoices in an approved, secure electronic format.
| Who | Mandatory from | Time remaining |
|---|---|---|
| Annual supplies above OMR 5 million | 1 April 2027 | About 7 months from this guide’s September 2026 review |
| All remaining VAT-registered businesses | 1 October 2027 | About 13 months from this guide’s September 2026 review |
A warning about the dates circulating elsewhere. Oman revised its implementation timeline, and a good deal of vendor material still repeats the earlier roadmap of February 2027 and August 2027 phases. Those two were replaced by Decision No. 189/2026. The August 2026 pilot, by contrast, did go ahead and is running now — see above. The binding dates are the two above. If a supplier is quoting the old schedule, treat it as a signal about how closely they are actually following this.
What Fawtara actually requires
Oman has taken the decentralised Peppol route rather than a central clearance platform. The Tax Authority became a Peppol Authority in January 2026 and published the draft PINT OM specification — the Omani profile of the Peppol International Invoice — in April 2026, with the binding version 1.0.1 released on 29 July 2026 (build against that version, not the draft). In plain terms:
- Invoices are issued as structured data — XML (UBL 2.1), or PDF/A-3 carrying that structured data — conforming to PINT OM.
- They are exchanged over the Peppol network through a service provider, not emailed directly.
- They must be issued, transmitted and retained in that approved secure format.
What will not qualify: a paper invoice, an ordinary PDF, or a scanned image sent by email. This is the point most finance teams underestimate. The invoice stops being a document a human reads and becomes data a machine validates — and a field that is missing, mistyped or wrongly coded is no longer a cosmetic issue a customer would forgive. It is a rejected transaction.
What actually breaks: audit this before you buy anything
In every implementation we have run, the integration is the small part and the data is the large part. Structured invoicing exposes every shortcut a finance team has been quietly absorbing for years, because a person could read around them and a schema cannot.
Run this audit first. It takes days rather than weeks, and it tells you whether your remaining time goes into clean-up or integration:
- Customer tax records. How many VAT-registered customers have no valid VAT identification number recorded, or one that fails a format check? Usually the single largest gap.
- Item master discipline. Consistent codes, descriptions and units of measure — or does the same product exist three times because three people created it?
- Tax treatment per line. Oman’s 5% standard rate, zero-rated and exempt supplies must be distinguishable line by line, not decided per document.
- Invoices raised outside the system. Every invoice produced in a spreadsheet or a Word template is one that cannot be transmitted. Count them honestly.
- Credit notes. A structured system needs a properly referenced credit note, not an amended reprint of the original.
- Multi-entity and multi-currency. If you invoice from more than one legal entity, each needs its own registration details carried correctly on every document.
The output of that audit is the only reliable input to a budget. Anyone quoting you a figure before it exists is guessing.
What to do with the time remaining
- Now. Establish which side of the OMR 5 million line you fall on — it decides whether your deadline is April 2027 or October 2027 — and run the data audit above.
- In parallel, not after. Shortlist service providers who can transmit over Peppol for Oman. Do not wait for the clean-up to finish first.
- Then. Fix the master data, close the off-system invoicing routes, and map your ERP output to PINT OM.
- Before the deadline. Test end to end rather than discovering rejections on live customer invoices in the first compliant week.
Where ERPNext fits — and what we are not
ERPNext holds the structured transaction data the specification depends on, and because it is open-source, the item master, tax templates and customer records can be extended with the fields PINT OM expects, then mapped to your service provider’s interface. There are no per-user licence fees, which matters when compliance work suddenly requires more people to touch the system.
We will say the same thing here that we would say in the room: the ERP is not the service provider. Your system produces the invoice data; a separate accredited party transmits it across the Peppol network. You need both, and we are clear about which one we are. Be wary of any vendor who blurs that line.
Related reading: our Oman ERP buyer’s guide, the Oman implementation service, and for groups trading across the Gulf, the UAE e-invoicing guide and Saudi Arabia (ZATCA).
This guide is general information, not tax advice. Confirm how the rules apply to your business with your tax adviser or against current Oman Tax Authority guidance. Facts verified against Decision No. 189/2026 (Official Gazette No. 1660, 9 August 2026). Last reviewed 10 September 2026, and corrected the same day after an independent fact-check.
Frequently asked questions
When does e-invoicing become mandatory in Oman?
Two dates, both now written into law by Tax Authority Decision No. 189/2026, published in the Official Gazette on 9 August 2026. Businesses with annual supplies above OMR 5 million must issue tax invoices in the approved electronic format from 1 April 2027. Every other VAT-registered business follows from 1 October 2027. There is no turnover floor at the second stage, so in principle every VAT-registered business is captured. The relief is narrow: the amended regulations let the Chairman of the Tax Authority grant a taxpayer an exemption for a determined period, on formal application with supporting reasons, and non-resident foreign suppliers sit outside the scope.
Careful - are the Fawtara dates you have seen elsewhere out of date?
Quite possibly. Oman revised its implementation timeline, and a good deal of vendor content still circulates the earlier February 2027 and August 2027 phases, which Decision No. 189/2026 replaced with 1 April 2027 and 1 October 2027. Note the distinction: the August 2026 pilot was not cancelled - it went live and is running now for around 100 selected large taxpayers. If a supplier is quoting you the older schedule, that is a useful signal about how closely they are following this.
What format does Fawtara actually require?
Structured electronic invoices built on the Peppol network. Oman's Tax Authority became a Peppol Authority in January 2026 and published the draft PINT OM specification in April 2026, with the binding version 1.0.1 released on 29 July 2026 - build against that version. Invoices are exchanged as XML (UBL 2.1) or PDF/A-3 conforming to that specification. The practical consequence matters more than the acronyms: a paper invoice, an ordinary PDF, or a scanned image emailed to your customer will not qualify as a tax invoice.
Is a PDF invoice good enough?
No - and this is the single most common misunderstanding. Under the new framework an ordinary PDF is not an electronic tax invoice. What is required is structured data a machine can read and validate, which is why the state of your item master, tax codes and customer records decides how hard this transition will be. Emailing the same invoice you send today, as a PDF, will not make you compliant.
What should an Omani business do first?
Not choose software. Start with an audit of the data the schema depends on: how many customers lack a valid VAT identification number, whether tax treatment is set per line rather than per document, how many invoices are raised outside your accounting system in spreadsheets or Word, and whether corrections are issued as properly referenced credit notes. That audit takes days and it determines everything else, because it tells you whether your remaining time goes into clean-up or into integration.
Does ERPNext support Oman e-invoicing?
ERPNext holds the structured transaction data the specification requires, and being open-source it can be extended with the fields PINT OM expects and connected to the service provider you appoint. The honest framing is the one we give every client: the ERP produces compliant invoice data, and a separate accredited party transmits it over the Peppol network. You need both, and most of the real work is data quality rather than software.
How does this compare with the UAE and Saudi Arabia?
Saudi Arabia went first and routes invoices through a central government platform for clearance under ZATCA. The UAE and Oman have both taken the decentralised Peppol route, with the UAE mandatory for larger businesses from 1 January 2027 and Oman following from 1 April 2027. For a group trading across the Gulf that means one ERP has to satisfy genuinely different architectures - an argument for keeping invoice data clean and standards-based in one system rather than bolting on a country-specific workaround.