The UAE Ministry of Finance has released Version 1.1 of the UAE Electronic Invoicing Guidelines, and while it does not alter the scope, timeline, or technical architecture of the e-invoicing mandate,
It answers a set of operational questions that have been holding businesses back from finalising their systems. For finance teams preparing ERP configurations, negotiating Accredited Service Provider (ASP) agreements, or simply trying to understand what changes on the ground, this update fills in details on record retention, advance payments, contractual retentions, and ASP responsibilities that the original framework left open.
With the pilot phase set to begin in July 2026 and mandatory implementation to follow in phases, this is the moment for UAE businesses to close the gap between knowing e-invoicing is coming and actually being ready for it.
What Does UAE E-Invoicing Actually Change for Businesses
Under the current system, most UAE businesses issue invoices as PDFs or paper documents, then email or hand them to customers directly. Once e-invoicing takes effect, invoices must be created and exchanged in a structured, machine-readable format, transmitted through an Accredited Service Provider rather than shared directly.
This shift means an invoice is no longer just a document sitting in a business's own records. It becomes a structured data record inside a wider compliance system, one that can be validated and, depending on the model, shared with the Federal Tax Authority (FTA) close to real time. That is precisely why questions like who stores what, how advances are sequenced, and what an ASP is required to log suddenly carry much more weight than they did under a paper-based system.
Why Was Version 1.1 of the Guidelines Released
Version 1.1 exists because the practical side of e-invoicing adoption raised questions the original guidelines did not fully address. The Ministry of Finance has now clarified four areas in particular: record-storage responsibility, ASP obligations, advance-payment invoicing, and contractual retention amounts.
None of these clarifications change the scope, the implementation timeline, or the underlying technical framework. What they do is remove ambiguity that would otherwise lead to inconsistent invoicing practices, and inconsistent practice is exactly what creates compliance risk once the mandate goes live.
Who Is Responsible for Storing E-Invoices When Using an Accredited Service Provider
A key clarification in Version 1.1 is that businesses remain legally responsible for maintaining electronic invoices, credit notes, and related records for the statutory retention period, even when the actual storage is outsourced to an ASP. Outsourcing the mechanics of storage does not outsource the underlying legal responsibility.
To stay compliant, businesses must ensure their records
• Remain complete, secure, and unaltered throughout the retention period
• Can be readily retrieved and provided to the FTA on request
• Maintain their integrity, so the stored version is demonstrably the same as the version originally issued
Cloud-based or offshore hosting arrangements may be acceptable under the updated guidance, provided records can still be accessed and reproduced for regulatory purposes whenever required. The emphasis is on availability and integrity of the record, not where it is physically hosted.
What Are ASPs Required to Log and Maintain
Version 1.1 reinforces that Accredited Service Providers must maintain transaction logs documenting the processing, validation, and transmission of every electronic invoice that passes through them. Because the ASP sits in the middle of the invoicing flow, these logs form a critical part of the audit trail if a dispute or FTA inquiry arises later.
This is a good moment for businesses to revisit their ASP service agreements and confirm two things: that record-retention and support obligations are written into the contract, and that responsibilities between the business and the ASP are clearly divided rather than left implied.
How Should Advance Payments Be Invoiced Under the New Guidelines
Where VAT becomes due on receipt of an advance payment, the Ministry has clarified that an electronic tax invoice must be issued at the time the advance is received, not after the fact. When the final invoice is later issued, it should reflect only the remaining balance due and reference the original advance invoice, so the same VAT amount is never reported twice.
This detail matters most for businesses that routinely take deposits or staged payments, such as consultancies, contractors, and service providers with milestone billing. It is worth building this sequencing into billing workflows directly rather than relying on manual tracking, since manual processes are where sequencing errors tend to creep in.
How Are Contractual Retention Amounts Treated for E-Invoicing
Contractual retention amounts are common in construction and other long-term project work, where a client withholds a percentage of each payment until project completion or a defect liability period ends. Version 1.1 confirms that businesses may continue following their existing VAT-compliant retention practices.
For interim billings, invoices can be issued for the net amount payable after retention deductions. Once the retained amount becomes due, a separate electronic tax invoice should be issued specifically for that amount. This gives project-based businesses a clear, compliant path for phased billing without needing to redesign their existing retention arrangements.
When Does UAE E-Invoicing Become Mandatory
The pilot phase of UAE e-invoicing is expected to commence from July 2026, with mandatory implementation following in phases after that. The pilot is designed to let businesses test their systems under real conditions before compliance becomes obligatory, so treating it as a rehearsal rather than a distant deadline is the more strategic approach.
What Should Businesses Do to Prepare Now
Based on the clarifications in Version 1.1, businesses should prioritise the following before the pilot phase begins:
1. Map current invoicing practices for advance payments and contractual retentions against the new sequencing requirements
2. Confirm ERP readiness to produce structured, machine-readable invoices rather than human-readable PDFs
3. Review record-retention settings to ensure they meet the integrity and retrieval standards set out in the guidelines
4. Renegotiate or clarify ASP contracts where record-retention and audit-log responsibilities are not explicitly defined
5. Test the full invoicing flow, from issuance through validation to storage, during the pilot window rather than waiting for the mandate to take effect
What Are the Most Common Readiness Gaps Businesses Are Finding
A few gaps tend to recur as businesses prepare:
• ERP systems configured to produce human-readable invoices, not the structured format the system requires
• Record-retention settings that store invoices without guaranteeing the integrity or easy retrieval the guidelines call for
• Advance payments and retentions handled manually, which works on paper but breaks down once sequencing and cross-referencing become mandatory
• ASP agreements that are silent on record retention and audit-log responsibilities
Identifying these gaps during the pilot, rather than after the mandate takes effect, is the single most valuable step a business can take right now.
Get Ready for UAE E-Invoicing Before It Becomes Mandatory
Don't wait for the mandate to test your systems. Talk to Legacy Partners' Virtual CFO and tax advisory team today to get your invoicing, ERP, and ASP contracts pilot-ready info@legacypartners.ae
Updated On: 14 Jul, 2026
