Qatar e-invoicing is moving from pilot to law. The General Tax Authority (GTA) has completed a pilot with selected large entities, and the Cabinet approved a draft law with executive regulations on 6 May 2026. That law is not yet enacted. Here is the verified position, and the groundwork worth starting now.
Key Takeaways
- Cabinet approved the draft law & executive regulations on 6 May 2026. It has not been officially gazetted, so no obligation binds yet.
- Documents move through GTA's Central Platform as UBL 2.1 XML. A PDF, scan or OCR copy is not an e-invoice.
- The pilot ran two models: Standard invoices through clearance, simplified invoices through reporting within 24 hours. The final decision will be approved in the law.
- Standard invoices need clearance before reaching the buyer; simplified invoices are reported within 24 hours.
- GTA's pilot deck indicates a January 2027 rollout, though waves and segment dates are yet to be confirmed.
- As of date, Qatar has not yet introduced VAT.
E-invoicing in Qatar means issuing, validating, exchanging and storing invoices, credit notes and debit notes as structured XML through GTA's Central Platform. Three controls travel with every document: a cryptographic stamp, a QR code, and the hash of the previous invoice from that device.
That last control does the heavy lifting. Each document points back to the one before it, so deleting or backdating an invoice breaks a visible chain. For a device's first invoice, the hash is the public key hash issued at onboarding. Unstructured PDFs, images, HTML invoices in emails, OCR-scanned paper and faxes are not electronic documents.
Timeline | Milestone |
January 2027 | Countrywide rollout as per GTA material |
May 2026 |
|
Late 2025 | Proof of Concept; PoC SDK, Data Dictionary v1.0 |
Treat January 2027 as a programme plan. GTA has said waves and segment go-live dates will be set in the Law and Executive Regulations.
Build towards the below. None of it is binding law yet, because the approved draft has not been gazetted.
Note: No retention period appears in any Qatari official source, so business should wait for the official law and regulations in that regard.
Six document types are confirmed. Each device must submit one sample of every type, in both flows, to pass conformance testing.
Document type | Buyer details | Pilot submission flow |
Electronic Invoice | Required | Clearance |
Electronic Credit Note | Required | Clearance |
Electronic Debit Note | Required | Clearance |
Simplified Electronic Invoice | Not required | Reporting |
Simplified Electronic Credit Note | Not required | Reporting |
Simplified Electronic Debit Note | Not required | Reporting |
Transaction types layer on top: third-party, export, import, self-billed, summary and continuous supply.
Scope is yet to be published. GTA has confirmed only that covered transactions, whether B2B, B2G or B2C, will appear in the executive regulations. The pilot drew on selected large entities, pointing to bigger businesses entering first.
Device coverage is clearer. Anything issuing an invoice must be onboarded: ERP, POS terminal, billing server or invoicing application. Retailers may onboard each POS, or route everything through one central system and onboard only that. Qatar Financial Centre (QFC) entities sit under a separate regime and should confirm with the QFC Tax Department.
Requirement | Specification |
Format | UBL 2.1 XML, restricted by Qatar Business Terms and Rules |
Platform | GTA Central e-Invoicing Platform, REST APIs |
Language | Arabic mandatory, secondary after a pipe |
Authentication | Device certificate after conformance |
Cryptography | SHA-256 hashing; key pair on ECDSA-P256K1 |
Chaining | Previous Document Hash on every document |
QR code | Required on customer-facing documents |
Readable copy | PDF/A-3 customer copy with the stamped XML embedded and sealed is required once the regime goes live |
Reporting window | 24 hours from issuance |
Retention, penalties | Not published |
Platform cost | No licence fee, free solution for micro & small entities |
Step by step e-invoicing process in Qatar:
Qatar runs two flows side by side, placing it among continuous transaction control regimes.
Aspect | Clearance | Reporting |
Applies to | Standard invoices, Credit & Debit Notes (CDNs) | Simplified invoices & CDNs |
GTA validation | Before issuance | Not required to issue |
Timing | Real time | Within 24 hours |
Buyer receives | Platform-validated document | Seller's document, reported afterwards |
GTA's pilot specifications define a Qatar-specific document identifier, and submission runs through GTA's own Central Platform APIs rather than the Peppol network. Qatar does not appear among the Peppol Authorities listed by OpenPeppol.
e-Invoicing penalty schedule has not yet been published. What the design already implies is commercial, not just fiscal. A document that fails clearance cannot be legally issued until you fix it, which stalls the receivable as much as the tax position. A device without a valid certificate cannot issue invoices at all. And counter gaps or broken chains surface directly to GTA.
ClearTax runs as middleware, keeping compliance logic out of your ERP.
Qatar e-invoicing draft law along with executive regulations has been approved by its Cabinet, sitting on top of a completed GTA pilot and a published Data Dictionary. That gap is your preparation window, not a reason to wait. Clean your master data, confirm your invoicing devices, and test UBL 2.1 output now, so that a gazetted law becomes a switch-on rather than a scramble.
As a qualified Chartered Accountant with extensive expertise in accounting, finance, taxes, and audit, I specialise in simplifying complex regulations for a broader audience. Well-versed in tax laws across India and the GCC region, I have a keen interest in the evolving finance ecosystem. Passionate about learning, I enjoy engaging in conversations, exploring new cultures through travel, and unwinding with music.. Read more