Blog Single

On June 1, 2026, the UAE Ministry of Finance released Version 1.1 of the Electronic Invoicing Guidelines—and if you’ve been waiting for clarity on storage, advances, and retention, this update is exactly what you needed.

Here’s the catch: Version 1.1 is not a redesign; it’s a clarification. Which sounds simple until you realize what it actually means for your ERP, your ASP contracts, and your finance operations.

What Stayed the Same (Spoiler: Everything Big)

The core pillars remain unchanged:

• Scope: E-invoicing is mandatory for B2B, B2G, G2B, and G2G transactions in the UAE (existing exclusions still apply).
• Timeline: Voluntary phase starts July 1, 2026. Mandatory implementation follows the phased schedule (businesses, then government).
• Model: 5-corner architecture, Peppol network, PINT AE specifications, and the requirement to use an Accredited Service Provider (ASP).

Translation for your team: You don’t need to restart your scoping or roadmap. You need to tune your systems, contracts, and procedures.

The Three Big Clarifications That Actually Matter

1. Storage Responsibility – The Cloud Hosting Question (Finally Answered)

The biggest source of confusion has been: “Can we store e-invoices in an offshore cloud?”

Version 1.1 says: Yes, but with conditions.

You can use cloud or offshore hosting provided that:

• Data integrity and security are maintained
• You can retrieve and provide complete records to the FTA within the statutory retention period

The rule isn’t about where the servers are. It’s about where the data can be accessed from. If your cloud provider (AWS, Azure, Google Cloud) can deliver your UAE e-invoices to the FTA on demand, you’re compliant.

What this means for CFOs: If you were debating between local and offshore hosting, this clarification removes that barrier. But—and this is critical—you need explicit SLAs with your cloud provider that guarantee FTA access and retrieval timelines.

2. Advance Payments – VAT Timing (The ERP Configuration Challenge)

Here’s where e-invoicing meets real finance chaos: advance payments.

The rule: When you receive an advance payment and VAT is due, you must issue an electronic Tax Invoice at the time of advance receipt—not wait for the final invoice.

The final invoice then covers only the remaining balance and must reference the advance invoice to signal VAT has already been accounted for.

What Version 1.1 clarifies: How to use PINT AE fields (preceding invoice reference, paid amount fields) to link advance and final invoices in your system.

Why CFOs need to care: If you’re using a legacy ERP or custom invoicing module, this is a system redesign conversation. Your ASP will need to support this dual-invoice workflow. If it doesn’t, you’ve found your technical blocker for July 1.

Practical example: A construction contractor receives a 50% advance on a AED 1M contract. VAT is due on receipt of the advance = AED 50K invoice must be issued via e-invoicing on day 1. Six months later, when you issue the final invoice for the remaining AED 500K, that final invoice links back to the advance invoice. Your ERP must handle both.

3. Retention Amounts – Construction & Long-Term Projects (The Contractual Complexity)

Retention is where invoice law meets construction reality. Version 1.1 acknowledges this and keeps it practical.

The clarification:

• You can keep your existing retention practices (net invoicing for progress billings, separate invoices when retention is released).
• The e-invoicing system simply documents the amounts due at each stage, including when retention gets released.
• The detailed retention calculations stay in your contract and project management system—not in the e-invoice itself.

Why this matters: If you’re a contractor managing retentions across 20 projects, you don’t have to rethink your entire invoicing process. You just need to issue separate e-invoices when retention becomes due.

What You Should Do Before July 1, 2026

1. Audit your ASP contract — Does it address: (a) advance payment workflows, (b) transaction logging, (c) FTA retrieval timelines, (d) cloud hosting arrangements?

2. Test your ERP with advance scenarios — If your system isn’t configured for dual invoicing (advance + final), test it now with your ASP.

3. Clarify your storage model — Confirm with your cloud provider or hosting provider that they can guarantee FTA access within your retention periods.

4. For projects with retention — Ensure your project management system and e-invoicing module are synchronized for retention release dates.

5. Document your retention practice — Version 1.1 says you can keep existing practices; document what yours actually are.

The Bigger Picture

E-invoicing is not about new rules; it’s about transparency, auditability, and real-time compliance. Version 1.1 simply clarifies how to achieve that without forcing you to rebuild your finance operations.

The real challenge? It’s in the execution—ASP contracts, ERP configuration, and cross-system coordination. And that’s where CFOs often stumble, not on the rules themselves.

FSH Financial Consultants advises UAE businesses on e-invoicing readiness, ASP vendor selection, and ERP implementation for VAT compliance. If you’re still uncertain about your July 1 readiness, let’s talk.