Oman · Fawtara · ERP readiness

Your ERP has until 2027. The data inside it needs longer.

The Fawtara dates are fixed, but the integration is rarely what runs late. It is the customer master with missing tax numbers, the credit notes that do not reference their invoice, and the rounding that only shows up when a validator checks every line. This is the plan we work back from.

Which phase are you in

Your date depends on one number.

Pilot

August 2026

The OTA has notified Oman’s top 100 large taxpayers to pilot structured invoicing ahead of the mandatory dates.

Phase 1

1 April 2027

Mandatory for VAT-registered businesses with annual supplies of OMR 5 million or more.

Phase 2

1 October 2027

Mandatory for VAT-registered businesses with annual supplies below OMR 5 million.

What has to come out of your ERP

The data Fawtara actually needs.

Each of these is a field that has to exist, be populated and be correct on every invoice — not just on the ones you test with.

Master data

Tax IDs on both sides

Seller and buyer tax identification numbers on the customer master, not typed into a free-text field at invoice time.

Tax

Line-level breakdown

Tax calculated and carried per line. Header-only tax is the most common reason an ERP needs changes rather than just mapping.

Format

PINT OM output

UBL 2.1 XML or PDF/A-3 to the PINT OM specification — generated by your ERP, a connector, or middleware.

Timing

Real-time posting

B2B is expected in real time. Any process that holds invoices for a nightly batch has to change before go-live.

B2C

QR code

The human-readable B2C invoice carries a QR code, which means the print layout changes too, not just the data.

Corrections

Credit notes that reference

Every credit and debit note needs a clean reference back to the original invoice — usually the hardest data to fix retrospectively.

A plan, worked back from the date

Six steps between now and go-live.

1

Gap analysis

Map every invoice type you issue against PINT OM and list what your ERP cannot produce today.

2

Data clean-up

Fix tax IDs, addresses and item tax codes in the masters. This is the longest step, and it can start before anything else is decided.

3

Choose the architecture and provider

Native ERP module, connector or middleware — and which OTA-accredited service provider sits behind it.

4

Build and map

Generate PINT OM, wire in real-time submission, and write provider status back to the ERP.

5

Test on real volume

Run a month of real invoices through validation, including credit notes, multi-currency and your largest documents.

6

Go live on your phase date

1 April 2027 for Phase 1, 1 October 2027 for Phase 2 — with monitoring in place from the first invoice.

Start here

A gap analysis tells you how much of the list on the left applies to your ERP — usually in a couple of weeks.

E-Invoice Gap Analysis ERP Data Readiness
Traps we have already solved

What went wrong elsewhere, before it goes wrong in Oman.

Five-corner and clearance models fail in the same places. These case studies come from UAE and Saudi rollouts.

Running the UAE as well?

One middleware layer can serve both five-corner countries.

See dsConnectMW →