Web design for Muscat.
Built for Fawtara, without inventing its deadline.

Oman is further along than the commentary suggests in one way and further behind in another, and getting that the wrong way round costs money. The Oman Tax Authority is a recognised Peppol Authority and its Fawtara system is real, specified and published. What it has not published is a single date. Every consultancy page you will read quotes dates anyway. We build to the model and leave the date configurable, which is the only honest engineering answer to a timetable that does not yet exist in writing.

Start a project

What the Oman Tax Authority actually publishes

Read from the Tax Authority’s own e-invoicing page on 2 November 2026, and cross-checked against OpenPeppol’s register of authorities. We are quoting what is on the page, including the gaps.

Fawtara is a five-corner model, and that part is settled

The Authority describes a 5-corner model: you and your customer each work through a service provider, and the tax authority sits as the fifth corner receiving the data. That is the same shape as the UAE’s system, so a build that is ready for one is most of the way to the other. This is the part worth engineering now.

Oman is a Peppol Authority, which is the real signal

OpenPeppol lists the Oman Tax Authority, E-invoicing Project (Fawtara) among twenty-six Peppol Authorities worldwide. That means the network standard is decided. Your invoice format question is answered even though your deadline question is not.

Four phases, and no dates against any of them

The Authority lists a pilot with selected large taxpayers, expansion to medium and large companies, SME onboarding, then all VAT-registered entities. Against those four phases its page carries no dates and no revenue thresholds. The page was last updated on 7 October 2026, so this is current rather than stale.

So we will not sell you a deadline

Dates and an OMR threshold are circulating widely in advisory commentary, attributed to a Chairman’s decision. They may well be right. They are not on the Authority’s page, this site’s rule is that a figure needs a publisher we can point you at, and your accountant is the person to confirm your own dates with. What we can do is make the switch a configuration change rather than a rebuild.

Sources, checked 2 November 2026

How that changes what we build

A regime with a known format and an unknown start date calls for different decisions from one with a published go-live.

The invoice document gets its own layer What you sell and how you bill are separated from how the invoice is formatted and sent. When Fawtara switches on for your band, that is a new output from an existing layer, not a project.
Nothing is hard-coded to a date No deployment, no migration and no feature flag in your system carries a Fawtara date, because we would only have invented it. The switch is an administrative setting.
Your service provider stays swappable In a five-corner model the accredited provider is the piece most likely to change, on price or on service. We integrate through an interface so that swapping provider is a week, not a rewrite.
Arabic is a first-class requirement, not an afterthought Right-to-left layout, Arabic numerals where you want them, and both languages on the document. Retrofitting this into a finished English system is the single most expensive mistake on Gulf projects.

When we are the wrong firm for this

If what you actually need is Fawtara compliance in isolation — your existing accounting package connected to an accredited provider and nothing else — then you need an accredited service provider and your accountant, not us. That is a procurement decision with a short list, and paying a development studio to sit in the middle of it adds cost and a second point of failure.

Where we fit is when the invoice is an output of something larger we are building: an ordering system, a trade portal, a platform with its own billing. Then having the invoicing designed in from the start is worth real money. If your invoice comes out of an off-the-shelf package, keep it there.

Questions

Before you ask.

When does Fawtara become mandatory for us?

The Oman Tax Authority’s own e-invoicing page lists four phases — pilot, expansion, SME onboarding, then all VAT-registered entities — and puts no dates or thresholds against them. Dates are circulating in advisory commentary and may be correct, but they are not on the Authority’s page, so we will not quote them to you as fact. Confirm your own band with your accountant, and build so the date is a setting.

Is Oman using Peppol?

Yes. OpenPeppol lists the Oman Tax Authority, E-invoicing Project (Fawtara) as one of twenty-six Peppol Authorities, and the Authority describes Fawtara as a 5-corner model. The format question is settled even though the timetable is not.

We already have a UAE system. Does it carry over?

Largely, in shape. Both are five-corner models working through accredited service providers, so the architecture transfers and the integration layer is reusable. The provider, the registration and the invoice fields are country-specific, so budget for a connector rather than a second build.

Ready to get started?

Tell us what you need. We will scope it, price it and build it.

Start a project →

Web design for Muscat.Built for Fawtara, without inventing its deadline.