Fawtara: what Oman’s e-invoicing mandate means for your business

Fawtara is the name the Oman Tax Authority gave its national e-invoicing programme. Under it, a tax invoice stops being a document you write and send yourself. It becomes a structured electronic record that passes through an accredited service provider, is validated, and is reported to the Tax Authority.

The word itself causes confusion, so it is worth separating three things. فاتورة is the Arabic word for invoice. فوترة is the programme. Fawtara is the Latin spelling the Tax Authority uses. People search all three interchangeably and they do not mean the same thing.

Two milestones set the technical shape. The Tax Authority became a Peppol Authority in January 2026, committing Oman to an international document exchange standard rather than a national one built from scratch. It published the PINT OM specification in April 2026, which defines what an Omani e-invoice contains and how it is structured.

The exchange uses a five-corner model: you, your service provider, your customer’s service provider, your customer, and the Tax Authority. You do not send anything directly to the Tax Authority, and you cannot. That routing is the most misunderstood part of the system and it determines what software you will need.

Most businesses reading this are in Phase 3. There are no permanent exemptions.

If you are registered for VAT in Oman and the Tax Authority has not written to you, you are almost certainly in Phase 3, with a date of 1 August 2027.

The Tax Authority published a rollout checker in May 2026 that answers this against your VAT identification number. That is the authoritative answer and it takes under a minute. Phase 1 covered a directly notified group, so if you were in it you would already know.

Being small does not remove you from scope. Neither does being new, working in cash, or having a single customer. The only businesses outside Fawtara are those not registered for VAT at all, and registration becomes mandatory at OMR 38,500 of annual taxable supplies, with voluntary registration available from OMR 19,250.

Most coverage treats Fawtara as a rule arriving in 2027. That is only half right, and the other half is more useful to know.

Decision 456/2022 amended Article 1 of the VAT Executive Regulations to define an Electronic Tax Invoice as a tax invoice generated in a structured format by electronic means. The same decision added a fourth violation to Article 202: failure to issue a tax invoice, or an electronic tax invoice, meeting the requirements set out in the Regulations and within the specified period.

That penalty provision has been in force since 17 October 2022. It does not wait for your Fawtara phase. Fawtara is the infrastructure that makes structured invoicing universal and verifiable, but the requirement to issue a correct tax invoice, on time, is already law and already carries a penalty of OMR 500 to OMR 5,000.

Today you can build a tax invoice in a spreadsheet, export it as a PDF, and send it on WhatsApp. Provided it carries the fields Article 144 requires, it is a valid tax invoice.

From your phase date, that stops being true. A PDF sent to a customer will not be a tax invoice. It will be a picture of one. The valid document is the structured electronic record that travelled through the accredited-provider route and was reported to the Tax Authority.

Three consequences arrive earlier than the deadline does.

• Your customers will ask before the law does. Large companies enter scope eighteen months ahead of you. From February 2027, a Phase 2 buyer dealing with a supplier still sending PDFs has a problem, and commercial pressure moves faster than regulatory pressure.
• Your invoice data has to be correct. Structured invoicing validates fields. A wrong customer VAT number, a rate applied to the wrong line, or a discount shown as a percentage instead of a value as Article 35 requires: these pass unnoticed on a PDF and get rejected in a structured system.
• You cannot fix a mistake by deleting it. Article 155 requires an adjustment document that identifies the original invoice and the tax value being corrected. There is no void mechanism in the Regulations. Once invoices are reported as they are issued, that stops being a housekeeping preference and becomes the only available path.

None of Article 144 waits for Fawtara. These are the fields a tax invoice needs now, and the same data is what a structured e-invoice will carry later, which makes getting them right today the cheapest preparation available.

The document must be titled Tax Invoice, carry a sequential number, and show the issue date and the supply date as separate fields. It must show your full legal name, address and VAT identification number, and your customer’s full name, address and VAT number where they have one. Each line needs a description, quantity, the consideration excluding tax, the tax rate applied, the taxable value, and the tax due in Omani rials. Any discount not already netted off must appear as a value, not only a percentage.

The full Article 144 field checklist is on the tax invoice penalties page

One requirement is routinely missed. Article 144 states that a tax invoice shall be issued in Arabic. English is permitted provided an Arabic translation can be furnished at the Tax Authority’s request. An English-only invoicing tool leaves you holding that obligation.

Article 143, as amended by Decision 456/2022, requires a tax invoice within 15 days of making a supply, making a deemed supply, or receiving consideration in full or in part before the date of supply.

The trigger most often missed is the third. An advance payment starts the clock even though nothing has been delivered yet. For a contractor taking a mobilisation payment, the 15 days run from the money arriving, not from the work finishing.

Under the five-corner model, e-invoices are exchanged through service providers accredited by the Tax Authority. Direct transmission from your own system to the Tax Authority is not part of the design and is not permitted. Accreditation opened during 2026 and providers are already operating.

We say this plainly because the distinction matters and is often blurred in marketing. Producing a correct document and transmitting it are two different jobs. Yusrin does the first. When your phase arrives, the second happens through an accredited provider.

Nothing on this list requires waiting for a technical specification or buying an integration.

Confirm your phase using the Tax Authority’s rollout checker, so you are working to a real date rather than an assumed one.

Audit one recent invoice against Article 144, field by field. Most non-compliance found this way is a missing supply date or a discount shown only as a percentage, and both take minutes to fix.

Check that your customer records hold correct VAT identification numbers. This is the field most likely to fail validation later and the slowest to fix in bulk.

Move off hand-built documents. Anything produced by retyping into a template will not survive structured validation, and the transition is far cheaper made once, early, than under deadline.

Confirm your invoices are issued in Arabic, or that you can produce an Arabic version on request.