Background and regulatory context
On 29 September 2025, the Ministry of Finance (MoF) issued Ministerial Decision No. 243 of 2025 on the eInvoicing system and Ministerial Decision No. 244 of 2025 on its phased implementation, establishing the legal framework for eInvoicing in the UAE.On 9 October 2025, the Federal Tax Authority (FTA) issued Cabinet Decision No. 106 of 2025 introducing an administrative penalty regime for non-compliance, signaling that eInvoicing is an enforceable obligation and not a procedural formality.
On 23 February 2026, the MoF followed this with the UAE eInvoicing Guidelines (Version 1.0), the eInvoice Mandatory Fields document and considerations for selecting Accredited Service Providers (ASPs), providing detailed operational and technical clarification for businesses.
Collectively, these timely and apt publications shift eInvoicing from a future concept to an immediate implementation priority for organisations operating in, or transacting with, the UAE.
Scope: Wider than VAT compliance
eInvoicing system applies to any person conducting business in the UAE in respect of every business transaction, regardless of whether they are established in the UAE or not, subject only to specific exclusions. The regime captures B2B, B2G, G2B and G2G transactions, regardless of whether the transacting party is registered for VAT or not, moving well beyond a traditional VAT-only boundary.Commercial invoices relating to exempt or out-of-scope supplies can still fall within scope where the underlying transaction qualifies as a business transaction, so entities issuing purely commercial documentation should not assume they are excluded. Limited carve-outs exist for investment holding companies solely generating passive income, sovereign activities by Government entity, certain international air transport services and specified exempt financial services, but these are narrowly framed and must be assessed carefully against the detailed rules in the Guidelines.
VAT groups benefit from a 24-month grace period for intra-group transactions only, all external transactions must comply from each member's respective mandatory date.
Implementation timeline and mandatory dates
Ministerial Decision No. 244 of 2025 provides the phased implementation framework as follows:|
Phase |
Threshold |
ASP Appointment Date |
Go Live Date |
| Pilot phase | On nomination by Ministry | Commences from 1 July 2026 | |
| Voluntary phase | All persons regardless of their revenue | Commences from 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 their turnover | 31 March 2027 | 1 October 2027 |
The accredited service provider decision
Every in-scope person must appoint a single Accredited Service Provider to handle both issuance (accounts receivable) and receipt (accounts payable) of eInvoice and eCreditnote. ASPs are accredited under Ministerial Decision No. 64 of 2025. The MoF lists pre-approved providers on its website.The ASP decision is not simply a technology procurement, but a long-term compliance and integration choice affecting system architecture, data flows, control frameworks and service levels.
In evaluating providers, organisations should consider at minimum:
- 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.
- Contractual clarity on responsibilities, incident management and ongoing support.
Note: BDO Digital Solutions FZ-LLC is included on the Ministry's pre-approved provider list.
Peppol framework and participant identifiers
The UAE has adopted a Peppol-based five-corner DCTCE model, under which invoices are exchanged between ASPs and reported to the FTA through a structured network rather than via direct point-to-point integrations.The Guidelines confirm that the primary participant identifier on the Peppol network is derived from the Tax Identification Number (TIN). In the case of VAT registrants, the first 10 digits of the Tax Registration Number (TRN), formatted as 0235:[10-digit TIN].
For VAT groups, each member uses its own individual identifier rather than that of the representative member, supporting transactional traceability at legal-entity level.
Persons not registered for VAT but conducting in-scope business transactions will need to obtain a TIN solely to participate in the system, even where they are not otherwise required to register for VAT.
Data storage, retention and location
Earlier commentary around "data storage in the UAE" generated concern that all eInvoicing data would need to be physically hosted on UAE-based servers. The Guidelines clarify that what matters is secure retention, data integrity and the ability to retrieve complete, readable records promptly upon request by the FTA and not the geographic location of servers or storage infrastructure. This allows continued use of global cloud infrastructure, provided that retrievability and auditability requirements are demonstrably met.Retention periods follow the Tax Procedures Executive Regulations: Generally five years for taxable persons, with an extended seven-year period for records relating to real estate, and longer where periods are under audit or dispute. Businesses should test whether existing local archiving, back-up and document management solutions can support the structured XML formats required under the regime.
Dual-tracking invoicing during transition
A practical complexity arises from the fact that a supplier's obligation to issue an eInvoice does not depend on whether its customer is yet in scope or technically ready. Under the phased timetable, many supply chains will see suppliers go live on eInvoicing before customers are operational, particularly across differing size tiers and sectors.In these cases, suppliers will often need to operate a dual-track model i.e. issuing the structured XML eInvoice via the Peppol network for compliance purposes while simultaneously providing a human-readable PDF or equivalent for customers' operational processes. The Guidelines provide predefined Peppol endpoints for non-ready or non-resident customers, ensuring that invoices can still be routed and reported even where the ultimate recipient is not yet fully integrated.
Provisional, milestone and self-billing arrangements
The Guidelines confirm that there is no separate category for provisional invoices within the eInvoicing framework: any provisional or milestone-based invoice that would ordinarily be issued must be generated as an eInvoice, with subsequent adjustments processed through eCreditnote(s) or additional eInvoice(s). This has implications for construction, professional services and long-term project sectors where provisional billing is common, and will require re-design of billing workflows, approval processes and system configuration.Self-billing remains available under the VAT legislation where the statutory conditions are met, but only in respect of VAT-registered suppliers and only where the party issuing the invoice can itself comply with the eInvoicing 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.
As a common industry practice, insurance businesses and developers issue tax invoices on behalf of brokers using the notation “Tax invoice raised by buyer” to streamline operational processes. Under the UAE Peppol eInvoicing framework, this practice may continue through the self‑billing document model, provided the required conditions are met. Alternatively, businesses may opt to transfer the responsibility to the broker under the new eInvoicing regime, an aspect that will require further consideration going forward.
Reverse charge: Imports versus domestic supplies
The eInvoicing regime draws a clear distinction between import reverse charge scenarios and domestic reverse charge supplies.Import reverse charge on concerned goods and services is outside the scope of eInvoicing.
By contrast, specified domestic reverse charge supplies between VAT-registered persons, including certain electronic devices, precious metals and stones, hydrocarbons, crude and refined oil, natural gas and scrap metal, are within scope. The supplier is required to issue an eInvoice which will not include VAT and clearly referencing the reason for supply being subject to domestic reverse charge treatment.
This reinforces the need for robust tax classification within product and customer master data so that reverse charge scenarios are correctly identified and flagged at the point of invoicing.
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 eInvoice, complemented by additional optional and conditional mandatory fields. This document serves as the primary reference for ERP and billing system configuration, covering seller and buyer identifiers, invoice metadata, monetary totals, tax breakdowns and line-level attributes.Other notable technical requirements:
- No limit on line-items per invoice, enabling high volume and complex billing scenarios.
- Multi-currency invoicing is permitted, but amounts must also be presented in AED using UAE Central Bank exchange rates, with responsibility for accurate conversion resting with the supplier.
- Partial credit notes are allowed, and a single credit note may refer to multiple prior invoices.
- Rounding is applied at invoice level to two decimal places, not per line-item or tax category.
- A single invoice may include taxable, exempt and out-of-scope supplies, subject to correct tax coding and disclosure.
- HSN codes are currently optional, but a mandatory date is expected to be announced. 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
eInvoicing sits at the intersection of tax, finance, IT, procurement, sales and legal. 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.Key design and control considerations include ownership of eInvoicing master data (customer and supplier TINs, Peppol IDs, tax codes); exception-handling and dispute workflows; incident management for system failures and ASP outages; segregation of duties between tax configuration and IT deployment; and audit trail requirements for both VAT and corporate tax purposes. Organisations that treat eInvoicing as an organisation-wide change programme, rather than an isolated IT or finance project, are consistently better positioned to achieve sustainable compliance.
Penalties, enforcement and wider risk
Cabinet Decision No. 106 of 2025 introduces a granular schedule of administrative penalties for eInvoicing non-compliance:|
Nature of non-compliance |
Administrative penalty in AED |
| Failing to appoint an ASP by the prescribed deadline or failing to implement the eInvoicing system | 5,000 per month or part thereof |
| Failing to issue or transmit eInvoice or eCreditnote in the prescribed manner within the required timeframe | 100 per eInvoice or eCreditnote, capped at 5,000 per month per category |
| Failing to notify the FTA promptly of system failures preventing eInvoicing | 1,000 per day or part thereof |
| Failing to notify the ASP of changes to the data required with FTA in prescribed timeline | 1,000 per day or part thereof |
Beyond the formal penalty schedule, the practical consequences of non-compliance 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 competitive disadvantage from operational friction while better-prepared peers transact smoothly.
Practical next steps
We recommend that UAE businesses and international groups with UAE operations take the following near-term actions:- Confirm your mandatory implementation date and assess readiness.
- Map all transaction flows, by legal entity, business line and jurisdiction against the 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 intra-group charging to identify where contractual or process changes are required.
- 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 your 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 is mandatory.
How BDO UAE can support
eInvoicing regime should be approached 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 improve tax transparency, reduce errors, increase efficiency and align the UAE with global digital tax standards.eInvoicing implementation is not simply an overlay on existing processes, it is a tax-to-technology transformation that reshapes how transaction data is created, validated, transmitted and retained.
Drawing on experience across multiple eInvoicing regimes and the UAE's broader indirect tax and corporate tax framework, BDO UAE supports clients across the full implementation lifecycle: from gap assessment, architecture design and ASP to system integration, testing, go-live support and post-implementation optimisation.
BDO middleware backed with in-house ASP connectivity remains as the market differentiator with data-mapping and transformation capabilities, which limits the requirement to update ERP and other invoicing systems. BDO middleware comes with informative customizable dashboards and VAT return preparation module as a standard offering.
If your organisation would like to discuss the implications of the UAE eInvoicing regime or explore tailored implementation support, please reach out to our BDO Team.