Advance Payments and Deemed Supplies: The Two Oman E-Invoicing Triggers Your ERP Will Miss

The short answer

Under the amended Article 143, an electronic tax invoice is required on four events. Two of them are routinely absent from ERP configurations built for paper:

• Receiving consideration, wholly or partly, before the date of supply — deposits, prepayments, staged payments, retainers
• Deemed supplies — which in most paper processes produce no invoice at all

Both become mandatory on your wave date: 1 April 2027 above OMR 5m, 1 October 2027 below. Neither is a formatting change. Both are changes to when your system creates a document, which is a far deeper piece of configuration work than adding a new output format.

Why these two are the ones that bite

The other two triggers in Article 143 — ordinary supplies, and any other case in the Regulations — describe events your ERP already invoices. You are changing the format of a document you already produce.

These two are different. You are producing a document that does not currently exist.

That distinction decides how long the project takes. Re-formatting output is a connector task. Creating a document at a new point in the process touches order management, the receipts workflow, revenue recognition, the numbering sequence and the VAT return reconciliation. It needs analysis, configuration and testing — and it needs finance and IT in the same room.

Advance payments: the sequence that is about to break

The common pattern today:

1. Customer pays a 30% deposit → receipt issued
2. Goods delivered three months later → tax invoice for the full amount
3. VAT accounted at delivery

From your wave date, step 1 requires an electronic tax invoice for the consideration received. The receipt is no longer sufficient.

Three consequences worth planning for:

Your invoice count rises. Every staged payment becomes a document. A project business billing in four stages issues four tax invoices where it previously issued one, plus the final settlement. That affects volume-based pricing, archival, and any manual review step in the chain.

Double taxation becomes a live risk. If the deposit was invoiced with VAT and the final invoice is raised for the gross amount without netting the prepayment, you have declared output VAT twice. This is the single most common defect we would expect to see in the first months of a prepayment-heavy rollout, and it is the specific thing to test in sandbox.

Cancellations need a credit path. A cancelled order that was invoiced at deposit stage now needs a credit note, not a quiet refund of a receipt.

Deemed supplies: documents where there were none

A deemed supply is treated as a supply for VAT even though it is not an ordinary sale — the classic case being goods or services taken for personal or non-business use. Article 143 spells this out on the ordinary-supplies limb too, covering supplies "to a taxable person allocating the supplies for personal use".

In most finance functions today this is a journal entry and a line on the VAT return. There is no invoice, no number, and nothing to submit.

From your wave date it needs a document with a unique number, in the approved electronic format, retained like any other. Practically that means deciding who the document is addressed to, what triggers its creation, and where it sits in your numbering sequence — none of which your ERP will decide for you.

What to do, in order

1. List every point where money arrives before a supply. Deposits, retainers, milestone billing, subscriptions billed in advance, customer credit on account.
2. List every deemed supply you currently handle as a return adjustment. If it only exists in a spreadsheet at quarter end, it needs an owner.
3. Decide the netting rule for prepayments and write it down before configuring anything. This is where double-taxed VAT comes from.
4. Extend your numbering scheme. One unique number per invoice, across every issuing point, including the new documents.
5. Test both flows end to end in a sandbox, including a cancellation and a credit note. Not the happy path.
6. Reconcile a full period — the documents you issued against the VAT you declared — before your wave date, not after.

Where this sits in the wider mandate

These are the transaction-level triggers. Two other parts of the same decision affect scope: simplified and B2C invoices run on the same clock, and Article 143 bis 1 places security and continuity obligations on your systems rather than your documents.

For the exchange mechanics underneath all of it, see the Fawtara five-corner model and the Tax Data Document deep dive.

If you want the ERP side scoped rather than guessed, the Peppol API documentation covers the integration surface, the Oman page covers the rules, and you can book a session to walk your prepayment flows with our Oman team before you configure anything.

Sources

• Decision of the Chairman of the Tax Authority No. 189/2026, amended Article 143
• Oman Tax Authority and the Fawtara portal