E-Invoicing, UAE
UAE Electronic Invoicing Guidelines: Scope, Roles & Readiness
The UAE Ministry of Finance's Electronic Invoicing framework is designed to strengthen digital infrastructure, improve tax compliance and increase operational efficiency. For businesses, the transition requires structured data, system integration, clear responsibilities, reliable master data and readiness to exchange invoices through an Accredited Service Provider.
This guide follows the supplied UAE Electronic Invoicing Guidelines, covering the framework, scope, exclusions, rollout, record retention, invoice categories, key scenarios and tax categories.
Scope and purpose
The guidance is relevant to commercial businesses, government entities, and tax and technology advisers. Electronic Invoicing applies to persons conducting business in the UAE unless specifically excluded under the applicable decisions.
- Implementation follows a phased rollout.
- The Participant Identifier uses the Tax Identification Number (TIN); the supplied guidance describes the TIN as the first 10 digits of the TRN.
- Entities without a TIN may need to obtain one through the Federal Tax Authority.
- Members of a Tax Group use their individual TINs for Electronic Invoicing purposes.
Essential terminology
| Term | Business meaning |
|---|---|
| 5-Corner Model | Decentralized exchange model involving the supplier, supplier's ASP, buyer's ASP, buyer and FTA. |
| Accredited Service Provider | A service provider accredited by the Ministry to facilitate Electronic Invoicing. |
| Electronic Invoice | A structured XML document issued and transmitted through the Electronic Invoicing System for automated processing. |
| Peppol | The interoperability framework adopted for the UAE Electronic Invoicing model. |
| UUID | A unique 128-bit identifier generated in the Electronic Invoicing System in addition to the sequential invoice number. |
UAE Electronic Invoicing framework
The supplied guidance describes a decentralized 5-corner model based on Peppol PINT-AE specifications. Electronic Invoices are structured XML documents rather than conventional PDF invoices, and the framework does not rely on QR codes as the core exchange mechanism.
- The supplier creates the invoice data and submits it to its ASP.
- The supplier's ASP validates and, where required, converts the data into the structured format.
- The invoice is exchanged with the buyer's ASP through the network.
- Relevant tax data is reported to the FTA.
- The buyer's ASP validates and delivers the Electronic Invoice to the buyer.
Record retention
| Record holder or situation | Retention period stated in the supplied guidance |
|---|---|
| Taxable Persons | 5 years from the end of the relevant Tax Period. |
| Persons other than Taxable Persons | 5 years from the end of the calendar year in which the document was created. |
| Real estate records | 7 years from the end of the calendar year in which the document was created. |
| Dispute or ongoing audit | An additional 4 years for relevant data, as described in the supplied guidance. |
Scope in specific business scenarios
- The stated transaction scope includes B2B, B2G, G2B and G2G transactions; B2C and G2C consumer supplies are described as outside scope.
- Transactions between members of the same VAT group remain within the overall scope of Electronic Invoicing.
- Where a non-resident person must issue a Tax Invoice under the VAT Decree-Law, the guidance states that it must be issued as an Electronic Invoice.
Exclusions from Electronic Invoicing
- Certain sovereign activities of Government Entities that do not compete with the private sector.
- Specified airline supplies and goods documentation described in the guidance.
- Specified exempt financial services and the treatment described for certain zero-rated exports to non-residents.
- Any other activities or categories determined by the Minister.
Phased implementation
The supplied material describes voluntary participation for invited participants from July 2026, followed by mandatory implementation based on annual revenue and Government status.
| Entity type | Annual revenue | ASP appointment | Implementation |
|---|---|---|---|
| Person | AED 50 million or more | 31 July 2026 | 1 January 2027 |
| Person | Below AED 50 million | 31 March 2027 | 1 July 2027 |
| Government | N/A | 31 March 2027 | 1 October 2027 |
Electronic Invoice categories
- Electronic Tax Invoice
- Electronic Tax Credit Note
- Self-billed Electronic Tax Invoice
- Self-billed Electronic Tax Credit Note
- Commercial Invoice
- Electronic Credit Note
Key Electronic Invoice scenarios
Include relevant beneficiary details where required; commercial invoices may apply.
The guidance describes special buyer electronic-address and ASP reporting considerations.
The VAT amount need not be displayed for the described scenario.
Validation considerations apply; an Electronic Credit Note is used where the total payable is negative.
Retention amounts and milestones may require separate commercial documentation and later invoicing.
A Tax Invoice is issued electronically, with a fallback endpoint where the overseas buyer has no Peppol ID.
Tax categories
- Standard Rate: taxable supply at 5% VAT.
- Exempt from VAT: in-scope supply treated as exempt.
- Out of Scope: transactions outside UAE place-of-supply rules or applicable exclusions.
- Reverse Charge: domestic supplies of specified goods.
- Zero Rated: supplies subject to 0% VAT, such as qualifying exports.
- Margin Scheme: VAT calculated on the margin.
Practical readiness priorities
- Confirm whether each legal entity and transaction type is in scope.
- Validate TIN, TRN, legal names, addresses and participant identifiers.
- Map ERP, CRM, warehouse and other source data to required structured fields.
- Document responsibilities between the business and its ASP.
- Review self-billing, Free Zone, export, deemed-supply, margin-scheme and continuous-supply scenarios.
- Plan end-to-end testing for creation, validation, transmission, receipt, reporting, rejection and correction.
- Maintain a regulatory change log so implementation dates and technical specifications remain current.
For a business-focused risk assessment, read UAE e-invoicing practical business challenges. For Oracle Fusion implementation planning, see the UAE readiness, timeline and ASP guide.