UAE’s e-invoicing mandate accelerates: key guides issued by Ministry of Finance

To aid readiness for VAT groups, the MoF has granted a temporary 24-month deferral of e‑invoicing reporting for intra VAT group transactions.

However, it does not remove sales by VAT group members from the scope of e‑invoicing; once the grace period ends on 31 December 2029, VAT group intercompany invoices must fully comply with e‑invoicing requirements. 

The guides reaffirm that e‑invoice data must be retained for at least five years, or longer in specific cases (e.g. additional years if under audit or dispute). These periods mirror existing tax record-keeping laws.

In terms of data storage, there is an important clarification on the requirement to store invoices “within the State” (UAE). The MoF’s guidance interprets that data will be “within the State” even if stored on servers outside the UAE as long as:

• The integrity and security of e‑invoice records are preserved (e.g. using encrypted storage).
• The storage infrastructure allows the taxpayer to promptly retrieve and produce complete, readable records.
• The e‑invoices and any associated data needed to verify authenticity can be provided to the FTA in full, on demand.

In essence, “within the State” means within easy reach of the FTA. Therefore, businesses should review their archiving solutions against these criteria to ensure compliance. 

Choosing the right ASP is crucial. The MoF’s new guide, “Considerations for Selecting an ASP”, lays out clear suggested evaluation parameters to help businesses make informed decisions.  

Key criteria include:

• Product capabilities and ownership 
• Integration readiness 
• Data management 
• Compliance and security frameworks 
• Customer support and SLAs 
• Pricing transparency 
• Scalability and future-proofing

By assessing ASPs against these (and other relevant) criteria, businesses can select an ASP that is a strong fit for their operations and existing systems landscape. 

The guide entitled “UAE Electronic Invoice Mandatory Fields” provides a simplified consolidated reference checklist of all mandatory data fields required on electronic invoices. This covers both Electronic Tax Invoices and Commercial Electronic Invoices.

Note: This guide should be read alongside the Peppol-based UAE invoice specifications (PINT-AE) to ensure complete compliance. 

Addressing industry questions, the MoF clarified that Harmonised System (HSN) commodity codes are not yet mandatory on e-invoices.

However, this is expected to change, and the timelines for making HSN codes mandatory will be announced later. Businesses should anticipate a future phase where certain sectors or transactions must include HSN codes, which will aid tax data analytics and customs alignment.  

To help businesses visualize what an e-invoice looks like in practice, the MoF released a sample “human-readable” Electronic Tax Invoice template. This example shows how an XML e-invoice can be rendered in a familiar layout.

Note: Even with this template, actual compliance relies on the XML content exchanged via ASPs. Printed or PDF invoices alone do not count as electronic invoices for FTA compliance. 

A critical principle reiterated by the new guidance is that the obligation to issue an electronic invoice lies entirely with the supplier. Even if a buyer is not yet onboarded to the e-invoicing system, or not mandated to use e-invoicing, the supplier must still issue an Electronic Tax Invoice for the sale.

During the “transition period”, where buyers are not yet onboarded, suppliers must issue both e-invoices and traditional tax compliant hard copy invoices.

The guidance confirms that holding companies earning only passive income such as dividends or interest, are not in the scope of mandatory e-invoicing.

However, where holding companies engage in taxable transactions, such as the recharge of management fees to a subsidiary, these will fall within the scope of e-invoicing. 

If non-resident suppliers are obligated to issue a UAE Tax Invoice (for example, a foreign entity registered for VAT making a B2B supply under UAE VAT law), then that invoice must now be electronic.

In short, being outside the UAE does not exempt a supplier from using an ASP and issuing e-invoices.  

The recently issued guides also address a range of special invoicing scenarios to guide businesses on their treatment under e‑invoicing. Key clarifications include:

• Provisional invoices: There is no separate category for “provisional” invoices in the e-invoicing system. Any provisional invoice (e.g. before final quantity/price is set) must itself be an Electronic Invoice in XML form.
• Deemed supplies: In cases of deemed or free supplies, no e-invoice needs to be delivered to a recipient. The requirement is only to report the deemed supply through the ASP to the FTA.
• Margin scheme transactions: For sales under the VAT margin scheme, the VAT amount on the e-invoice should be displayed as “0”. This aligns with current VAT invoicing practice for margin scheme sales.
• Retention payments in contracts: Retention amounts should not appear on the electronic tax invoice. Instead, they must be documented in a separate commercial document, while the e‑invoice reflects the full milestone amount. A new e‑invoice should be issued only when the retention becomes due.
• Export transactions: When exporting goods or services, companies must issue an electronic tax invoice which can also be shared with UAE Customs to streamline export procedures.
• Advance payments: When a customer pays an advance before an invoice is issued, the amount of advance should be recorded in the “Paid Amount” field of the final invoice. Additionally, the final invoice should include a reference to the original advance invoice in the “Preceding Invoice Reference” field.
• Industry-specific fields: Some industries have unique invoicing needs (for instance, energy companies might include volume metrics). The MoF instructs that if industry-specific data fields or classifications are needed, businesses must coordinate with their ASP on how to include these.
• Insurance sector – reinsurance treaty statements: A special note was made for the insurance/reinsurance industry. Often, reinsurance treaties between insurers and brokers involve periodic statements that net out premiums, claims, and commissions, rather than individual invoices for each transaction. The guidance now clarifies if such statements have any VAT impact, they must be issued as Electronic Invoices in compliance with the VAT rules.

These scenario-specific clarifications provide practical guidance, preventing ambiguity as businesses implement e-invoicing across their operations. Businesses should carefully assess each type of transaction they engage in against these points to ensure full compliance for every use case.