XML, not PDF
Electronic Invoices use the UAE PINT-AE XML standard. A PDF, scan, Word file, image, or email by itself is not an eInvoice.
LexaBillsOfficial guidance, made practical
This summary distils the Ministry of Finance Electronic Invoicing Guidelines, Version 1.1 dated 1 June 2026. It helps businesses understand the framework, scope, data, responsibilities, and practical preparation steps.
The essential change
It is issued, transmitted, and received through the Electronic Invoicing System in a machine-readable format that supports automatic processing.
Electronic Invoices use the UAE PINT-AE XML standard. A PDF, scan, Word file, image, or email by itself is not an eInvoice.
Each in-scope person appoints one Accredited Service Provider for both sending and receiving Electronic Invoices.
Your participant identifier is 0235 + your 10-digit TIN. For registered taxpayers, the TIN is the first 10 digits of their own TRN.
The structured XML Electronic Invoice does not feature a QR code or barcode under this framework.
The five-corner model
The supplier and buyer use their respective ASPs. Both ASPs validate and exchange the invoice, while required Tax Data is reported to the FTA.
The compliance obligation remains with the supplier, or with the buyer for self-billed invoices, even where an ASP performs the technical exchange.
Who and what are in scope
The obligation generally applies to any person conducting business in the UAE for in-scope transactions, unless a specific exclusion applies.
A person can be in scope even if they are not VAT registered. A person without a tax registration may need to register with the FTA to obtain a TIN.
Use the first 10 digits of your own TRN, not the Tax Group representative’s TRN. Intra-group business transactions are not automatically excluded.
Examples include qualifying sovereign activities, certain airline transactions, and exempt financial services. Each exclusion has conditions and should be reviewed carefully.
Phased implementation
Voluntary implementation began on 1 July 2026. Mandatory implementation follows the official phased timetable.
The June guideline shows 31 July 2026 for large businesses to appoint an ASP. A later Ministry amendment extended that appointment deadline to 30 October 2026. The mandatory implementation date remains 1 January 2027.
For businesses in scope, the mandatory date depends on annual revenue. The deadline to appoint an Accredited Service Provider (ASP) comes first.
Appoint an ASP by .
Mandatory E-Invoicing begins .
Appoint an ASP by .
Mandatory E-Invoicing begins .
Businesses with annual revenue of AED 50 million or more must appoint an Accredited Service Provider by 30 October 2026. Mandatory E-Invoicing begins on 1 January 2027 for in-scope businesses and transactions.
Yes, if the business and its transactions are in scope. Revenue below AED 50 million determines the later business timetable; it is not, by itself, an exemption. B2B and B2G transactions are generally covered, subject to the stated exclusions. The revenue threshold is annual business revenue, not invoice count.
Sources checked 15 September 2026: Ministerial Decision 244 of 2025 · amending Decision 66 of 2026.
Peppol is a framework for exchanging structured electronic documents between connected participants. The UAE E-Invoicing framework uses OpenPeppol standards, with Accredited Service Providers handling the exchange. Choosing invoicing software does not by itself make a business or its software provider an accredited access point. Read the Ministry's framework explanation.
Use the UAE E-Invoicing readiness checklist · Compare LexaBills pricing
Practical readiness path
The official guide groups preparation into understanding the rules, selecting an ASP, testing, and going live.
Confirm scope, deadline, applicable scenarios, tax categories, penalties, and the changes needed in your accounting or invoicing process.
Choose an accredited provider, complete commercial arrangements, initiate onboarding through EmaraTax, and obtain your Peppol participant identifier.
Identify mandatory data points, buyer and supplier identifiers, tax categories, invoice scenarios, and any ERP or accounting-system changes.
Test invoice transmission, validation, confirmations, tax reporting, security, and the end-to-end buyer experience with your ASP.
Define oversight, error resolution, service-disruption procedures, security responsibilities, and support before production exchange begins.
Data, tax, and retention
Each transaction needs the correct category: standard rate, exempt, outside the scope of VAT, domestic reverse charge, zero-rated, or margin scheme.
Electronic Credit Notes support reductions and cancellations. Extra fields may apply to Free Zones, exports, self-billing, agents, e-commerce, and other special scenarios.
Generally five years for taxable persons, five years for other persons, and seven years for real-estate records, subject to extensions under tax law.
Records must remain complete, readable, secure, and promptly retrievable by the FTA. Delegating storage to an ASP does not transfer the legal obligation.
E-Invoicing penalties apply from your mandatory implementation date. The guide states that voluntary eInvoices issued before that date are not subject to E-Invoicing penalties, although other tax obligations still apply.
Read the source
This page is a practical summary, not a substitute for the legislation, the full guideline, or professional advice.
Turn the checklist into a plan
We will guide your company from account verification to the operating model that fits your systems and invoice volume.