UAE Electronic Invoicing – Ministry of Finance issues detailed implementation guidelines

Participant identifier 

The guidelines confirm that a person’s participant identifier will be its tax identification number (TIN). For entities already registered with the FTA, the TIN corresponds to the first 10 digits of the tax registration number (TRN). Businesses that fall within the scope of electronic invoicing but are not currently registered for any tax type will be required to register with the FTA to obtain a TIN.

Importantly, entities that are members of a VAT group must use their own TIN and not the TIN of the tax group representative.

The UAE-specific Peppol Participant Identifier is “0235:” Businesses must collect buyers’ Peppol IDs for compliance.

The guidance also confirms that when issuing invoices to buyers who have not yet implemented electronic invoices, whether voluntarily or because they are not yet subject to a mandatory requirement, regular tax invoices (e.g., in PDF format) must be issued in addition to electronic tax invoices. A pre-defined end-point is specified for this scenario (0235: 9900000098).

Lastly, non-UAE established persons making taxable supplies in the UAE and required to issue tax invoices are also subject to the e-invoicing regime and must comply with the relevant onboarding and implementation requirements. In this regard, non-resident persons who do not already hold a UAE tax registration number (TRN/TIN) will be required to register with the FTA and obtain a TIN in order to meet their invoicing and e-invoicing compliance obligations.

General responsibilities of suppliers, buyers and ASPs

The UAE electronic invoicing framework clearly distinguishes responsibilities between the supplier, buyer, and the accredited service provider (ASP), reinforcing that compliance accountability remains with the transacting parties and not the technology provider.

Importantly, while the ASP performs validation and transmission functions, it does not assume tax compliance liability. The legal responsibility for correct invoicing and VAT treatment remains with the supplier and buyer.

The allocation of responsibilities demonstrates that electronic invoicing is not merely a technical integration exercise but a governance and control framework.

Data storage and archival

Electronic invoice data must be retained in accordance with the existing Tax Procedures Executive Regulation—five years for general transactions and seven years for real estate—with extensions applying in the case of audits or voluntary disclosures.

The new guidelines confirm that from a tax perspective physical storage in the UAE is not required, provided that records can be promptly retrieved upon request by the FTA.

Categories, provisional invoices and commercial invoices  

The guidance confirmed the six categories of electronic invoices that may be issued:

• Electronic tax invoice
• Electronic tax credit note
• Commercial invoice
• Electronic credit note
• Self-billed electronic tax invoice
• Self-billed electronic tax credit note

There is no separate category for provisional invoices. Any provisional billing must be issued as an electronic invoice, with subsequent adjustments made through an electronic credit note or additional electronic invoice.

The guidance also confirmed that commercial invoices are those that are  issued for supplies that do not require a tax invoice (e.g., exempt or out-of-scope supplies, or where the supplier is not VAT registered). Businesses will need to review commercial invoices closely, as this area may introduce new data mapping requirements to ensure accurate reporting of exempt, out-of-scope, or non-VAT-registered supplier transactions.

Electronic invoice scenarios

Under the earlier public consultation document, the ministry had outlined 16 use-case scenarios intended to capture a broad range of transaction types. However, in the guidelines, this has now been split between invoice types and transaction scenarios, providing for further granularity in issuance rules and allowing for further flexibility on use of data fields.

The guidance highlights eight specific scenarios that impose additional data requirements under the electronic invoicing framework. These scenarios may impose mandatory fields, predefined endpoints, or specific treatment rules.

1) Free zone transactions – This scenario applies where a transaction involves a free zone entity (supplier, buyer, or beneficiary) or where the supply takes place within or from a free zone. Typical examples include, 1) A supply to or from a party established in a free zone, 2) A supply of goods within a free zone, and 3) An export of goods from a free zine. This scenario applies to both tax and commercial invoices.

2) Deemed supplies – This scenario applies where a supply made by a VAT-registered person is deemed to be a taxable supply under the UAE VAT Decree-Law. Examples include supplies made without consideration (such as free-of-charge supplies, gifts exceeding the prescribed threshold, or private use of business assets or inventory), as well as goods and services held at the time of VAT deregistration. This scenario does not apply to commercial invoices.

3) Margin scheme – This scenario applies to instances where VAT is calculated only on the supplier’s profit margin (i.e., the difference between the purchase price and the resale price). Examples include a car dealer selling a used vehicle under the profit margin scheme and a gallery reselling artwork purchased from private collectors who are not taxable persons. This scenario does not apply to commercial invoices.

4) Summary invoices – This scenario applies where multiple transactions with the same customer over a defined invoicing period are consolidated into a single summary invoice. For example, a bank may issue a monthly electronic tax invoice summarizing all supplies made to a customer during that period. This scenario applies to both tax and commercial invoices.

