Oman has a real e-invoicing programme. It is called Fawtara, it is run by the Tax Authority, and it uses the Peppol five-corner model. It now also has a law behind it. Decision 189/2026, issued by the Chairman of the Tax Authority on 3 August 2026 and published in Official Gazette issue 1660 on 9 August 2026, amends the VAT Executive Regulations to mandate electronic invoicing from 1 April 2027 for taxable persons whose annual supplies exceed OMR 5 million, and from 1 October 2027 for those at or below it.
The law and the Authority's own website currently disagree, and the website is the one that is wrong. Decision 189/2026 is gazetted — Official Gazette issue 1660, 9 August 2026 — and it sets two mandatory dates, 1 April 2027 and 1 October 2027, split at OMR 5 million.
Meanwhile the Authority's Fawtara FAQ document is still stamped 30 June 2026 and still says the "Regulation for e-invoicing will be released in due time". It has been released. And the Authority's e-invoicing FAQ page still displays the old four-phase timetable of August 2026, February 2027 and August 2027. Both are superseded.
If you are planning around a date, take it from the Gazette text, not from the portal. We have linked the Arabic text in the sources at the foot of this page.
What the decision actually does
Decision 189/2026 amends the Executive Regulations of the VAT Law, issued by Decision 53/2021. It replaces Article 143, inserts Articles 143 bis, 143 bis 1 and 143 bis 2, replaces the second paragraph of Article 146, and adds an item 11 to Article 147. Article 143 now defines the electronic tax invoice as one issued, sent and kept in an approved and secured electronic format, stored with a unique number for each invoice. Article 143 bis provides for the companies licensed to supply e-invoicing services, and says the Authority will announce them to taxpayers. Article 143 bis 1 deals with the security and resilience of the systems. Article 143 bis 2 allows an exemption on justified application.
Article 3 carries the operative dates, and they are worth reading in the original because so much secondary coverage paraphrases them loosely: 1 April 2027 for taxable persons whose annual supplies exceed OMR 5 million, and 1 October 2027 for those whose annual supplies do not exceed OMR 5 million. There is no third date and no fourth phase in the decision.
No royal decree. This is a chairman's decision made under the existing VAT Law, not new primary legislation. That is perfectly sufficient to bind you, but it means the framework can be changed again by another chairman's decision rather than by a decree.
No penalty for failing to e-invoice. The decision sets no fine and no penalty schedule, and the Authority's FAQ had deferred penalties to regulations that have not appeared. That gap is real and it has survived the change.
No QR code, no cryptographic stamp, no invoice hash, no UUID. None of these words appears anywhere in the gazetted Arabic text. The only identification requirement is a unique number per invoice. See the section below, because several vendors are telling Omani businesses otherwise.
A little history explains why this matters. The previous amendment to the VAT Executive Regulations, Decision 81/2025 of 30 April 2025, dealt with registration certificates and procedures and did not mention electronic invoicing at all. For about a year the Authority ran a funded, staffed, technically delivered programme — a production system at fawtara.taxoman.gov.om, a Service Provider Registration User Manual v2.0.0, an Oman SMP API Specification, accreditation opened on 28 June 2026 — with no instrument underneath any of it. That absence is exactly why the announced dates kept moving. It is now closed, and the dates moved once more on the way.
What happened to August 2026
There is no mandatory start in August 2026 and there never will be now. Nothing went live, and no Authority announcement claimed anything had. What sits in that slot instead is a voluntary pilot of about 100 taxpayers, scheduled to begin at the end of August 2026 — and as at 17 August 2026 we cannot confirm it has started, because the end of the month has not arrived. Both halves of that matter: it is a pilot, not a mandate, and it is scheduled, not running.
The phases under Decision 189/2026
| Stage | Date | Who |
|---|---|---|
| Pilot | Scheduled from end August 2026 | About 100 taxpayers, voluntary, selected by the Authority |
| Phase 1 | 1 April 2027 | Annual supplies exceeding OMR 5 million |
| Phase 2 | 1 October 2027 | Annual supplies not exceeding OMR 5 million |
Read the second column carefully, because this is the biggest single change. There is now a published turnover threshold. Phase membership is no longer a selection exercise you cannot reverse-engineer: if your annual supplies exceed OMR 5 million you are in the first phase and you have until 1 April 2027; if they do not, you are in the second and you have until 1 October 2027. The earlier four-phase timetable — August 2026, February 2027, August 2027 and an undated government phase — is superseded. The decision says nothing about government institutions, so what happens to them is now unclear rather than merely undated, and we are not going to guess.
Take your annual value of supplies. Above OMR 5 million puts you in the first phase, 1 April 2027. At or below it puts you in the second, 1 October 2027. That is a rule you can now apply to yourself. It is the single biggest practical change in the decision, because until 9 August 2026 phase membership was a discretionary selection you had no way of predicting.
The Tax Authority's rollout period checker is still live at tms.taxoman.gov.om/portal/rollout-checking. You enter your full VATIN, the one beginning OM, press search, and it returns your assigned rollout period. Its role has changed, though: it used to be the only authoritative answer to a question you could not answer yourself. It is now a confirmation of an answer you can work out first.
If the checker and the threshold disagree, treat the earlier of the two dates as your planning date and ask the Authority in writing. The checker was built around the old timetable, and like the rest of the portal it may not yet reflect the decision.
The checker page carries no phase dates itself — it is purely a lookup, with a Fawtara support email for anything further. Check it, and check it again before your phase date, because assignments can change.
Which official pages to distrust, precisely
As at 17 August 2026 — eight days after the Gazette — the Tax Authority's own published pages still describe the programme the Gazette replaced. Three specific items are wrong. The Fawtara FAQ document is still stamped 30 June 2026 and still says the regulation "will be released in due time"; it has been. The e-invoicing FAQ page still gives four phases beginning August 2026, then February 2027, then August 2027. The e-invoicing overview page still gives four phases described only by taxpayer size, with no dates at all.
This is ordinary lag — portal content trails instruments everywhere — but the consequence is not ordinary. A reader who does the sensible thing and checks the government website rather than a blog will come away with a superseded timetable and no threshold, and will be planning for February 2027 when the law says April. Where the portal and the Gazette disagree, the Gazette wins. That is not a close question: Decision 189/2026 is published law and the FAQ is guidance that has not been revised.
One older confusion is worth killing while we are here, because it is now actively dangerous. The Authority has always said the pilot cohort is about one hundred taxpayers. At least one widely copied vendor page describes phase 1 as the "top 150 largest taxpayers". That 150 is not a Tax Authority figure, and it collides with a separate 150 that does appear in the Fawtara portal terms — an annual cap on free-portal invoices, discussed below. Two different numbers, neither of them a phase rule. If you see 150 attached to phase membership, discard it.
How Fawtara works: the five-corner model
Fawtara uses the Peppol five-corner model. Four corners are the ordinary Peppol network — the trading parties and their service providers — and the fifth is the tax authority.
- C1 — the supplier, who issues the invoice
- C2 — the supplier's accredited service provider, who validates it and puts it on the network
- C3 — the customer's accredited service provider, who receives it
- C4 — the customer
- C5 — the Oman Tax Authority, which receives the tax data
The structural point: you do not send invoices to the Tax Authority yourself, and you do not wait for the Authority to approve an invoice before issuing it. Your service provider validates against the Oman schematron rules, exchanges the document with the buyer's provider, and reports the tax data to the Authority. The Peppol specification defines this reporting document separately as a Tax Data Document, submitted to the Authority rather than exchanged between trading parties.
Format and timing
XML is the mandatory structured format. The specification is PINT OM, published by OpenPeppol at docs.peppol.eu, at version 1.0.1 with a development kit release of 29 July 2026. It defines three processes: the Tax Data Document, PINT OM Billing for ordinary invoicing, and PINT OM Self-Billing for buyer-issued invoices. A PDF is not an e-invoice under this regime, and neither is a scan.
| Transaction | Submission timing |
|---|---|
| B2B | Real time |
| B2C | Within 24 hours |
| Exports | C1 to C2 to C5, bypassing the buyer side |
Those timings come from the Tax Authority's Fawtara FAQ document, not from Decision 189/2026 — the decision itself does not set submission windows, and several secondary write-ups blur that. Note the export flow: because there is no Omani buyer or Omani service provider, an export invoice runs from you, through your provider, to the Authority only. The point that does follow from the decision is the format one, and it is the expensive one: once your phase lands, paper invoices, plain PDFs and emailed images stop being valid tax invoices — not merely discouraged, not valid. Some coverage also states that consolidated B2C invoices are prohibited; we could not find such a prohibition in the gazetted Arabic text, so treat it as unconfirmed rather than as a rule.
Service providers, and the free option
You will transact through an accredited service provider. To be accredited, a provider must complete OpenPeppol testing and the Oman Test Suite and submit the evidence to the Tax Authority for review; the Fawtara portal then lets taxpayers onboard and manage their provider relationship. The Authority's FAQ refers to a 30-day response timeline for providers. Accreditation opened with Release 2 on 28 June 2026.
One caution on choosing a provider. The Tax Authority's accreditation section does not publish a list of accredited providers. It is an information hub pointing to manuals, criteria and provider FAQs, and it carries its own warning that requirements "are subject to change in line with project phases and regulatory or technical updates". Several vendor sites publish "OTA-accredited" lists; the fullest of them names eleven providers, and it was compiled in July 2026, before the decision. Those lists are self-declared or assembled by third parties, not reproductions of an official register. Ask a prospective provider for their accreditation evidence directly.
This is the question we are asked most, so here it is plainly. Zoho, Xero, QuickBooks, Sage and Odoo do not appear on any accredited-provider list for Oman. Tally appears only as a system that an accredited provider can connect to, which is a different thing entirely.
Oman accredits service providers, not accounting software. The accredited names are e-invoicing specialists, not general bookkeeping packages. So the likely shape of your solution is: keep the accounting system you have, and connect it to an accredited provider that does the Peppol exchange and the reporting.
If a salesperson tells you their bookkeeping product is "OTA-approved", ask which register they are on and for the evidence. There is no Omani approved-software list for them to be on.
The Fawtara portal terms published on the tax portal describe a free service under which you appoint the portal operator as your authorised service provider and are onboarded to the Oman SMP. That route does exist and is worth looking at before you buy anything.
The limits previously published with it were up to 150 e-invoices a year, counting standard invoices, debit notes and credit notes together, with PDF and XML files no longer accessible through the portal 120 days after issue. We record those as previously published figures because we could not re-verify either of them on any Tax Authority page on 17 August 2026. Do not build a plan on the number without confirming it with the Authority.
The wider point survives regardless of the exact cap. A free portal route is a genuine answer for a micro-business and not an answer for anyone issuing invoices daily. And any portal retention window measured in months sits awkwardly against a ten-year record-keeping obligation — download and archive your own copies either way.
What applies now, regardless of Fawtara
Whatever happens with the phases, the existing invoicing law applies to every VAT-registered business today. Article 67 of the VAT Law requires a tax invoice when you supply goods or services, or when you receive consideration in advance, and leaves the required contents to the Executive Regulations.
The enforceable part is Article 100. Refusing to issue a tax invoice when required, or issuing an invoice showing an incorrect amount of tax, carries imprisonment of two months to one year and/or a fine of OMR 1,000 to OMR 10,000, doubling on repetition. That is the invoicing penalty that exists in Omani law right now. There is no published penalty at all for failing to e-invoice.
Retention is Article 70: ten years from the end of the tax year, fifteen years for real estate documents. And a distinction worth drawing carefully — Articles 5 and 6 of the Executive Regulations already allow returns and documents to be filed through the Authority's portal or by email, and deem them signed and received on the date of receipt. That is electronic filing of returns, which has existed since 2021. It is not e-invoicing, and the two are frequently conflated. On the mandatory particulars of a tax invoice, and on what your till has to print at the counter, see our guide to invoicing and POS systems in Oman — this page does not repeat them.
We have read the gazetted Arabic text of Decision 189/2026. There is no QR code in it. There is no cryptographic stamp, no invoice hash, no UUID and no public-key infrastructure obligation either. The only identification requirement anywhere in the decision is that each invoice is stored with a unique number.
This needs saying because at least two widely republished vendor pages assert that the decision makes a QR code mandatory on B2C invoices. It does not, and we have corrected this page accordingly. The Tax Authority's own service provider FAQ is the proof: it says guidance on QR codes and on the difference between UUID and hash "will be shared shortly". An authority does not promise forthcoming guidance on a requirement it has already imposed.
Much of what you are being sold is Saudi Arabia's rulebook. Cryptographic stamps, invoice hashes and UUIDs are ZATCA requirements under Saudi law and appear in no Omani instrument. If a supplier quotes you for a stamping or hashing module on the strength of an Omani obligation, the obligation does not exist. This could change — the Authority has said guidance is coming — but it has not changed yet, and you should not pay for it today.
The QR code is the one item on that list where the Authority itself has said something, and you should hear it from us before you find it yourself: the Tax Authority's own Fawtara FAQ document, stamped "Last updated on: 30th June 2026", says that "The QR code is required only on the human-readable invoice (not the e-invoice)" and that a "QR code is mandatory for all (B2C) transactions whether full or simplified", generated by the taxpayer, under a heading reading "QR Code, UUID and Invoice Hash". Read that as an administrative design expectation published ahead of the legislation rather than a rule in force — the same document still says the e-invoicing "Regulation will be released in due time", and the QR code did not make it into the gazetted decision that followed, so nothing in Omani law requires one today.
What Oman is not: five systems people confuse it with
E-invoicing is the single worst topic in Gulf tax content for cross-border contamination, because the neighbouring programmes are far better documented than Oman's. These are the specific confusions we hit while researching this article.
- Saudi Arabia — ZATCA and FATOORA. A clearance-and-reporting model with QR codes, cryptographic stamps and UUIDs, rolled out in waves defined by SAR turnover thresholds and structured as "Phase 1 Generation" and "Phase 2 Integration". Oman has taken none of that list — no QR code, no stamp, no hash, no UUID — and its two phases are a scope schedule split by turnover, not a generation-then-integration model. If you see "Phase 1 / Phase 2 integration" framing applied to Oman, or a QR code asserted as a gazetted Omani requirement, you are reading Saudi rules with the country name changed — with the single qualification set out in the callout above.
- United Arab Emirates. The hardest one, because the UAE genuinely also uses a Peppol five-corner model with accredited service providers. The tells are the specification and the portal: the UAE uses PINT AE, EmaraTax and the Ministry of Finance provider register. Oman uses PINT OM, the Fawtara portal and the Oman SMP.
- Jordan — JoFotara. Jordan's national system is also called Fawtara. An Arabic search for فوترة will put Jordanian government manuals in front of you that look entirely plausible. Jordan's is at jofotara.gov.jo; Oman's is at fawtara.taxoman.gov.om.
- Qatar — Dhareeba. The Qatari tax portal. Nothing to do with Oman. Oman's portal is tms.taxoman.gov.om.
- Egypt, and "Royal Decree on e-invoicing". Egypt has run its own mandate for years. And searching for a royal decree on structured electronic invoicing will return Belgium before it returns anything Omani — because Oman has not issued one.
The Jordan point deserves emphasis for readers who research in Arabic, which in Oman is most people. The two systems share a name. A Jordanian user manual, a Jordanian penalty schedule and a Jordanian registration deadline will all read as authoritative and will all be wrong for you. Check the domain before you read the document.
What to do now
You can now do the first step yourself, which you could not before 9 August 2026: look at your annual supplies, decide which side of OMR 5 million you are on, and put the matching date in the calendar. Everything after that is the same for everyone and none of it is wasted, because the existing invoice rules require it anyway.
- Work out your annual value of supplies and take your date from it — over OMR 5 million means 1 April 2027, otherwise 1 October 2027. Then enter your VATIN at the Tax Authority's rollout checker and record what it says, in case the two differ.
- Confirm whether your accounting system can output structured XML to a named specification, or whether it only produces PDFs. That single question determines whether this is a configuration job or a system replacement, and after your phase date a PDF is no longer a valid tax invoice.
- Clean your customer master data. The five-corner model routes on tax identification numbers; a wrong or missing VATIN on a business customer will fail validation in a way that a PDF never did.
- Check whether your annual supplies sit close to OMR 5 million. If they move across that line between now and 2027, your date moves with them, and the decision does not say which year's figure is measured — so ask the Authority in writing rather than assuming.
- If you issue very few invoices, look at the free portal route before you buy anything; if you are in the first phase, start talking to service providers now and ask each one for evidence of accreditation rather than a claim of it.
- Do not buy a QR, cryptographic stamping or invoice-hashing module for Omani compliance. No Omani instrument requires any of them today. Revisit only if the Authority publishes the guidance it has promised.
The gaps that remain, now the biggest one has closed
For a year the honest summary of this programme was that nothing underneath it was published. That is no longer the headline: the instrument exists, the threshold is public, and the dates are law. What is left is a shorter and more specific list, which is worth keeping because every item on it is something a vendor may try to fill in for you.
- No penalty for e-invoicing non-compliance. Not in Decision 189/2026, not anywhere else. The Authority's FAQ deferred penalties to regulations that have not appeared. Article 100 of the VAT Law still bites on invoicing generally, but there is no e-invoicing-specific fine.
- No QR, hash or UUID rule — and no published guidance either. The Authority's service provider FAQ says that guidance "will be shared shortly". Until it arrives, nothing is required and nothing can be planned for with any precision.
- No published rule for who is in the pilot. The roughly 100 pilot taxpayers are still picked by the Authority, on criteria it has not published. Selection discretion survives for the pilot even though it has gone for the mandatory phases.
- No official list of accredited service providers, despite an accreditation section on the portal. The lists in circulation are secondary compilations.
- No clarity on government institutions. The old four-phase timetable had a phase for them. Decision 189/2026 does not mention them at all, which is a gap rather than an answer.
- No published detail on how PINT OM fields sit against the Article 144 invoice particulars, and no re-verifiable figure for the free portal's annual invoice cap.
Is e-invoicing mandatory in Oman?
When does e-invoicing start for my business in Oman?
What happened to the August 2026 start date for Oman e-invoicing?
Do Omani invoices need a QR code?
What is the penalty for not e-invoicing in Oman?
Is Zoho, Xero, QuickBooks, Sage or Odoo approved for e-invoicing in Oman?
We will re-verify this guide when the Tax Authority updates its own e-invoicing pages to match the Gazette, and when the promised guidance on QR codes and identifiers appears. The date at the top will change when we do. If you want your turnover checked against the OMR 5 million line, your VATIN run through the rollout checker, or your invoice output tested against the specification before your date reaches you, our office in Al Ghubra can do that with you. The counter-level detail — the mandatory particulars and the till itself — is in our guide to invoicing and POS systems in Oman.