If your finance team is still treating UAE e-invoicing as a 2027 problem, you are already behind. The Federal Tax Authority (FTA) has locked in two firm cutoffs that will reshape how every VAT-registered business issues and receives invoices: 1 January 2027 for companies with annual revenue of AED 50 million or more, and 1 July 2027 for the rest. This blog gives you a clear view of what Phase 2 and Phase 3 actually require, what your teams need to fix inside your ERP, invoicing workflow and supplier network, and how to sequence the work over the next twelve to eighteen months without disrupting billing operations.
The UAE Electronic Invoicing System is being introduced in waves, not overnight. The legal framework was set out in Ministerial Decisions No. 243 and 244 of 2025, with the penalty schedule confirmed under Cabinet Decision No. 106 of 2025.
The rollout currently confirmed by the Ministry of Finance runs as follows:
Intra-group transactions within a VAT group are transitionally exempt until 1 January 2029, but every other in-scope flow falls under the dates above.
Many finance leaders still assume this is a large-enterprise issue. It is not. The mandate covers e-invoicing B2B B2G UAE transactions for almost all persons conducting business in the country, including free zone entities and even non-VAT-registered businesses that trade with other companies. Pure B2C sales remain outside the mandate for now.
Only invoices issued in the structured PINT-AE (Peppol International Invoice, UAE Profile) XML format and transmitted through an FTA-accredited ASP will be legally valid. PDF, Excel and scanned invoices will not qualify as tax invoices for Phase 2 and Phase 3 transactions. Your buyer’s system will simply reject them, and input VAT recovery becomes a problem for the recipient.
The exchange itself runs on the Peppol-based 5-corner model, formally called Decentralised Continuous Transaction Control and Exchange (DCTCE). Both the sender’s ASP and the receiver’s ASP report the Tax Data Document to the FTA independently, giving the tax authority a near real-time, dual-verified view of every covered transaction.
If your group turnover crosses AED 50 million, the 2026 window is not a runway, it is a construction zone. Practical readiness work usually breaks into four streams:
This is the stage where an advisory-led readiness assessment pays for itself. A structured gap analysis across regulation, ERP, master data and workflow lets you sequence twelve months of work in the right order, rather than firefighting surprises in December 2026.
If your revenue sits below AED 50 million, the temptation is to let Phase 2 businesses work out the issues first. That approach has three flaws.
First, from 1 January 2027, your Phase 2 customers will begin routing invoices through Peppol. If you cannot receive PINT-AE invoices, you will delay your own supplier payments and strain commercial relationships.
Second, ASP capacity will tighten sharply in early 2027. Providers will prioritise larger clients close to Phase 3 deadlines, and integration slots will get scarce.
Third, the technical work does not shrink because your business is smaller. Master data hygiene, ERP mapping and workflow redesign take proportionally similar effort.
A realistic Phase 3 plan starts readiness assessment by Q2 2026, ASP shortlisting by Q4 2026, integration and testing across Q1 and Q2 2027, and go-live rehearsals in June 2027.
A few misconceptions keep resurfacing in board discussions:
The Phase 2 and Phase 3 rollout is less about a single deadline and more about a coordinated programme spanning regulation, ERP configuration, ASP integration, master data hygiene and workflow change. Businesses that treat it as a technology purchase tend to miss the compliance depth. Businesses that treat it purely as a tax project tend to underestimate the ERP work. The organisations that go live cleanly usually combine both perspectives from the start, and start early enough to test properly before their mandatory date.
AA Technologies works with UAE finance leaders to run readiness assessments, guide vendor-neutral ASP selection, coordinate ERP integration and stand up managed compliance operations tailored to your industry and system landscape. If you want an independent view of where your business sits against the Phase 2 or Phase 3 timeline, book a UAE e-invoicing readiness assessment or explore our e-invoicing advisory services.
Phase 2 becomes mandatory on 1 January 2027 for businesses with annual revenue of AED 50 million or more. These businesses must appoint an FTA-accredited ASP by 30 October 2026. From the go-live date, all in-scope B2B and B2G invoices must be issued in PINT-AE XML format and transmitted through the Peppol-based 5-corner network. Traditional PDF or Excel invoices will not be accepted as valid tax invoices for these transactions.
Phase 3 covers all remaining in-scope VAT-registered businesses in the UAE with annual revenue below AED 50 million, with mandatory go-live on 1 July 2027. It also captures non-VAT-registered businesses conducting qualifying B2B or B2G supplies. Government entities follow a parallel track and must go live by 1 October 2027. Free zone entities are largely included, subject to specific rules around Qualifying Free Zone Person status and intra-group flows.
No. The current UAE Electronic Invoicing System scope, under Ministerial Decisions 243 and 244 of 2025, covers business-to-business and business-to-government transactions only. Consumer sales are excluded during the initial rollout. The Ministry of Finance has indicated that B2C may be brought into a later phase, so retailers, hospitality operators and consumer-facing service providers should still monitor updates and prepare their systems for eventual coverage.
Under Cabinet Decision No. 106 of 2025, administrative penalties apply for failing to appoint an ASP or implement the system on time. Beyond the direct fine, the operational impact is often more damaging. Your invoices to Phase 2 customers may be rejected, input VAT recovery on your purchases may be disrupted, and payment cycles can slow significantly. Early ASP appointment protects both your compliance status and your working capital.
Most ERPs, including SAP, Oracle, Microsoft Dynamics, Zoho, QuickBooks and Tally, will need configuration changes and a validated integration to an accredited ASP. The system must produce PINT-AE compliant XML, handle credit notes and self-billing scenarios, and pass validation before transmission. Custom or legacy systems typically require API middleware. A readiness assessment against your specific ERP version is the fastest way to size the work required.
