The UAE Ministry of Finance (MoF) issued two ministerial decisions on 29 September 2025 (Ministerial Decision No. 243 of 2025 on the national e-invoicing system and Ministerial Decision No. 244 of 2025 on its phased implementation), establishing the legal foundation for e-invoicing in the UAE. These were followed by Federal Tax Authority (FTA) regulations on 9 October, introducing an administrative penalty regime for noncompliance, an unmistakable signal that e-invoicing will be a substantive compliance obligation, not a procedural formality. Most recently, on 23 February 2026, the MoF released detailed e-invoicing guidelines, the E-invoice Mandatory Fields document and considerations for selecting Accredited Service Providers (ASPs), which provides detailed operational and technical clarifications businesses have been awaiting.
Collectively, these publications move e-invoicing from a future concept to an immediate implementation priority for organisations operating in, or transacting with, the UAE.
With the pilot phase for e-invoicing launching on 1 July 2026, affected businesses should begin preparing now.
The e-invoicing system will apply to any person conducting business in the UAE for every business transaction, regardless of whether they are established in the UAE, subject to limited exclusions. The regime will cover B2B, B2G, G2B and G2G transactions and will apply whether or not the transacting party is registered for VAT, extending well beyond a traditional VAT-only perimeter.
Commercial invoices relating to exempt or out-of-scope supplies will still be able to fall within the scope of e-invoicing where the underlying transaction qualifies as a business transaction, so entities issuing purely commercial documentation should not assume they are excluded. Narrow carve-outs will exist for:
VAT groups will benefit from a 24-month grace period for intragroup transactions, but all external transactions will have to comply based on each group member's mandatory date.
Selecting an ASP decision is not a simple technology procurement—it is a long-term compliance and integration decision that will shape system architecture, data flows, control frameworks and service levels.
Key evaluation criteria include:
The UAE has adopted a Peppol-based five-corner DCTCE (Decentralised Continuous Transaction Control and Exchange) model, under which invoices will be exchanged between ASPs and reported to the FTA through a structured network rather than via direct point-to-point integrations. (Peppol or the Pan-European Public Procurement Online is a standardised framework that streamlines the process of exchanging electronic documents through access points.)
The guidelines confirm:
Earlier commentary suggesting that all e-invoicing data must be stored on UAE-based servers created concern. The guidelines clarify that geographic location is not determinative. What matters is:
Retention periods follow the Tax Procedures Executive Regulations:
A supplier's obligation to issue an e-invoice does not depend on whether the customer is in scope or technically prepared. Under the phased timetable, many supply chains will see suppliers go live on e-invoicing before customers, particularly across differing size tiers and sectors. Suppliers may therefore need to operate a dual-track model:
The guidelines confirm there is no separate category for provisional invoices. Any provisional or milestone-based invoice that would ordinarily be issued must be generated as an e-invoice, with subsequent adjustments made through e-credit note(s) or additional e-invoice(s).
This has significant implications for construction, professional services and long-term project sectors where provisional billing is common, and will require the re-design of billing workflows, approval processes and system configuration.
Self-billing will remain available under the VAT legislation where the statutory conditions are fulfilled, but only in respect of VAT-registered suppliers and only where the party issuing the invoice can itself comply with the e-invoicing obligations from its mandatory date. Where a customer's mandatory date falls after the supplier's, the existing self-billing arrangements may need to be suspended or renegotiated to avoid compliance gaps during the transition period.
In industries such as insurance and real estate development, invoices are commonly issued on behalf of brokers using the notation “Tax invoice raised by buyer.” Under the UAE Peppol e-invoicing framework, this practice may continue under the self-billing document model provided conditions are fulfilled. Alternatively, businesses may opt to transfer the responsibility to the broker under the new e-invoicing regime, which will require further consideration going forward.
The e-invoicing regime draws a clear distinction between import reverse charge scenarios and domestic reverse charge supplies.
Import reverse charge on goods and services is outside the scope of e-invoicing. By contrast, specified domestic reverse charge supplies between VAT-registered persons—covering certain electronic devices, precious metals and stones, hydrocarbons, crude and refined oil, natural gas and scrap metal—will fall within scope. The supplier will be required to issue an e-invoice without VAT, clearly referencing the reason for domestic reverse charge treatment.
This underscores the need for robust tax classification within product and customer master data.
The technical backbone of the regime is the UAE-specific PINT-AE XML standard, combined with the 51 mandatory fields set out in the e-invoice, complemented by additional optional and conditional mandatory fields. These requirements form the primary reference for ERP and billing system configuration, covering:
E-invoicing sits at the intersection of tax, finance, IT, procurement, sales and legal. As a result, effective implementation requires cross-functional governance rather than a siloed approach. In practice, the following functions typically need direct representation in an implementation steering committee:
The FTA regulations introduce a detailed schedule of administrative penalties for e-invoicing noncompliance:
Beyond the formal penalty schedule, the practical consequences of noncompliance can be more significant:
Affected UAE businesses and multinational groups with UAE operations should consider taking the following near-term actions:
Collectively, these publications move e-invoicing from a future concept to an immediate implementation priority for organisations operating in, or transacting with, the UAE.
With the pilot phase for e-invoicing launching on 1 July 2026, affected businesses should begin preparing now.
Scope: Wider than VAT Compliance
The e-invoicing system will apply to any person conducting business in the UAE for every business transaction, regardless of whether they are established in the UAE, subject to limited exclusions. The regime will cover B2B, B2G, G2B and G2G transactions and will apply whether or not the transacting party is registered for VAT, extending well beyond a traditional VAT-only perimeter.Commercial invoices relating to exempt or out-of-scope supplies will still be able to fall within the scope of e-invoicing where the underlying transaction qualifies as a business transaction, so entities issuing purely commercial documentation should not assume they are excluded. Narrow carve-outs will exist for:
- Investment holding companies generating only passive income;
- Sovereign activities carried out by government entities;
- Certain international air transport services; and
- Specified exempt financial services.
VAT groups will benefit from a 24-month grace period for intragroup transactions, but all external transactions will have to comply based on each group member's mandatory date.
Implementation Timeline and Mandatory Dates
Ministerial Decision No. 244 of 2025 sets out the phased implementation framework:| Phase | Threshold | ASP Appointment Date | Go Live Date |
| Pilot phase | On nomination by the MoF | 1 July 2026 | |
| Voluntary phase | All persons, regardless of revenue | 1 July 2026 | |
| Mandatory phase 1 | Annual revenue ≥ AED 50 million | 31 July 2026 | 1 January 2027 |
| Mandatory phase 2 | Annual revenue < AED 50 million | 31 March 2027 | 1 July 2027 |
| Mandatory phase 3 | Government entities, regardless of turnover | 31 March 2027 | 1 October 2027 |
Accredited Service Provider Decision
Every in-scope person will be required to appoint a single ASP to manage both the issuance (accounts receivable) and receipt (accounts payable) of e-invoices and e-credit notes. ASPs are accredited under Ministerial Decision No. 64 of 2025 and the MoF publishes a list of pre-approved providers on its website.Selecting an ASP decision is not a simple technology procurement—it is a long-term compliance and integration decision that will shape system architecture, data flows, control frameworks and service levels.
Key evaluation criteria include:
- Integration with existing ERP and finance systems;
- Peppol-based capability and adherence to the UAE PINT-AE standard;
- Information security and data governance; scalability for future regulatory changes; and
- Contractual clarity on responsibilities, incident management and ongoing support.
Peppol Framework and Participant Identifiers
The UAE has adopted a Peppol-based five-corner DCTCE (Decentralised Continuous Transaction Control and Exchange) model, under which invoices will be exchanged between ASPs and reported to the FTA through a structured network rather than via direct point-to-point integrations. (Peppol or the Pan-European Public Procurement Online is a standardised framework that streamlines the process of exchanging electronic documents through access points.)The guidelines confirm:
- The primary participant identifier on the Peppol network is derived from the Tax Identification Number (TIN). For VAT registrants, this is the first 10 digits of the Tax Registration Number (TRN), formatted as 0235:[10-digit TIN]).
- VAT group members will use their own identifiers rather than that of the representative member, ensuring entity-level transactional traceability.
- Non-VAT-registered persons carrying out in-scope business transactions will need to obtain a TIN to participate in the system.
Data Storage, Retention and Location
Earlier commentary suggesting that all e-invoicing data must be stored on UAE-based servers created concern. The guidelines clarify that geographic location is not determinative. What matters is:
- Secure retention;
- Data integrity; and
- The ability to retrieve complete, readable records promptly upon request by the FTA.
Retention periods follow the Tax Procedures Executive Regulations:
- Five years for taxable persons;
- Seven years for records relating to real estate; and
- Longer where periods are under audit or dispute.
Dual-Tracking Invoicing During Transition
A supplier's obligation to issue an e-invoice does not depend on whether the customer is in scope or technically prepared. Under the phased timetable, many supply chains will see suppliers go live on e-invoicing before customers, particularly across differing size tiers and sectors. Suppliers may therefore need to operate a dual-track model:
- Issuing the structured XML eInvoice via the Peppol network for compliance; and
- Providing a human-readable PDF or equivalent for customers' operational processes.
Provisional, Milestone and Self-Billing Arrangements
The guidelines confirm there is no separate category for provisional invoices. Any provisional or milestone-based invoice that would ordinarily be issued must be generated as an e-invoice, with subsequent adjustments made through e-credit note(s) or additional e-invoice(s).This has significant implications for construction, professional services and long-term project sectors where provisional billing is common, and will require the re-design of billing workflows, approval processes and system configuration.
Self-billing will remain available under the VAT legislation where the statutory conditions are fulfilled, but only in respect of VAT-registered suppliers and only where the party issuing the invoice can itself comply with the e-invoicing obligations from its mandatory date. Where a customer's mandatory date falls after the supplier's, the existing self-billing arrangements may need to be suspended or renegotiated to avoid compliance gaps during the transition period.
In industries such as insurance and real estate development, invoices are commonly issued on behalf of brokers using the notation “Tax invoice raised by buyer.” Under the UAE Peppol e-invoicing framework, this practice may continue under the self-billing document model provided conditions are fulfilled. Alternatively, businesses may opt to transfer the responsibility to the broker under the new e-invoicing regime, which will require further consideration going forward.
Reverse Charge: Imports Versus Domestic Supplies
The e-invoicing regime draws a clear distinction between import reverse charge scenarios and domestic reverse charge supplies.Import reverse charge on goods and services is outside the scope of e-invoicing. By contrast, specified domestic reverse charge supplies between VAT-registered persons—covering certain electronic devices, precious metals and stones, hydrocarbons, crude and refined oil, natural gas and scrap metal—will fall within scope. The supplier will be required to issue an e-invoice without VAT, clearly referencing the reason for domestic reverse charge treatment.
This underscores the need for robust tax classification within product and customer master data.
Key Technical and Data Requirements
The technical backbone of the regime is the UAE-specific PINT-AE XML standard, combined with the 51 mandatory fields set out in the e-invoice, complemented by additional optional and conditional mandatory fields. These requirements form the primary reference for ERP and billing system configuration, covering:
- Seller and buyer identifiers;
- Invoice metadata;
- Monetary totals;
- Tax breakdowns; and
- Line-level attributes.
- No limit on line-items per invoice, supporting high volume and complex billing scenarios.
- Multi-currency invoicing will be permitted, but all amounts will have to be presented in AED using UAE Central Bank exchange rates, with responsibility for accurate conversion resting with the supplier.
- Partial credit notes will be allowed and a single credit note may reference multiple prior invoices.
- Rounding will be applied at the invoice level to two decimal places, not at the line-item or tax category level.
- Mixed supply invoices will be permitted, allowing taxable, exempt and out-of-scope supplies to appear on a single invoice, provided tax coding and disclosures are accurate.
- HSN codes will remain optional for now, but a mandatory date is expected. Given the volume of product catalogues in many sectors, businesses should begin HSN classification and master data enrichment now.
Governance, Controls and Cross-Functional Impact
E-invoicing sits at the intersection of tax, finance, IT, procurement, sales and legal. As a result, effective implementation requires cross-functional governance rather than a siloed approach. In practice, the following functions typically need direct representation in an implementation steering committee:
- Accounts receivable and accounts payable;
- Tax;
- Finance and accounting;
- IT, ERP and integration;
- Procurement and supplier management;
- Sales and customer service; and
- Legal and compliance.
Penalties, Enforcement and Wider Risk
The FTA regulations introduce a detailed schedule of administrative penalties for e-invoicing noncompliance:| Nature of noncompliance | Administrative penalty (AED) |
| Failing to appoint an ASP by the prescribed deadline or failing to implement the e-invoicing system | 5,000 per month or part thereof |
| Failing to issue or transmit e-invoices or e-credit notes in the prescribed manner within the required timeframe | 100 per e-invoice or e-credit note, capped at 5,000 per month per category |
| Failing to notify the FTA promptly of system failures preventing e-invoicing | 1,000 per day or part thereof |
| Failing to notify the ASP of changes to the data required on a prescribed timeline | 1,000 per day or part thereof |
Beyond the formal penalty schedule, the practical consequences of noncompliance can be more significant:
- Delayed customer payments where invoices cannot be processed electronically;
- Strained supplier relationships where inbound invoices are not handled correctly;
- Increased audit exposure where structured records and retrieval processes are deficient; and
- Operational friction and competitive disadvantage compared with better-prepared peers.
Practical Next Steps
Affected UAE businesses and multinational groups with UAE operations should consider taking the following near-term actions:
- Confirm the mandatory implementation date for each legal entity and assess readiness.
- Map all transaction flows by entity, business line and jurisdiction against scope and exclusions, including free zone, export, agent, e-commerce and deemed supply scenarios.
- Shortlist and evaluate ASPs against technical, operational and contractual criteria and progress to appointment well ahead of statutory deadlines.
- Review existing invoicing models, including provisional billing, self-billing, domestic reverse charge, advance payments and VAT group intragroup charging to identify required contractual or process changes.
- Begin TIN validation, Peppol ID collection and HSN coding within customer and supplier master data.
- Design and test dual-track processes for counterparties that will not be ready on the go-live date, particularly across regional and cross-border supply chains.
- Consider participating in the voluntary pilot from 1 July 2026 to gain operational experience, test error handling and refine control frameworks before compliance becomes mandatory.
BDO Perspective
The e-invoicing regime should be viewed not as a narrow tax requirement, but as a cross-functional digital transformation with significant implications for finance, tax, IT, legal and operational processes. This digital transformation is expected to enhance tax transparency, reduce errors, increase efficiency and align the UAE with global digital tax standards.
E-invoicing implementation is not an overlay on existing processes, it is a tax-to-technology shift that will reshape how transaction data is created, validated, transmitted and retained across the organisation.
Amrita Chandwani
Ashish Athavale
Dhruv Mehta
Mufaddal Safdari
BDO in United Arab Emirates