Two deadlines are now on every Phase 1 compliance calendar in the UAE. Businesses with annual revenue of AED 50 million or more must appoint an Accredited Service Provider by 30 October 2026 and complete implementation of the Electronic Invoicing System by 1 January 2027. For finance directors, tax teams, and ERP leads across the UAE and within multinationals headquartered in the GCC, UK, Europe, and India, these dates are non-negotiable — and the preparation required between now and go-live is more extensive than it might appear.

The Revenue Threshold That Places You in Phase 1

Ministerial Decision No. 244 of 2025 establishes the phased implementation structure for UAE electronic invoicing. Phase 1 applies to any person conducting business in the UAE whose annual revenue equals or exceeds AED 50 million, calculated by reference to the most recent accounting period for which financial statements are available.

Revenue for this purpose means gross income as defined under applicable legislation in the UAE. Where financial statements are prepared in accordance with IFRS or the applicable local standard, the gross revenue figure from those statements is the reference point. The FTA has made clear that this is an entity-level calculation — not a consolidated group figure — which means each legal entity within a corporate group must be assessed independently against the AED 50 million threshold.

For multinationals with UAE subsidiaries, branches, and free zone entities, this creates an assessment task that frequently reveals unexpected results. A holding company with minimal active revenue sits differently from an operating subsidiary that invoices regularly. A UAE branch of a foreign company must be assessed based on UAE-sourced revenue. The entity-level granularity of phase classification is one of the first significant scoping questions any Phase 1 compliance programme must resolve.

The Two Deadlines That Govern Phase 1 Compliance

30 October 2026 — The ASP Appointment Deadline

Every Phase 1 business must appoint an Accredited Service Provider through EmaraTax by 30 October 2026. The ASP is the accredited technical intermediary through which the business connects to the UAE Electronic Invoicing System — what the global Peppol framework refers to as Corner 2 for outbound invoices and Corner 3 for inbound. Without an appointed ASP, a business has no legal pathway to issue or receive electronic invoices under the system.

The ASP appointment triggers the provisioning of a Peppol Participant Identifier for each legal entity — a globally unique electronic address within the Peppol network that suppliers use to route invoices to your business and that your business uses to route invoices to customers. The participant identifier is entity-specific. A corporate group with ten UAE legal entities in Phase 1 requires ten participant identifiers, provisioned through the ASP onboarding process for each entity separately.

The ASP selection decision involves meaningful due diligence. The Ministry of Finance publishes the list of accredited service providers. All accredited providers must be active Peppol-certified service providers who have completed the OpenPeppol conformance tests. Beyond accreditation, Phase 1 businesses need to assess integration method, contractual terms, SLA commitments, data storage arrangements, and the provider's capacity to handle the specific transaction types and volumes the business generates.

1 January 2027 — The Go-Live Date

From 1 January 2027, every business transaction within scope of the Electronic Invoicing System must be exchanged and reported through the system. Every in-scope B2B invoice and credit note issued by a Phase 1 business must be transmitted as a PINT-AE compliant XML document through the ASP, exchanged with the counterparty's ASP, and reported to Corner 5 — the FTA's reporting layer — within the timeline prescribed by the Minister.

The practical window between the ASP appointment deadline and go-live is approximately 62 days. This is the period in which the business must complete technical integration between its ERP and billing systems and the ASP, validate PINT-AE data field completeness across all invoice types and transaction scenarios, test end-to-end electronic invoice exchange including confirmation message processing, and train operational teams on the new issuance and monitoring workflows. Sixty-two days is sufficient for businesses that begin structured preparation well in advance of October. For businesses that treat the ASP appointment as the start of technical work, it is extremely tight.

What Implementation Actually Requires

Technical Compliance Under PINT-AE

