E-invoicing in Qatar: what is public and what is not

Where things stand

Qatar's Council of Ministers has approved a draft e-invoicing law together with its implementing regulations. Both EY and KPMG report that the draft was prepared by the Ministry of Finance with the General Tax Authority (GTA). It is a draft: it still has to go through the Shura Council and be enacted by the Amir, so it does not yet bind anyone.

EY reports that the GTA has been running a pilot with a select group of large entities. EY also expects the model to resemble Saudi Arabia's: clearance for business-to-business and business-to-government invoices, and reporting for business-to-consumer invoices. The start date and the order in which businesses join are not confirmed; the date that has been mentioned is listed in the box below and is anticipated, not confirmed.

What a vendor reports about the pilot (unverified)

A software vendor, ClearTax, publishes a guide that says it draws on GTA pilot material. We found no e-invoicing material on the GTA website itself, so everything in this section is a vendor's report that we have not been able to check against a primary source. Treat it as a hint about direction, not as a specification.

• Documents are reported to be UBL 2.1 XML restricted by Qatar-specific business terms and rules in a GTA data dictionary, with a cryptographic stamp, a hash chain linking each document to the previous one, and a QR code.
• Submission is reported to run through the GTA's own central platform and its APIs, not through the Peppol network.
• Standard invoices are reported to be cleared before the buyer receives them, and simplified (consumer) invoices reported within a short window after issue.
• Arabic is reported to be mandatory on the document, with an optional second language after it.
• Each invoicing device is reported to be onboarded through a portal by the business's own administrator, and a free GTA solution is reported for micro and small entities.

What is not known

As far as we can tell, the following are not published by the GTA: the technical specification and field list, which businesses and transactions are in scope and in which order, retention periods, and penalties. Fiscalane does not implement, label or guess any Qatar file format, field name or interface, and its Qatar tool is not connected to any government system.

Qatar has no VAT in force according to our research (the GTA website lists income, capital gains, withholding, excise and global minimum tax). E-invoicing in Qatar is therefore about transparency and tax administration, not VAT compliance, and nothing here should be read as VAT advice.

What Fiscalane offers today, and what it does not

The Qatar readiness check reads an invoice export in your browser and tests it against Fiscalane's own hypothesis rules, such as complete seller and buyer details, Arabic names, sequential numbering and consistent line totals. A good result means your data is complete against those rules. It does not mean the GTA will accept your invoices, and Fiscalane is not a Peppol access point, not certified and not a GTA gateway.

Because Arabic is reported to be mandatory, bilingual Arabic and English documents are a core need. The Fiscalane invoice editor can produce a bilingual invoice document.

What to prepare without guessing

None of this depends on a specification that has not been published.

• Clean master data: customer and supplier legal names in Arabic and English, commercial registration numbers and tax identifiers where you have them.
• One unbroken numbering series per document type, with a written rule for voided invoices and credit notes.
• Know which system issues your invoices and whether it can export every invoice, including credit notes, with line detail.
• Decide who owns the archive and who would file or submit invoices once the rules exist.
• Watch the GTA website for the pilot and technical information, and test your data against any specification only after it is published.