UAE Updates E-Invoicing Guidelines to Version 1.1 - What Changes on 1 June 2026?

The UAE Ministry of Finance published version 1.1 of the UAE Electronic Invoicing Guidelines on 1 June 2026. This is not a cosmetic revision. The updated document introduces two new appendices that directly affect day-to-day invoicing and document archiving processes for every business operating in the UAE.

Context: Where Does the UAE Stand in Its Implementation Timeline?

The UAE is rolling out mandatory e-invoicing in phases:

• 1 July 2026 — Pilot launch of the system
• 1 January 2027 — Mandatory for businesses with revenue above AED 50 million
• 1 July 2027 — Mandatory for all remaining businesses

Version 1.1 reaffirms clearly that e-invoicing is mandatory for every person conducting business in the UAE, regardless of VAT registration status — unless specifically excluded under Article 4 of Ministerial Decision No. 243 of 2025.

Appendix 4 – Invoice Storage: Liability Always Rests with the Taxpayer

The new Appendix 4 expands on Article 11 of Ministerial Decision No. 243/2025 and introduces several important clarifications with direct implications for businesses using third-party Accredited Service Providers (ASPs).

Key principles:

Responsibility for data storage always rests with the taxpayer, even when archiving obligations are technically delegated to an ASP. Businesses using external e-invoicing platforms cannot transfer their legal liability — they must ensure that data is stored in compliance with requirements and remains accessible to the Federal Tax Authority (FTA) upon request.

Version 1.1 also draws a clear distinction between invoice data and ASP transaction logs. Only the former constitutes tax documentation under UAE law.

The "within the State" requirement — a functional, not geographic interpretation:

This is one of the most significant clarifications in version 1.1. The requirement to store data "within the State" is to be understood functionally rather than geographically. Physical server locations may be outside the UAE, provided that data integrity, security, and full, prompt access for the FTA throughout the required retention period are guaranteed.

This is welcome news for businesses using global cloud platforms — provided their ASP agreements adequately reflect these requirements.

Appendix 5 – Advance Payments and Retention: No More Ambiguity

The second new appendix addresses two scenarios that have generated the most practical questions: advance payments and retention — amounts withheld by a buyer until final acceptance of works or services.

Advance payments:

The principle is straightforward: upon receipt of an advance payment, a tax invoice must be issued for the amount of the advance. The final invoice should cover only the remaining balance — not the total contract value.

Version 1.1 clarifies how to technically link both invoices within the Peppol PINT-AE model. The final invoice can reference the advance payment invoice through the appropriate data fields (IBT-25/IBT-26 or a description in IBT-022). Importantly, the cbc:PrepaidAmount field may be left empty in such a scenario, provided the reference to the advance invoice is clearly identified.

Retention:

Businesses may continue to apply their existing accounting practices, provided they comply with applicable legislation. The guidelines identify two permissible approaches: issuing an invoice for the amount net of retention, and subsequently issuing a separate invoice for the retained amount once it becomes due.

VAT Groups - 24-Month Transitional Period

Version 1.1 also expands the section on VAT groups. Transactions between members of the same VAT group benefit from a 24-month grace period commencing 1 January 2027. The Ministry is explicit that this is a deferral of the obligation — not an exemption from the e-invoicing system. Businesses within VAT groups should begin implementation planning now, bearing in mind that the grace period will expire faster than expected.

What Should Businesses Operating in the UAE Do Now?

The update to version 1.1 signals that the UAE e-invoicing system is taking concrete operational shape. The pilot launches on 1 July 2026 — less than a month from today.

Businesses should take the following steps immediately:

Review ASP agreements for compliance with the archiving requirements introduced in version 1.1 — particularly regarding FTA access guarantees and data integrity when servers are located outside the UAE.

Verify advance payment and retention invoicing processes — does the current ERP configuration correctly handle the Peppol PINT-AE reference fields required to link advance and final invoices?

Plan ahead for VAT groups — systems must be ready to process intra-group transactions before the grace period expires.

Register in EmaraTax and obtain a TIN — the TIN (the first 10 digits of the TRN) is the unique Peppol participant identifier in the UAE. Entities not required to register for VAT but within the scope of e-invoicing must register separately with the FTA to obtain their TIN.

Conclusion

Version 1.1 of the UAE Ministry of Finance guidelines is an operational document, not a declarative one. It answers the specific questions that arise in practice — how to store invoices when operating a global cloud infrastructure, how to correctly invoice advance payments within the Peppol model, and how to handle retention. Businesses that have been treating UAE e-invoicing as a future concern must recognise that the pilot begins in four weeks.

This article was prepared on the basis of the official document "UAE Electronic Invoicing Guidelines V1.1" published by the UAE Ministry of Finance on 1 June 2026. Information reflects the legal and regulatory position as of 2 June 2026.