The UAE E-Invoicing Timeline, Quarter by Quarter: What to Do in Q4 2026, Q1 2027 and Q2 2027
The UAE e-invoicing mandate arrives in two waves, 1 January 2027 and 1 July 2027. Which wave you are in decides what the next three quarters should look like. This is the dated plan, with honest durations for each piece of work.
Most articles on UAE e-invoicing explain what the mandate is. Fewer tell you what to do this quarter. The answer depends on one fact: whether your business is in Phase 1, mandatory from 1 January 2027 for revenue of AED 50 million or more, or Phase 2, from 1 July 2027 for everyone else. The two groups have different calendars, and the same action is prudent for one and overdue for the other.
This article sets out the dated milestones, then a plan per quarter for each phase, then how long each of the six readiness jobs takes in practice. The durations are ranges from our projects, not promises; the ERP and integration work is where the time goes.
Key takeaways
- Phase 1 businesses have one quarter left. Q4 2026 is cut-over preparation, not planning.
- Phase 2 businesses have three quarters. Q4 2026 is scoping and ASP selection; Q1 2027 is the ERP work; Q2 2027 is testing and go-live.
- Voluntary early adoption removes penalty exposure, which makes Q1 or Q2 2027 go-live attractive for Phase 2 businesses.
- The penalty under Cabinet Decision No. 106 of 2025 is AED 5,000 per month or part month of delay, including failure to appoint an ASP.
- "Too late" is not a date; it is the point where the remaining jobs no longer fit the quarters left.
The milestones on one table
The framework is run by the Ministry of Finance with the Federal Tax Authority on a decentralised Peppol-based network, the five-corner model, in which structured PINT AE invoices travel from supplier to buyer through Accredited Service Providers (ASPs) while the FTA receives the tax data in near real time. Scope is B2B and B2G; B2C is out for now. These are the dates that matter.
| Date | Milestone | Who it affects |
|---|---|---|
| July 2026 | Pilot programme begins | Pilot participants and ASPs |
| 30 October 2026 | Deadline to appoint an ASP | Businesses with revenue of AED 50M or more |
| 1 January 2027 | Phase 1 mandatory go-live | Businesses with revenue of AED 50M or more |
| 1 July 2027 | Phase 2 mandatory go-live | Other in-scope businesses |
Quarter-by-quarter plan for both phases
The six readiness jobs are the same for everyone: confirm scope and date; choose and contract an ASP; clean master data; make the ERP produce compliant structured invoices and credit notes; integrate ERP to ASP and test end to end; train the team and set controls. What differs is which quarter each job lands in.
| Quarter | Phase 1 (live 1 Jan 2027) | Phase 2 (live 1 Jul 2027) |
|---|---|---|
| Q4 2026 | ASP contracted and connected. ERP invoice and credit-note templates finished. Master data cleaned. End-to-end testing with real documents. Train users, freeze controls, plan the 1 January cut-over. | Confirm scope and revenue band. Score the ERP against the data requirements. Shortlist ASPs and sign one. Start the master-data clean-up, which needs no system change. |
| Q1 2027 | Live. Monitor rejections daily for the first month. Fix root causes in the ERP, not by hand. Close the first VAT return with structured data. Confirm records retention is working. | ERP configuration or upgrade. Build and test structured invoices and credit notes for every transaction type. Connect to the ASP test environment. Consider voluntary early go-live for low-risk invoice streams. |
| Q2 2027 | Stabilise. Extend controls to branches and inter-company flows. Review supplier e-invoices arriving from Phase 2 counterparties as they come online. | End-to-end testing with real documents from each department. Train users. Freeze controls. Go live before 1 July, ideally in May or early June, so the first month is not also the deadline month. |
How long each job takes in practice
These are ranges we have seen, and they overlap. Nothing here is a commitment for any specific business; a readiness review turns a range into a date.
| Readiness job | Typical range | What stretches it |
|---|---|---|
| Confirm scope and date | 1 to 2 weeks | Group structures, free zone entities, mixed B2B and B2C activity |
| Choose and contract an ASP | 2 to 6 weeks | Procurement cycles, legal review, ERP compatibility questions |
| Clean master data | 3 to 8 weeks | Customer count, missing TRNs, product tax codes never set |
| ERP produces compliant invoices and credit notes | 4 to 12 weeks | Old ERP versions, spreadsheet invoicing, many transaction variants |
| Integrate ERP to ASP and test | 3 to 8 weeks | Custom ERPs, ASP sandbox availability, test-case coverage |
| Train the team and set controls | 2 to 4 weeks | Number of branches and invoicing staff, approval design |
Run in parallel, a business on a modern platform such as Odoo with reasonable data can complete the programme within a single quarter. A business invoicing from spreadsheets, or on an ERP version the vendor no longer supports, should assume two quarters and treat the ERP job as the critical path.
The voluntary-adoption exclusion
Cabinet Decision No. 106 of 2025 sets a penalty of AED 5,000 per month or part month of delay in implementing the system, and failing to appoint an ASP counts. The same decision excludes businesses that adopt voluntarily ahead of their mandatory date from the penalty regime.
For Phase 2 businesses this changes the calculation. Going live in Q1 or early Q2 2027 is not just prudent; it removes penalty exposure and gives the team a quieter period to find problems. For Phase 1 businesses that missed the October ASP deadline, the exclusion does not apply, and the only way to limit the exposure is to close the gap fast.
What "too late" looks like in each quarter
Too late is not a calendar date. It is the point at which the remaining jobs no longer fit the time left, so the business will be issuing non-compliant invoices on its phase date.
- Q4 2026, Phase 1: no ASP contract signed, or an ERP that still cannot produce a structured credit note. Both are recoverable only by compressing testing, which is where rejections come from in January.
- Q4 2026, Phase 2: nothing is too late yet. Not having confirmed scope and started ASP selection by December means Q1 will be rushed.
- Q1 2027, Phase 2: ERP work not started. If structured invoices are not being tested by the end of March, the April to June window has to hold the ERP job, integration, testing and training at once.
- Q2 2027, Phase 2: no ASP, or an ERP that has not sent a test invoice by the start of May. At this point the plan becomes a short-term bridge through the ASP's own tools while the ERP catches up.
Whichever quarter you are in, the first step is the same: know your phase, score the six jobs honestly and put dates on them. A UAE e-invoicing readiness review with a senior consultant does that in a single session and tells you whether the quarters left are enough.
Not sure which quarter you are actually in?
Book a readiness review with a senior Kaido consultant. We confirm your phase, score the six readiness jobs against your current ERP and give you a dated plan that fits the time you have left.
Book a discovery call