It is not a PDF
A compliant e-invoice is structured XML, not a document you email. Your system has to produce machine-readable data.
The UAE is moving to mandatory structured electronic invoicing. It is the biggest change to how businesses here issue invoices since VAT arrived in 2018 — and unlike VAT, it changes the plumbing rather than just the paperwork. This page explains the timeline, what an Accredited Service Provider actually does, and what your accounting or ERP system needs to be able to produce.
A compliant e-invoice is structured XML, not a document you email. Your system has to produce machine-readable data.
Invoices travel through an Accredited Service Provider, which reports them to the FTA. Appointing one is a required step, not optional tooling.
Consumer-facing sales are outside the current scope. If you sell only to consumers, this phase does not apply to you.
AED 50 million revenue is the dividing line between the first and second mandatory waves.
Most of the work is not compliance paperwork. It is whether your existing system can emit the right XML and talk to an ASP.
This timeline has been revised more than once. Plan against it, but verify with the FTA before committing.
As published by the Ministry of Finance.
Businesses can begin issuing compliant e-invoices ahead of their mandatory date. Going early is the low-risk option: you find the problems while they are still optional.
Businesses with annual revenue of AED 50 million or more are expected to have appointed their Accredited Service Provider by this date.
E-invoicing becomes mandatory for businesses at AED 50 million revenue or above.
Businesses below the AED 50 million threshold are expected to have appointed their ASP.
E-invoicing becomes mandatory for the remaining businesses in scope.
Government bodies come into scope.
Always confirm against the Federal Tax Authority or your tax adviser. This page is general information, not tax advice.
Worth understanding, because it explains why the ASP step is unavoidable.
The UAE has adopted a decentralised model built on the Peppol network, using a UAE-specific profile called PINT-AE. In practice an invoice moves like this:
Your ERP or accounting software creates the invoice as structured XML with every mandatory field populated.
Your Accredited Service Provider checks it against the specification and transmits it onto the network.
The invoice arrives in your customer's system through their provider — no email, no re-keying.
Reporting to the FTA's platform happens as part of the flow, not as a separate filing you remember to do.
The practical implication: invoices that fail validation do not quietly go out looking slightly wrong. They are rejected. Data quality that was tolerable when a human read the PDF becomes a blocker when a schema validates it.
The three capabilities, and where systems usually fall short.
Invoices as PINT-AE compliant XML with all mandatory fields. If your system can only produce a PDF or a CSV, that is the gap.
Usually an API integration. Ask your ASP which systems they already have connectors for before you assume yours is covered.
You need to retain the transmitted invoice and the network response, so compliance can be evidenced later.
Tax registration numbers, legal entity names and addresses must be correct and complete. Validation is unforgiving about fields humans used to fudge.
Standard, zero-rated, exempt and reverse-charge have to be right at line level, not corrected in the return afterwards.
Older self-hosted deployments often need an upgrade before the localisation is even available. This is the item most likely to blow up a timeline.
Your ASP deadline is 30 October 2026 and mandatory compliance is 1 January 2027. Start now: audit whether your system can emit PINT-AE XML, shortlist ASPs, and confirm a connector exists for your platform. If it does not, that is a development project with a lead time.
You have until 31 March 2027 for the ASP and 1 July 2027 to comply. Use the extra time deliberately: clean your customer and tax-registration master data first, because that work is independent of whichever system you end up on.
This is the forcing function. You will need a system that produces structured invoices, so combine the two decisions rather than buying twice. Our ERP buyer's guide covers how to choose.
B2C is outside the current scope. Keep an eye on later phases, but you do not need to act now.
We audit what you run today — Odoo, another ERP, or accounting software plus spreadsheets — and tell you plainly what needs to change before your deadline, and what it will take. If you are already fine, we will say that too.