What Has Changed in the June 2026 UAE E-Invoicing Guidelines?
The Ministry of Finance has issued an updated version of the UAE Electronic Invoicing Guidelines, moving from Version 1.0 dated 23 February 2026 to Version 1.1 dated 1 June 2026.
The core e-invoicing framework remains the same: the UAE continues to follow a 5-corner model, where invoices are exchanged between suppliers and buyers through Accredited Service Providers, while tax data is reported to the Federal Tax Authority. However, the June version introduces important new guidance through two additional appendices:
- Appendix 4: Further guidance on storage obligations under Article 11 of Ministerial Decision No. 243 of 2025
- Appendix 5: Clarification on advance payments and retention for PINT AE purposes
New Clarification on Storage Obligations Under Article 11
One of the most important additions in the June version is the detailed clarification on how electronic invoices, electronic credit notes and related data must be stored.
The updated guidance confirms that the legal obligation to retain e-invoicing records remains with the Person subject to the Electronic Invoicing System. This means that businesses must ensure that their electronic invoices, electronic credit notes and associated data are retained for the legally required period and can be made available to the Authority when requested.
From a practical perspective, this clarification is important because many businesses will rely on ASPs, cloud platforms or ERP-connected storage solutions. The update makes clear that outsourcing storage does not remove the taxpayer’s responsibility.
ASPs Must Retain Transactional Logs and Technical Traceability Records
The June guideline also introduces more detail on the operational responsibilities of Accredited Service Providers.
ASPs are expected to retain transactional logs for each transaction. These logs are not the same as the invoice content itself. Instead, they are technical records that support traceability across the full e-invoice exchange and reporting cycle.
In practice, these logs should allow the ASP to demonstrate how an invoice moved through the system, including identifiers, transmission status and routing information. The guidance also clarifies that these technical logs form part of the ASP’s operational and compliance obligations.
Delegating Storage to an ASP Is Allowed, but Responsibility Remains with the Business
Another important point is the clarification that businesses may contractually appoint an ASP to store electronic invoices, electronic credit notes and associated data on their behalf.
However, this delegation does not transfer the legal retention obligation. The business remains ultimately responsible for ensuring that the records are preserved and can be produced when required.
This means that ASP contracts should not only cover invoice exchange and reporting. They should also address storage scope.
For businesses, this is a clear reminder that e-invoicing compliance is not just a transmission project. It is also a long-term data governance and recordkeeping project.
Greater Flexibility on Storage Architecture
The June version also provides useful flexibility on where and how e-invoicing records may be stored.
The guidance clarifies that storage does not have to take place at a specific system layer, such as Corner 1 or Corner 4. Any storage arrangement may be acceptable, provided that the required records are retained for the statutory period, the integrity and security of the data are maintained, and the records can be provided to the Authority when requested.
This is a practical clarification for businesses using cloud infrastructure, ERP-integrated archiving, ASP-hosted storage, or hybrid models. The focus is not on the exact technical layer where the data sits, but on whether the storage arrangement preserves compliance, accessibility, integrity, and auditability.
ASPs Must Provide Transmission Confirmations Without Undue Delay
ASPs must ensure that businesses are informed, on an event-driven basis and without undue delay, when electronic invoices or Tax Data Documents have been successfully transmitted to the Authority.
This is significant because businesses will need reliable visibility over whether their invoices and tax reporting messages have been properly submitted. In practice, this may require dashboards, API status updates, confirmation messages, error notifications or audit logs.
For finance and tax teams, this confirmation process will be essential for monitoring compliance and resolving failed transmissions. For ASPs, it means that confirmation flows should be treated as a core compliance function rather than a purely technical feature.
New PINT AE Clarification on Advance Payments
Where a business receives an advance payment, a tax invoice must be issued at the time the advance is received. When the final invoice is later issued, it should only cover the remaining balance, rather than the full contract value, because the advance has already been invoiced.
This is a practical clarification for ERP and billing teams. Instead of issuing a final invoice for the total contract value and then adjusting the advance through the prepaid amount field, the updated guidance indicates that the final invoice can reflect only the outstanding balance.
The June version also explains that the original advance invoice may be referenced using the relevant PINT AE fields, including the preceding invoice reference fields or a note field. It also clarifies that the prepaid amount field may be left blank where the later invoice already reflects only the remaining amount due.
New PINT AE Clarification on Retention Arrangements
The updated guidance also addresses contracts involving retention amounts, which are common in sectors such as construction, engineering, and project-based services.
It allows businesses to continue applying their existing commercial and accounting practices, provided those practices remain compliant with VAT and e-invoicing requirements.
One acceptable approach is to issue an electronic invoice for the amount payable after deducting the retention amount. A separate electronic invoice may then be issued later for the retained amount, when the buyer becomes liable to release and settle it.
This clarification is helpful because it aligns the e-invoicing treatment with the commercial reality of retention arrangements. It also confirms that businesses should ensure the relevant contractual terms and payment obligations are properly reflected in the corresponding electronic invoices.
Final Takeaway
This updated guideline does not change the overall UAE e-invoicing model, but it does provide important implementation-level guidance. Businesses should now review whether their e-invoicing readiness plans properly address the newly clarified areas.
The most important updates relate to storage responsibility, ASP technical logs, confirmation messages, advance payment treatment and retention invoicing. These are not merely technical details. They affect contract design, ERP configuration, tax compliance, audit readiness and the day-to-day operation of the UAE e-invoicing system.
Businesses and ASPs should treat the June update as a prompt to revisit their implementation plans and ensure that both technical and business processes are aligned before mandatory go live.
