The UAE Ministry of Finance has pushed the Phase 1 ASP appointment deadline back by three months — from 31 July to 30 October 2026 — while keeping the 1 January 2027 mandatory go-live date firmly in place. For businesses at or above AED 50 million in annual revenue, the additional window turns a compressed procurement sprint into a workable readiness project. The pilot, live since 1 July 2026, is already accepting voluntary participants who want to test their integrations before the mandate kicks in.
What Ministerial Decision No. 66 of 2026 actually changes
Issued in May 2026, Ministerial Decision No. 66 does one thing precisely: it moves the deadline by which Phase 1 taxpayers must formally appoint an Accredited Service Provider (ASP) from 31 July 2026 to 30 October 2026. Everything else in the calendar — the pilot, the go-live, the scope of Phase 1 — stays as previously communicated.
Two points are worth pinning down for finance directors reading this now:
- The extension does not touch the 1 January 2027 mandate. From that date, in-scope invoices must flow through the Peppol network via an appointed ASP. There is no signal that the go-live itself will slip.
- Phase 1 scope is unchanged: taxpayers with annual revenue of AED 50 million or above, based on the reference period defined by the FTA.
MoF's stated rationale — echoed by advisers at Deloitte Middle East and reflected in Gulf News and Khaleej Times coverage — is straightforward. Vendor selection, contract negotiation, ERP mapping, and PINT AE conformance testing are running longer than initially assumed. Three additional months give large taxpayers a realistic runway without weakening the go-live commitment.
The DCTCE model and the Peppol 5-corner flow
The UAE has not built a monolithic government tax portal. Instead, it has adopted DCTCE — the Decentralised Continuous Transaction Control and Exchange model — as its national implementation of Peppol PINT AE (Peppol International Non-Tax Invoicing, UAE localisation). In practice, this means invoices travel over an open, accredited network rather than through a central clearing service.
The flow has five corners:
- Corner 1 — the seller creates the invoice inside its ERP or billing system.
- Corner 2 — the seller's ASP validates, converts to PINT AE, and transmits.
- Corner 3 — the buyer's ASP receives, validates, and delivers.
- Corner 4 — the buyer books the invoice.
- Corner 5 — the FTA receives a copy in real time for VAT control.
Two design consequences follow. First, every taxpayer needs its own ASP relationship — there is no way to sit on the sidelines and let a counterparty carry the load. Second, all invoice data remains within the UAE. Data residency is baked into the accreditation criteria, not left to individual vendor policies.
On 1 June 2026, MoF released PINT AE Version 1.1. The update finalises the mandatory field list, tightens validation rules, and closes previously unclear gaps on credit and debit note scenarios. Any ASP shortlist prepared before June should be rechecked against Version 1.1 conformance, not the earlier draft.
The full phasing roadmap
The extension applies to Phase 1 only. The rest of the calendar looks like this:
- Phase 1 — Large taxpayers (revenue ≥ AED 50M). ASP appointment by 30 October 2026 (previously 31 July). Go-live 1 January 2027.
- Phase 2 — SMEs (revenue < AED 50M). ASP appointment by 31 March 2027. Go-live 1 July 2027.
- Phase 3 — Government entities. ASP appointment by 31 March 2027. Go-live 1 October 2027.
The voluntary pilot opened on 1 July 2026 and stays open. Any business — regardless of phase — can join if it is technically ready. For SMEs that already sit inside a Peppol-compatible finance stack, joining the pilot early is cheaper than absorbing the change during Q2 2027, when consultancy capacity will be under pressure.
As of 14 June 2026, the MoF pre-approved list of eInvoicing Service Providers had grown to 41 companies, up from 33 in May. Global names sit alongside regional specialists. The list is a live document — MoF publishes updates on mof.gov.ae, and it is worth checking directly rather than relying on secondary summaries.
A working checklist to 30 October 2026
For a Phase 1 business, the extension is genuinely useful only if the extra three months are spent on the right work. A defensible readiness sequence looks like this:
- Confirm scope and reference period. Verify revenue against the FTA's reference period rules. Borderline cases (revenue hovering near AED 50M) should be documented, with the position agreed by the CFO and external advisers before ASP procurement begins.
- Shortlist ASPs from the MoF-approved list. Focus on providers with published PINT AE Version 1.1 conformance, a delivery track record in the region, and connectors for your specific ERP (SAP, Oracle, Microsoft Dynamics, Odoo, Zoho). Ignore any provider not on the official list.
- Map invoice data end to end. Run a field-by-field mapping between your ERP output and the PINT AE mandatory fields. This is where most Phase 1 programmes stall — missing tax classification codes, incomplete party identifiers, and inconsistent unit-of-measure data are the usual culprits.
- Contract and integrate. Sign the ASP agreement with clear SLAs on validation error handling, FTA reporting continuity, and archiving. Deploy the connector in a sandbox first and reconcile a full month of live invoice volume before switching production traffic.
- Join the pilot before year-end. Once integration is stable, enrol in the voluntary pilot. Running live traffic through the network in Q4 2026 surfaces edge cases — foreign-currency invoices, self-billing, credit notes against prior-period invoices — while the FTA is in a supportive posture rather than an enforcement posture.
Advisers at Deloitte, Avalara, and Cleartax converge on the same message: the businesses that will find 1 January 2027 painless are the ones treating 30 October 2026 as a soft deadline for full readiness, not a hard deadline for signature.
