The timeline, by revenue band
The Ministry of Finance split the rollout into two business phases plus a government phase. Each phase has two dates that are easy to mix up: the day you must have appointed an accredited service provider, and the day e-invoicing actually goes live for you.
- Missing the ASP appointment draws a fine under Cabinet Decision No. 173 of 2026 (which replaced Decision 106 of 2025 in October 2026): AED 5,000, then AED 5,000 for each further month, capped at AED 50,000 in any 12 months
- Revenue decides the band, not headcount or legal form — check which side of AED 50 million your last financial year lands on
UAE e-invoicing deadlines (Ministerial Decisions 243 and 244 of 2025)
| Who | Appoint an ASP by | E-invoicing live from |
| Businesses with revenue ≥ AED 50 million | 30 October 2026 | 1 January 2027 |
| All other businesses | 31 March 2027 | 1 July 2027 |
| Government entities | — | 1 October 2027 |
What changed in October 2026
On 19 October 2026 the Ministry of Finance amended the e-invoicing rules to reduce the load on businesses. The go-live dates did not move. The changes, as reported at the time:
- Transactions between members of the same VAT tax group are excluded from e-invoicing for two years from 1 January 2027
- E-invoices and their data no longer have to be stored inside the UAE; keep them for the period the Tax Procedures Law sets
- The rule to notify the FTA of a system failure within two business days was removed
- Missed the 30 October 2026 ASP deadline? Appoint a provider now: the 1 January 2027 go-live still applies, and the monthly fine for a late appointment runs until you do
What an accredited service provider actually is
The UAE chose a decentralised "five-corner" Peppol model. Your invoice does not go from your software straight to the FTA: it goes to an accredited service provider (ASP) — a Peppol access point accredited by the Ministry of Finance — which delivers it to your customer's ASP and reports the tax data to the FTA.
That has a practical consequence for software selection: no ERP or accounting system is itself the legal transmission channel. The ERP creates and validates the invoice; the ASP you appoint transmits it. Any vendor claiming its accounting product alone makes you compliant is skipping the appointment you are legally required to make.
PINT-AE: the format your invoices must speak
UAE e-invoices use PINT-AE, the Emirates profile of the international Peppol invoice (the Ministry of Finance published the mandatory field list in February 2026). It is structured XML, not PDF: customer TRN, line-level tax categories, totals that must reconcile — each rule is machine-checked before the invoice travels.
The useful question for any system you evaluate: what happens when an invoice fails a PINT-AE rule? In ERP HRM Solution the checks run before the invoice is issued, so a failing invoice stays a draft showing the rule codes — it never leaves as a bad invoice you discover at the ASP.
How the work splits between your ERP and your ASP
A clean division of labour, worth writing into both contracts:
- ERP: create the invoice from the sales document, validate it against PINT-AE, hand it to the ASP, track the status (sent → delivered → accepted or rejected), and file what comes back
- ASP: transmit over the Peppol network, deliver to the buyer's access point, report the tax data to the FTA
- Inbound too: supplier e-invoices arrive from your ASP — in ERP HRM Solution they land in Purchases → E-invoice Inbox and become draft bills, so purchase invoices stop being retyped
- Invoices to customers with a UAE TRN and to customers outside the UAE are sent when issued; B2C invoices to UAE customers without a TRN are not sent for now
Your to-do list, in order
For a business in the second phase (under AED 50 million), the calendar to 1 July 2027 looks like this:
- Now — confirm your revenue band and check your master data: every business customer needs a correct TRN, and your own entity details must match the FTA record
- Before 31 March 2027 — appoint an ASP; if your ERP connects through an ASP connector (ours does), confirm the API compatibility with your software vendor before signing, not after
- Q2 2027 — connect the ASP in your software (in ERP HRM Solution under Settings → E-invoicing), send test invoices and fix the master-data rejections while they are cheap
- From 1 July 2027 — issue through the pipeline and watch the status flow; a rejected invoice needs a correction and a reissue, so make someone own that queue
One honest note about software claims
ERP HRM Solution is not an ASP and does not claim to be one. It creates and validates PINT-AE invoices and sends them through the FTA accredited service provider you appoint — one whose API is compatible with our connector, so ask us before you sign with a provider. The same honesty test is worth applying to any vendor: ask them to name where their product ends and the ASP begins.