5) Continuous supplies – This scenario applies to supplies provided on an ongoing or recurring basis, or where periodic invoicing is involved. Examples include monthly advisory service retainers, delivery of building materials in instalments, and milestone-based payments. This scenario applies to both tax and commercial invoices.

6) Agent billing (disclosed agent) – This scenario applies where a person acts as a disclosed agent on behalf of a principal and issues invoices in the name of, or on behalf of, that principal. It does not apply to undisclosed agents. An example includes an insurance broker issuing an invoice to collect premiums from a buyer on behalf of a VAT-registered insurance company. This scenario applies to both tax and commercial invoices.

7) E-commerce supplies – This scenario applies to supplies made through an electronic commerce medium, as defined under Ministerial Decision No. 26 of 2023 on the Criteria and Conditions for Electronic Commerce for the Purpose of Keeping Records of Supplies Made. Examples include a retailer selling products directly to consumers through its website or goods sold via an e-commerce platform. This scenario applies to both tax and commercial invoices.

8) Exports – This scenario applies to goods or services supplied to customers outside the UAE. Examples include a UAE wholesaler exporting cosmetics to a retailer in Kuwait or a UAE IT firm providing software development services to a client in France. This scenario does not apply to commercial invoices.

An electronic invoice may capture multiple scenarios within a single document. Where more than one scenario applies, all relevant requirements must be incorporated.

These scenarios introduce operational complexity, particularly for businesses with diverse transaction models (e.g., free zones, intercompany arrangements, continuous supplies). Early identification of applicable scenarios and system configuration is critical to ensure compliant invoice generation and avoid validation errors during implementation.

Electronic credit notes

The guidance confirms that a single electronic tax credit note can be issued to adjust or correct multiple previously issued electronic invoices.

This allows businesses to consolidate credit adjustments in a single document; however, it is crucial to ensure proper setup, as any misconfiguration could put the adjustments at risk.

Reverse charge mechanism

The guide confirms that only transactions subject to the domestic reverse charge mechanism should be included in the scope of e-invoicing. Such domestic reverse charge is applicable to qualifying supplies within the UAE such as supplies of electronic devices, scrap metal, etc.

By contrast, reverse charge transactions arising on imported services (i.e., foreign RCM) are not subject to the UAE e-invoicing requirements and therefore fall outside the scope of the regime.

Exclusions

The guidance re-affirms the exclusions including sovereign activities carried out by government entities, certain airline supplies, international passenger transport services where an electronic ticket or electronic miscellaneous document is issued. In addition, a temporary 24-month exclusion applies to international transportation of goods by airlines where an airway bill is issued.

Financial services that are exempt from VAT under Article 42 of the VAT Executive Regulation are excluded from electronic invoicing. However, standard-rated financial services supplied to UAE residents remain within scope, even if they qualify as zero-rated exports of services under Article 31 of the VAT Executive Regulation. In addition, interest income earned from related entities established outside the UAE, where the conditions for zero-rating as an export of services are met, would qualify as zero-rated financial services. In such cases, these supplies would fall outside the scope of the Electronic Invoicing regime.

B2C and G2C transactions were confirmed as out of scope.

Mandatory fields

The Mandatory Data Fields Guidelines outline the invoice data elements that must be captured and transmitted under the new e-invoicing regime, with additional information provided for each field. This includes the requirement to report VAT amounts at the line-item level in AED, regardless of the invoice currency, and must include a tax category code aligned with UAE VAT treatments, such as standard-rated, zero-rated, exempt, reverse charge, or margin scheme.

To prepare for compliance, businesses are recommended to conduct a gap analysis of their existing processes and systems to identify any adjustments needed for e-invoicing readiness.

Specific scenarios – Investment holding companies

Investment holding companies established solely to hold assets and generate passive income, without conducting business transactions, are generally not within the scope of electronic invoicing.

However, the guidance specifically referenced instances where an investment holding company charges management fees, operational costs, or makes recharges to related parties or third parties, such activities may constitute business transactions. In such cases, the entity would fall within the scope of electronic invoicing and be required to register, appoint an ASP, and issue electronic invoices. There may be heightened focus on this area.

Specific scenarios – VAT groups

Business transactions carried out between members of the same VAT group are within the scope of electronic invoicing and are not excluded solely because they are intra-group.

Recognizing the operational complexity of intercompany arrangements, a temporary 24-month grace period applies to intra-group transactions. The grace period commences on 1 January 2027, during which electronic invoicing obligations will not need to be implemented for transactions between members of the same VAT group.

This relief affects timing only and does not remove intra-group transactions from scope. VAT Groups should use the grace period to review intercompany billing flows, internal charging mechanisms, and ERP configurations. Given the typically high volume and automation of intra-group transactions, early system alignment will be critical to avoid operational disruption once the relief period ends.