Fawtara: What Oman's E-Invoicing Mandate Requires, and When

What Fawtara actually changes

A PDF emailed to a customer is an electronic document but not an electronic invoice. Fawtara requires a structured invoice — a machine-readable file in a prescribed schema, exchanged through accredited infrastructure, and cleared with the tax authority rather than merely sent to the buyer.

That distinction is the whole mandate. The invoice stops being a document your finance team produces and becomes a data record that has to validate against a specification before it is legally issued. An invoice that fails validation has not been issued late; depending on the transaction it may not have been issued at all.

The dates that currently matter

The OTA has set out the rollout in phases, amending the VAT Law by Decision No. 189/2026 to do it:

Two things about that table are worth saying plainly. The first is that if you have not been notified, you are almost certainly not in the pilot — the OTA approached this cohort directly, and being in it is not something you discover by inference. The second is that the April 2027 date is closer than it reads. A company above the OMR 5 million threshold has roughly two financial quarters to get its master data in order, and master data is the part that takes longer than the software.

These dates have moved before. The Peppol decision was taken in January 2026 and the phase structure was set out afterwards, so anything you read about Omani e-invoicing that was written in 2025 describes a different plan. Check the Fawtara portal against any summary, including this one.

Why Peppol means you are choosing a provider, not a file format

In January 2026 the OTA was approved as a Peppol Authority, which settled the architecture question: Fawtara runs on Peppol rather than on a bespoke national protocol. Peppol's ordinary shape is a four-corner model — your system, your access point, your customer's access point, your customer. Fawtara adds the tax authority as a fifth corner, so a cleared invoice reaches the OTA as part of being exchanged rather than as a separate filing.

The practical consequence is that you do not connect to the OTA. You connect to an accredited service provider that is already on the network, and your compliance depends on that provider's accreditation as much as on your own data. This is a procurement decision with a compliance consequence, which is an unfamiliar combination for most finance functions and worth recognising as one early.

It also means the interoperability problem is largely solved for you. An invoice that validates against the Omani specification will travel to a counterparty in another Peppol country without bilateral agreement, which is the argument for the standard over a national format.

What "compliant" means at the file level

Invoices must be produced from accounting or ERP software and transmitted as XML in UBL 2.1, or as PDF/A-3, aligned to the PINT Oman specification — the Omani localisation of Peppol's international invoice model. PINT is where the country-specific rules live: which fields are mandatory in Oman, how VAT treatment is expressed, what identifiers a buyer and seller must carry.

That last point is where readiness projects actually fail, and it has nothing to do with XML. A mandatory field is only a problem if you do not reliably hold the data that goes in it. Most companies discover during testing that they have customer records without a usable tax identifier, item lines without a classification, or a VAT treatment applied by habit at invoice time rather than derived from stored attributes. None of that is visible while a human is producing the invoice, because a human silently fills the gaps.

What to do now, depending on where you sit

If the OTA has notified you

You are live, and the work is operational rather than strategic: a monitored path for rejected invoices, someone who owns the exception queue, and a tested answer to what happens when clearance is unavailable and a customer still needs an invoice today.

If you are above OMR 5 million in annual supplies

April 2027 is your date. Spend the first part of the runway on data, not on software selection. Extract a few thousand recent invoice lines and check them against the PINT Oman mandatory fields — the output of that exercise tells you whether this is an integration project or a master-data cleanup with an integration at the end. They have very different costs.

If you are below the threshold

October 2027, and the sensible posture is to avoid decisions that make compliance harder later. If you are replacing an accounting system or a POS in the next eighteen months, make Peppol capability a selection criterion now. It costs nothing to ask and it removes a migration.