Electronic Invoicing Guidelines v1.1: Clarifications on Storage, ASP Obligations, Advance Payments, and Retention
 

The UAE Ministry of Finance (MoF) has issued Version 1.1 of the Electronic Invoicing Guidelines (1 June 2026), providing important clarifications to the framework introduced under MD No. 243 of 2025 and MD No. 244 of 2025.

While the core framework and rollout timelines remain unchanged, the updated guidance introduces critical interpretative clarity, particularly in relation to:

• Data storage and retention obligations & Roles and obligations of Accredited Service Providers (ASPs) [Appendix 4]
• Treatment of advance payments and retention [Appendix 5]

These clarifications are expected to have a direct impact on businesses' system configurations, contractual arrangements, and compliance processes.

We have summarized key updates and clarifications.

The updated Guidelines provide detailed clarification on the application of Article 11 of MD No. 243 of 2025, particularly regarding taxpayer obligations and storage expectations.

• Primary obligation remains with the taxpayer
  • Any Person subject to the e-invoicing system is required to retain:
    • Electronic invoices
    • Electronic credit notes
    • Associated data
  • Such records must be retained in accordance with timelines prescribed under the Tax Procedures Law and must be made available to the Federal Tax Authority (FTA) upon request.
• Interpretation of "storage within the State"
  • Businesses may use offshore or cloud-based storage solutions provided that:
    • Data is securely maintained
    • Integrity and authenticity are preserved
    • Records can be promptly retrieved and reproduced in a readable format when requested by the FTA
  • The requirement to store records "within the State" is clarified as functional \rather than location-specific.

• Scope of "associated data"
  • "Associated data" is restricted to information necessary to:
    • Maintain integrity and authenticity
    • Ensure auditability of the electronic invoice
  • This does not extend to general commercial or business documentation, unless such information is required to validate the invoice itself.

Appendix 4 also provides granular clarity on the responsibilities of Accredited Service Providers (ASPs) within the UAE's Peppol-based framework.

• Transactional logs and traceability
  • ASPs are required to maintain transactional logs for each transaction, including:
    • Unique transaction identifiers
    • Transmission status
    • Routing and processing details across the lifecycle
  • These logs are:
    • Technical in nature
    • Separate from the invoice data retained by the taxpayer
• Delegation of storage
  • Taxpayers may contractually delegate storage to ASPs.
  • However, such delegation:
    • Does not transfer the legal obligation
    • The taxpayer remains ultimately responsible for compliance with retention requirements
• Storage architecture flexibility
  • The Guidelines do not mandate storage at a specific system layer (e.g., ERP or ASP).
  • Any storage architecture is acceptable, provided: - Retention requirements are met - Data integrity and security are ensured - Records remain accessible for FTA review
• Transmission confirmation
  • ASPs must provide event-driven confirmations to taxpayers confirming:
    • Successful transmission of electronic invoices and tax data to the FTA
  • This ensures visibility and oversight of compliance for the taxpayer.

The Guidelines provide clarity on the treatment of advance payments within the e-invoicing framework.

• Issuance of invoice on receipt of advance
  • A tax invoice is required to be issued at the time the advance payment is received.
• Treatment of the final invoice
  • Where a tax invoice has already been issued for the advance:
    • The subsequent (final) invoice should be issued only for the remaining balance, and not for the full contract value
  • The final invoice should include a reference to the advance invoice.
• Prepaid amount field
  • The "Prepaid Amount" field may be left blank in such cases, as:
    • The final invoice already reflects the net outstanding amount
    • No further adjustment is necessary within the invoice structure

The Guidelines also clarify the treatment of retention arrangements.

• Flexibility in approach
  • Businesses may continue existing commercial and accounting practices, provided they remain compliant with VAT and e-invoicing requirements
• Acceptable invoicing approach
  • Issuing an Electronic Invoice for the amount payable (net of retention)
  • Issuing a separate Electronic Invoice for the retained amount, when such amount becomes due and payable
• Alignment with contractual terms
  • Businesses must ensure that:
    • The timing and value of invoices reflect contractual payment obligations
    • Retention release is appropriately captured in invoicing

The updated Guidelines signal a move toward implementation and operational readiness, with implications across:

• System and Process Readiness
  • ERP configuration for:
    • Advance payments
    • Retention structures
    • Invoice referencing mechanisms
• Data Governance
  • Strengthening record retention and accessibility
  • Ensuring audit readiness
  • Monitoring ASP performance and logs
• Contractual Alignment
  • Reviewing ASP agreements
  • Aligning commercial contracts with:
    • Retention clauses
    • Payment triggers