Cabinet approved the draft e-invoicing law and its executive regulations on 6 May 2026. The General Tax Authority has not yet said which model, which format, or which taxpayers go first. That leaves a window — and most of the work that makes go-live hard does not depend on the answers.
Every e-invoicing mandate in the region has followed one of three shapes. Qatar will very likely pick one of them — and each asks different things of your ERP.
| Clearance | Five-corner exchange | Post-audit reporting | |
|---|---|---|---|
| Regional example | Saudi Arabia (ZATCA) | UAE, Oman (Peppol) | Philippines (BIR EIS) |
| Invoice valid when | The authority clears it | Issued and exchanged via providers | Issued; data reported after |
| Who connects to the authority | You, directly | Your accredited provider | You, directly |
| Hardest part for the ERP | Real-time dependency at posting | Provider routing and status write-back | Complete, on-time data transmission |
Which model Qatar adopts is not yet confirmed. This table describes the regional options, not a prediction of the GTA’s choice.
All six of these are needed under every model above, so none of them is wasted if the spec surprises you.
Customer and supplier tax numbers held as structured fields, validated, and complete — not typed into free text at invoice time.
Tax calculated and stored per line. Every regional model validates at line level; header-only tax is the most common rebuild.
The approved regulations explicitly cover electronic credit and debit notes. Each one needs a clean link to the invoice it corrects.
Unique, sequential invoice numbering per entity and branch, with no manual overrides.
Middleware between the ERP and the authority absorbs whichever format and channel the GTA chooses, without touching the ERP twice.
Name the owner for tax data quality now. Every rollout in the region slipped where that role was missing.
Unlike Saudi Arabia, the UAE and Oman, Qatar has not introduced VAT. Its e-invoicing law therefore arrives without the VAT reporting machinery the other three built on, which makes it harder to predict exactly what tax data the GTA will want on each document — and is one more reason to keep the integration layer flexible rather than hard-coding a neighbour’s format.
Confirm Qatar’s current tax position against GTA publications before relying on this.
A gap analysis against the regional models tells you how much of the list above applies to your ERP.
E-Invoice Gap Analysis Compare with the GCC