Qatar's Cabinet approved the e-invoicing law on 6 May 2026. A phased mandate is expected from 2027 — but the General Tax Authority has not yet published a technical specification. Here is what is settled, what is not, and what you can usefully do now.
Sourced from the Cabinet announcement of 6 May 2026. Rows marked as expected are commentary, not published policy.
Most Qatar e-invoicing content states a technical model as though it were policy. It is not. Keeping the two apart is the difference between preparing and guessing.
The Cabinet release specified no technical model, clearance flow, architecture or platform. Every item in this column is inference from regional precedent.
This is the part most guides get wrong. Saudi Arabia, the UAE, Bahrain and Oman all introduced VAT first and e-invoicing afterwards. Qatar is doing it the other way round: the e-invoicing law is approved, and VAT is not yet in force.
It reads as deliberate. Reporting infrastructure built ahead of a tax gives the authority transaction-level visibility from the day that tax begins, rather than years later. If you are planning on the assumption that Qatari e-invoicing will simply mirror ZATCA, the missing VAT layer is the first place that assumption breaks.
The practical consequence: scope will not be defined by VAT registration, because there is no VAT register yet. How Qatar draws the boundary instead is one of the more consequential things the executive regulations will settle.
None of this depends on the specification, and all of it takes longer than the integration.
Legal names, addresses and tax identifiers for every customer and supplier. Validation rejects on this long before it rejects on anything clever.
If your ERP can only produce a PDF, that is the real project. Structured output is required under every model Qatar might choose.
Scope, categories and correction handling are tax judgements, not integration work. Who should own it.
Nobody can supply one — the specification does not exist. Any vendor selling Qatar compliance today is selling an expectation.
If you invoice into Saudi Arabia, the UAE or Oman, those mandates are live now and Qatar's will sit alongside them.
What matters is how quickly a country profile lands after publication. GoRoute passed Oman's full PINT OM suite and was accredited within weeks.
We are not going to tell you we are Qatar-compliant. No one can be: the General Tax Authority has not published a specification, so there is nothing to be compliant with.
What we can say is how we handled the last one. For Oman's Fawtara programme we built the validator against the published Schematron, passed the full OpenPeppol PINT OM conformance suite, and became an OTA-accredited service provider in July 2026. The platform already runs a certified Peppol Access Point and SMP, generates country tax documents, and validates against national rule sets.
If Qatar lands on a Peppol-based or clearance model, that work transfers. If it lands somewhere unexpected, the same team that read a Schematron and shipped against it will read Qatar's and do it again. Judge providers on that, not on a compliance badge for a specification nobody has seen.
Get the groundwork done while the specification is still being written.
Not yet. Qatar's Cabinet approved the draft e-invoicing law and its executive regulations on 6 May 2026, but the law still requires Shura Council review and the Amir's assent before publication in the Official Gazette, expected later in 2026. A phased mandate is widely expected to begin around 2027, starting with large taxpayers. No obligation applies to any business today.
No go-live date has been officially confirmed. Commentary consistently points to a phased rollout from around 1 January 2027, beginning with large enterprises and expanding to smaller businesses. Treat any specific date you see quoted, including that one, as an expectation rather than a published deadline.
This has not been confirmed. The Cabinet announcement of 6 May 2026 did not specify a technical model, exchange architecture, clearance flow or format, and the General Tax Authority has not published a specification. A Peppol-based model is plausible given regional precedent, but anyone stating it as fact is inferring from Saudi Arabia and the UAE, not citing Qatar.
No. Qatar has signed the GCC VAT Framework Agreement but has not implemented VAT, and the General Tax Authority has not confirmed a launch date. This makes Qatar unusual: the e-invoicing law arrived before the tax it will eventually support. Most regional authorities built reporting infrastructure first, so the sequence is deliberate rather than surprising.
Work on what will be required under any model. Clean up customer and supplier master data, make sure your ERP can emit a structured invoice rather than a PDF, identify which entities and transaction types would be in scope, and decide who owns the tax decisions. None of that depends on the specification, and all of it takes longer than the integration itself.
