The Revised UAE E-Invoicing Guidelines (V1.1): What Has Changed and How Businesses Should Prepare

On 1 June 2026, the UAE Ministry of Finance released Version 1.1 of the UAE Electronic Invoicing Guidelines, weeks before the national e-invoicing programme’s pilot begins on 1 July 2026. While the core system remains unchanged, the guidelines bring clarifications affecting business implementation, including a 24-month grace period for VAT group transactions, data storage guidance, and rules for advance payments and retention. This article summarises key changes, the timeline, and practical steps UAE businesses should take now.

A Quick Refresher: Who Is in Scope?

Electronic invoicing is mandatory for anyone doing business in the UAE for all transactions, regardless of VAT registration, unless excluded. It uses the Peppol 5-corner model: the supplier sends invoice data to an Accredited Service Provider (ASP), which validates and converts it into the UAE XML format (PINT-AE), exchanges it with the buyer’s ASP, and reports tax data to the Federal Tax Authority in near real time. Each business must appoint a single ASP for both sending and receiving invoices, with the Participant Identifier based on the 10-digit Tax Identification Number (TIN). B2B and B2G transactions are included; B2C are not. Exclusions include sovereign government activities, certain airline supplies, and VAT-exempt financial services including their zero-rated exports to non-residents.

What Is New in Version 1.1?

1. A 24-Month Grace Period for VAT Group Intra-Group Transactions

The main relief in the updated guidance involves VAT groups. Transactions within the same VAT group remain subject to e-invoicing; they are not excluded for being intra-group. The Ministry and FTA have confirmed a 24-month grace period starting 1 January 2027, during which e-invoicing for intra-group transactions is not mandatory. This impacts only timing; full compliance is required after the period. The relief does not apply to transactions with third parties, which must follow standard timelines. Each group member must be onboarded individually with its own TIN and Peppol ID, potentially using different ASPs.

2. Storage and Archival Obligations Clarified (Appendix 4)

Article 11 of Ministerial Decision No. 243 of 2025 requires electronic invoices, credit notes and associated data to be stored “within the State”. The revised guidelines adopt a pragmatic, outcome-focused interpretation: what matters is that records remain accessible, reproducible and verifiable by the FTA throughout the statutory retention period, irrespective of the geographic location of the servers, databases or cloud solutions used. A business meets the requirement where records are retained in a system that preserves integrity and security, can be produced promptly upon request, and can be retrieved in complete and readable form.

Other key clarifications include:

• Narrow definition of associated data: “Associated data” is limited to information needed to support the integrity, authenticity and auditability of the e-invoice itself — it does not extend to general business documentation.
• Delegation does not transfer liability: Storage may be contractually delegated to an ASP, but the legal obligation under Article 11 remains with the business at all times.
• ASP transactional logs: ASPs must retain transactional logs with unique transaction identifiers covering the end-to-end exchange and reporting cycle; these are the ASP’s operational obligation, distinct from the business’s own record-keeping duty.
• Architecture-neutral: No specific system layer (such as C1/C4) is mandated for storage — any compliant arrangement is acceptable.
• Transmission confirmations: ASPs must inform businesses, on an event-driven basis and without undue delay, when invoices have been successfully transmitted to the Authority.

The underlying retention periods remain those of the Tax Procedures Law: 5 years for Taxable Persons (7 years for real estate records), extended by 4 years in the event of disputes or audits, and by 1 year where a voluntary disclosure is submitted in the fifth year.

3. Advance Payments: Invoice at Receipt, Final Invoice for the Balance (Appendix 5)

A new appendix clarifies rules around advances. When a business receives an advance, it must issue a tax invoice upon receipt. The final invoice should only cover the remaining balance, not the full contract value, since tax has already been invoiced for the advance. References to the original advance invoice can be included in the reference fields or as a note, and the cbc: PrepaidAmount field can be left blank. For example, on a AED 10,000 contract plus 5% VAT with a AED 1,000 advance, the advance invoice shows AED 1,000 plus AED 50 VAT, and the final invoice shows AED 9,000 plus AED 450 VAT, referencing the advance invoice. Businesses with deposit-heavy revenue models should reconfigure their ERP billing logic.

4. Retention Arrangements in Contracts

For contracts with retention, businesses can continue existing commercial and accounting practices if VAT-compliant. The guidelines endorse a two-invoice approach: an electronic invoice for the payable amount after retention adjustment, and a separate invoice for the retained amount when the buyer is liable to release it. Payment terms should be accurately reflected in e-invoices, and milestone or retention calculations should be in a separate commercial document, not on the e-invoice.

The Implementation Timeline at a Glance

The pilot programme begins on 1 July 2026 by invitation, and any business, regardless of revenue, may adopt e-invoicing voluntarily from that date, with penalties applying only from its mandatory date. The mandatory phases are:

Revenue is measured as gross income for the most recent accounting period, as reported in the financial statements. For larger businesses, the first hard deadline is now less than two months away: an ASP must be appointed by 31 July 2026.

Penalties for Non-Compliance

Cabinet Decision No. 106 of 2025 outlines penalties for e-invoicing violations, complementing existing VAT and Tax Procedures penalties. Notably, penalties do not apply to voluntary invoices before the mandatory date, encouraging early adoption and testing.

Five Actions to Take Now

1. Confirm your go-live date. Map your entity’s revenue against the phased thresholds and, for VAT groups, factor in the intra-group grace period while planning third-party transaction compliance.
2. Select and contract with an ASP. Review the Ministry’s list of Accredited Service Providers, finalise commercial terms, and initiate onboarding through EmaraTax. If you are above the AED 50 million threshold, you must complete this by 31 July 2026.
3. Run a data gap analysis. Test whether your ERP can generate all mandatory PINT-AE data points, including tax categories, beneficiary details for Free Zone scenarios, AED tax-accounting values for foreign-currency invoices, and the predefined endpoints for non-onboarded buyers and exports.
4. Reconfigure billing for advances and retention. Align invoicing workflows with the Appendix 5 treatment, tax invoice at receipt of advance, balance-only final invoices with preceding-invoice references, and the two-invoice retention model.
5. Review storage and ASP contracts. Ensure your ASP agreement addresses storage delegation, data security, transmission confirmations and service-disruption protocols — remembering that legal responsibility for retention never shifts away from your business.

How Alpha Equity Consultancy Can Help

Alpha Equity Consultancy LLC, as FTA-registered tax agents, supports businesses in e-invoicing readiness, from impact assessments and ASP selection to ERP data reviews, VAT group structuring during the grace period, and post-go-live compliance with Corporate Tax, VAT, and Excise Tax. The voluntary window from July 1, 2026, offers a risk-free opportunity to test systems; businesses using it will approach January 2027 confidently.

To discuss your e-invoicing readiness, contact our team through www.alphaequitymc.com.

Disclaimer: This article is provided for general information purposes only and does not constitute tax, legal or professional advice. Readers should obtain advice specific to their circumstances before acting. References are to the UAE Electronic Invoicing Guidelines V1.1 (Ministry of Finance, 1 June 2026), MD No. 243 and 244 of 2025, and CD No. 106 of 20