Article 65 of the Federal Decree-Law No. 8 of 2017 on Value Added Tax now defines a Tax Invoice to include an Electronic Invoice issued in accordance with the Electronic Invoicing System. This change, made through the amendments to the VAT Decree-Law underpinning the UAE e-invoicing framework, has a direct practical consequence: for VAT-registered businesses in scope of the Electronic Invoicing System, issuing a PINT-AE compliant electronic invoice to a buyer who has implemented electronic invoicing satisfies the Tax Invoice obligation. The traditional paper or PDF document is no longer the baseline.
Understanding exactly what this means — and what it does not remove — is essential for tax directors and finance teams preparing for go-live.
The Two Document Categories Under Electronic Invoicing
The UAE Electronic Invoicing System distinguishes between two primary document categories: the Electronic Tax Invoice and the Commercial Invoice. This distinction maps directly onto existing VAT law but applies it within a new technical architecture.
The Electronic Tax Invoice
An electronic Tax Invoice is issued by a Taxable Person — a VAT registrant — in respect of Taxable Supplies, as required by the VAT Decree-Law. It may also include non-Taxable Supplies on the same document. The electronic Tax Invoice carries 51 mandatory fields under the PINT-AE specification, including all the information required for a Tax Invoice under Article 59 of the VAT Executive Regulation, plus UAE-specific extension fields (BTAE fields). The document type code for an electronic Tax Invoice is 380. A self-billed variant exists where the Recipient issues the invoice on behalf of the Issuer — subject to the conditions in the VAT Executive Regulation and only where both parties are VAT registrants.
The Commercial Invoice
A Commercial Invoice — document type code 480 — is issued for supplies that do not require a Tax Invoice under the VAT Decree-Law. This covers supplies made by persons not registered for VAT, as well as supplies that are exempt from VAT or outside the scope of UAE VAT. Under the Electronic Invoicing System, traditional Commercial Invoices in PDF or paper format must be replaced by electronic Commercial Invoices that meet the PINT-AE specification and are transmitted through the ASP exchange model. The Commercial Invoice carries 49 mandatory fields — two fewer than the Tax Invoice.
What Changes for Taxable Persons Under E-Invoicing
The Dual Output Problem During Transition
The Electronic Invoicing System creates a transitional complication for VAT-registered businesses. Where a buyer has implemented electronic invoicing and holds a Peppol Participant Identifier, the electronic Tax Invoice transmitted through the system satisfies the Tax Invoice obligation. No separate PDF Tax Invoice is required.
Where a buyer has not yet implemented electronic invoicing, the supplier must issue a regular Tax Invoice in addition to the electronic Tax Invoice. The electronic Tax Invoice must still be transmitted through the system, using the predefined endpoint 0235:9900000098 to signal that the buyer has not yet onboarded onto the Peppol network.
This dual-output requirement during the transition period creates a workflow management challenge. AR teams need to determine, at the point of invoice issuance for every transaction, whether the specific customer has a Peppol Participant Identifier. Where they do not, a second document must be generated and delivered through traditional channels. This buyer-status tracking requirement depends entirely on the completeness of customer master data — which, for most large UAE businesses, is one of the primary data gaps the compliance programme must address before go-live.
Self-Billing Arrangements
Article 9 of MD 243 of 2025 permits the Recipient to issue an Electronic Invoice or Electronic Credit Note on behalf of the Issuer, subject to the conditions prescribed in the VAT Executive Regulation. The conditions for self-billing under VAT law — mutual agreement, both parties registered, the invoice meeting Tax Invoice requirements — continue to apply. Under electronic invoicing, self-billing arrangements extend only to VAT-registered parties.
A practical complication arises where a supplier falls into the mandatory phase for electronic invoicing but their buyer — who issues invoices on the supplier's behalf under a self-billing arrangement — has not yet implemented. The supplier's obligation to comply with the Electronic Invoicing System cannot be transferred through a self-billing arrangement. From the Phase 1 go-live date, self-billed transactions involving Phase 1 suppliers require the buyer to be capable of issuing PINT-AE compliant electronic invoices. Businesses with self-billing agreements in place need to review those arrangements against the implementation timelines of both parties.
Credit Notes Under UAE E-Invoicing
Article 6(2) of MD 243 sets out four circumstances that require an Electronic Credit Note: cancellation of a business transaction, reduction of the agreed consideration, return of consideration in full or in part, and administrative or numerical error. Article 61 of the VAT Decree-Law — the governing rule for Tax Credit Notes — continues to apply. The Electronic Credit Note replaces the paper or PDF credit note as the mandated format.
The credit note carries specific mandatory fields, including a reference to the original invoice UUID and a credit note reason code from the PINT-AE code list. The UAE-specific reason codes — DL8.61.1.A through DL8.61.1.E — map to the legal adjustment scenarios. Where an adjustment relates to a voluntary disclosure, the reason code must reflect that. Mapping internal credit note reason codes to the prescribed PINT-AE list is a configuration task that must be completed before go-live.
Non-Resident Persons With UAE Tax Invoice Obligations
One scope area frequently overlooked in initial compliance assessments concerns non-UAE established persons with an obligation to issue Tax Invoices in the UAE under the VAT Decree-Law. The UAE E-Invoicing Guidelines V1.1 confirm that where such a person is obligated to issue Tax Invoices in the UAE, those invoices must be issued as Electronic Invoices. The phase classification rules apply based on UAE revenue.
For groups headquartered in the UK, EU, or India with UAE VAT registrations through branches or locally incorporated entities, this provision applies directly. The UAE e-invoicing compliance programme extends to every entity in the group with a UAE VAT registration, regardless of where the group's head office sits or which ERP instance processes the UAE entity's transactions.
Practitioner Insight: The most significant operational change that the Article 65 amendment creates is not the technical format of the invoice. It is the real-time connection between invoice issuance and tax data reporting. Under the electronic invoicing architecture, the FTA's Corner 5 receives invoice-level data at the point of exchange — not at the VAT return filing date. This transforms the tax assurance model from a period-end reconciliation to a continuous data stream that the FTA can query at any time.
Provisional Invoices Under the New Framework
The UAE E-Invoicing Guidelines V1.1 address provisional invoices directly: there is no separate electronic invoice category for provisional invoices. Every provisional invoice issued must be an Electronic Invoice. Adjustments to the provisional amount are handled through an Electronic Credit Note or an additional Electronic Invoice. This is a departure from some current business practices where provisional invoices are issued outside the formal invoicing system and settled through a final adjustment. Under electronic invoicing, every provisional document enters the system and becomes visible to the FTA.
Preparing the Tax Function for E-Invoicing
For UAE tax directors, the shift from a VAT compliance model centred on the period-end return to one anchored in real-time invoice data transmission requires a structural rethink of how the tax function monitors compliance. The VAT return does not disappear — but its relationship to the electronic invoice data stream means that discrepancies between what was transmitted through the system and what is reported on the return will be visible to the FTA before the return is filed.
The compliance programme for Phase 1 businesses must include a redesign of the VAT return preparation process to reconcile with electronic invoice data, a review of all document types and credit note workflows against PINT-AE requirements, and a training programme for the tax team on the new document landscape — including which document type applies to which transaction, what the credit note reason codes mean operationally, and how the confirmation message flow from buyers feeds into the AR reconciliation process.