The UAE Electronic Invoicing System operates on the PINT-AE billing specification — a UAE-specific adaptation of the Peppol International Network (PINT) framework. Every electronic invoice and credit note must be structured as a UBL 2.1 XML document that conforms to PINT-AE. The Tax Invoice carries 51 mandatory fields, including UAE-specific extension fields (BTAE fields) that do not exist in conventional ERP invoice output.

For SAP users, this means mapping ERP fields to PINT-AE business terms, building or configuring the generation of UAE extension fields, and implementing the schematron validation rules that govern the XML structure. For Oracle users, similar mapping and development work applies through DFFs and transaction attributes. For businesses using mid-market or cloud accounting systems, the path typically runs through ASP-side transformation — but only where the source system produces structured output that the ASP can process.

The data completeness question is frequently where Phase 1 businesses discover their largest gaps. The PINT-AE fields that rely on customer master data — including Peppol Participant Identifiers, TINs, emirate subdivision codes, and legal registration details — require enrichment of existing customer records on a scale that many businesses have not yet started.

The B2C Boundary

Business-to-consumer transactions are currently excluded from the Electronic Invoicing System. MD 244 Article 5(2) provides that B2C transactions shall not be subject to the system until a future ministerial decision expands the scope. For Phase 1 businesses that operate both B2B and B2C channels — retailers, hospitality groups, healthcare providers — this creates a transaction segregation requirement at the point of invoice issuance. Systems that currently mix B2B and B2C output through a single workflow need adjustment to route only B2B transactions through the electronic invoicing path.

The Scope of What Goes Through the System

Every in-scope business transaction covers all B2B supplies including standard rated, zero-rated, exempt, and out-of-scope supplies, subject to the exclusions in Article 4 of MD 243. Sovereign government activity, certain airline services, and financial services that are exempt from VAT or zero-rated under Article 42 of the VAT Executive Regulation are excluded. Everything else — including intercompany transactions between entities outside the same VAT group — falls within scope.

For UAE businesses with cross-border operations, exports are within scope. Where the overseas buyer has a Peppol participant identifier, the electronic invoice routes through the standard exchange flow. Where the buyer has no Peppol registration, the predefined endpoint 0235:9900000099 must be used on the electronic invoice. This technical distinction must be built into routing logic, not handled manually.

Practitioner Insight: The businesses that arrive at 30 October 2026 in genuine readiness to complete integration within 62 days are those that began their gap assessment in the first half of 2026. The assessment work — mapping legal entities, identifying source systems, profiling transaction types, auditing data completeness, and selecting an ASP — takes weeks, not days. Businesses that have not yet started that work need to begin now.

The Voluntary and Pilot Pathways

MD 244 also established a voluntary implementation pathway, open to any business regardless of revenue, from 1 July 2026. A pilot programme commenced on 1 July 2026 under Ministry supervision. Both pathways allow businesses to begin live operations under the system before the mandatory date, without exposure to the administrative penalties that apply from 1 January 2027 for Phase 1 businesses.

For Phase 1 businesses, voluntary early implementation is a risk mitigation strategy. Identifying and resolving data quality issues, integration errors, and operational process gaps in a live but pre-mandatory environment removes the risk of those issues surfacing on or after the go-live date when penalty exposure begins.

Building the Compliance Programme Now

The distance between where most Phase 1 businesses are today and where they need to be by 1 January 2027 is determined by the readiness of five things: the legal entity and ERP structure map, the transaction universe classification, the technical integration architecture, the data completeness of customer and supplier master records, and the operational governance framework for ongoing compliance. None of these five things resolves itself through the passage of time alone.

For GCC-headquartered groups, the UAE mandate is the first country-level e-invoicing obligation in the region with this technical specificity. For UK and European multinationals with UAE operations, it introduces a Peppol-network obligation in a jurisdiction outside the established EU and European e-invoicing frameworks. For Indian conglomerates with significant UAE revenue, it runs in parallel with the GST e-invoicing system but through an entirely different technical standard. In every case, the UAE Phase 1 programme requires dedicated compliance resourcing and structured programme management.