Odoo e-invoicing in Qatar
The Qatar e-invoicing picture in full: the scheme, the authority behind it, who it binds, and every requirement we map before a build is quoted.
Electronic invoicing law (draft). No branded scheme name has been published yet, unlike Saudi Fatoora or Egypt's e-invoice portal.
Authority: General Tax Authority (GTA), with the Ministry of Finance. Existing tax filings already run through the GTA's Dhareeba portal.
Qatar's Cabinet approved a draft e-invoicing law and its executive regulations on 6 May 2026. Nothing is in force: no scope, no technical specification and no start date have been published as of 22 August 2026.
Nobody yet. The draft law gives the GTA power to require e-invoicing for named taxpayers and transaction types, but those categories have not been published. Do not plan a build against a scope that does not exist.
Every requirement, in full
3 requirements. Each one has to end up as a field, a document layout, a stored response, or an API call in your Odoo build. This is the list an e-invoicing project in Qatar gets costed against.
- 1 Not yet defined. KPMG's read of the approved draft is that it will set rules for issuing, storing and transmitting e-invoices and related credit and debit notes, and create a database for GTA oversight.
- 2 No format, no clearance-versus-reporting decision, no QR rule, no signature or seal rule, and no accredited service provider list have been published. Anyone quoting these today is guessing.
- 3 What is real today: tax returns, withholding tax statements and contract notifications must be filed electronically in Dhareeba, and financial statements filed with the tax return must be in Arabic.
Checked Localization notes on this page checked on 22 August 2026.
Rates, formats, thresholds and submission windows change. We configure against the rules in force at build time and confirm every figure with your accountant or tax advisor before sign-off. If a rule moves after go-live, it is a support ticket, not a rebuild. Read more on our Odoo localization service.
How we build e-invoicing for Qatar
The delivery method behind the list above. The same four steps on a 10-user rollout and on a multi-company programme, with the depth scaled to the scope.
- 1 Requirements first, code second. Each line above becomes a field, a report, or an API call on a written mapping sheet. Anything with no home in Odoo is quoted as a build before the project starts.
- 2 Numbering is settled on day one. Invoice sequences are the part that breaks quietly and costs the most to unwind after go-live, so they are signed off before the first test document.
- 3 Submission runs from a queue. Retries, idempotency keys, stored responses and an audit trail. A failed send becomes a ticket with evidence, not a missing invoice you find at month end.
- 4 Your finance team signs it off. Real documents, in a test database, checked with your accountant or tax advisor before cutover, with a rollback plan in writing.
What we need from you to quote it
Bring these to the first call and you get a scoped, priced e-invoicing plan for Qatar instead of a range.
- โ Your tax registration details and the entity each one belongs to.
- โ A sample of every document type you issue: invoice, credit note, debit note, self-billing if you use it.
- โ Any registration, certificate or portal credential the authority has already issued you.
Services behind this work
The rest of the Qatar localization detail
Each topic has its own page with the full item list, the same way this one does.
E-invoicing in other markets we cover
Running the same rollout across borders? These pages carry the same depth for each market, so you can compare before scoping a multi-country phase.
Scope e-invoicing for your Qatar rollout.
Send us the list above with your answers against it. We come back with what is configuration, what is a connector, and what is a build, priced before the project starts.