From 2027, UAE businesses must issue invoices to other businesses and to government as structured data through an Accredited Service Provider — not as PDFs attached to emails. If your software cannot produce that data, it needs work before your deadline: 1 January 2027 for businesses with revenue of AED 50 million or more, 1 July 2027 for everyone else.
What is actually changing?
The UAE is adopting a Peppol-based "five-corner" e-invoicing model, set out in Ministerial Decisions 243 and 244 of 2025 and the Ministry of Finance's E-Invoicing Guidelines V1.1, published in June 2026. Under this model, your invoice does not go straight to your customer. It travels as structured data — a format called PINT AE — from your software to an Accredited Service Provider (ASP), which validates it, forwards it to your customer's provider, and reports the data to the Federal Tax Authority as the fifth corner.
The practical meaning is blunt. A PDF attached to an email stops counting as an invoice. So does a Word template with your logo on it. What counts is machine-readable data, delivered through an accredited channel, with the FTA receiving a copy. B2B and business-to-government transactions are in scope; sales to consumers are excluded until further notice.
What are the deadlines?
The Ministry of Finance has published a phased timeline:
- 1 July 2026 — the voluntary phase opened. Any business can start e-invoicing early.
- Revenue of AED 50 million or more — the ASP appointment deadline was 30 October 2026; go-live is 1 January 2027.
- Revenue under AED 50 million — appoint an ASP by 31 March 2027 and go live on 1 July 2027.
- Government entities — 1 October 2027.
Two further rules matter for software planning. E-invoices must be issued within 14 days of the business transaction, and invoice data must be stored inside the UAE. Penalties apply for non-compliance — the Federal Tax Authority is the authority on the details, and secondary sources quoting specific amounts are best treated with caution. The deadlines themselves are the numbers worth pinning to the wall.
What does your software need to do?
Four things, at minimum. It must produce invoices as structured data carrying every field the FTA requires — seller and buyer tax registration numbers, line-level items, quantities, tax rates, and totals that reconcile. It must connect to your chosen ASP, which in practice means an API integration. It must issue invoices within the 14-day window, which punishes any process where invoicing happens when someone gets round to it. And it must keep the data in the UAE.
None of this is exotic engineering. But it assumes your invoice exists somewhere as clean data — not as a layout in a PDF generator fed by free-text fields.
Where do custom and legacy systems fall short?
The common gaps in custom-built and older systems are predictable:
- Free-text invoices — descriptions and amounts typed by hand, totals worked out in a spreadsheet, nothing stored line by line.
- Missing TRNs — customer records with no validated tax registration number, or with it typed into a notes field.
- No API — the system generates a PDF or a print job and has no way to send data anywhere.
- Scattered data — customer details in one tool, prices in a spreadsheet, invoices in another, with no single record holding everything an e-invoice needs.
- Offshore hosting — invoice data sitting on servers outside the UAE, which collides with the residency requirement.
If your system was built for you years ago and the original developer has moved on, this is the moment to get it assessed. Our custom software team spends a fair amount of time retrofitting exactly these capabilities into systems that otherwise work perfectly well.
What if you use off-the-shelf accounting software?
You are in the best position, probably. Established vendors serving the UAE are building PINT AE support and ASP connections into their products, and for most users compliance will arrive as a software update. Your job is to confirm that rather than assume it. Ask your vendor four questions: will the product support the UAE e-invoicing model, by when, is it included in my current plan, and where is my data stored.
Watch for the workarounds, though. Plenty of businesses own accounting software but actually produce invoices in Word or Excel because the software was fiddly. Those side channels stop being a nuisance and become a compliance problem. And if your vendor has no UAE roadmap at all, start planning a replacement now rather than after your deadline.
Does this affect e-commerce stores?
Consumer orders are excluded until further notice, so your checkout does not change on day one. The catch is B2B. If you sell to other businesses — wholesale orders, corporate accounts, bulk purchases where the buyer asks for a tax invoice — those transactions are in scope, and most store platforms cannot capture a buyer's TRN, build a structured invoice and route it through an ASP without extra work.
The sensible move is to separate your B2C and B2B flows now and work out where B2B invoices actually get created. For stores we build, that logic lives in the e-commerce platform itself rather than in a manual step afterwards. And keep an eye on the B2C exclusion — "until further notice" is not the same as "forever".
What does an integration project involve?
A sensible project runs in five steps. First, an audit: list every place an invoice is actually created, which is usually more places than anyone expects. Second, data clean-up — collecting and validating customer TRNs, tidying item and tax data. Third, choosing from the official list of accredited providers. Fourth, the build: mapping your invoice fields to PINT AE, integrating with the ASP's API, and handling rejections, because some invoices will bounce and someone needs to see why. Fifth, testing against real transactions during the voluntary phase, while mistakes are still cheap.
How long to allow depends on the state of your data and your system. As a rough planning range — not a quote — a modern system with clean data might need a few weeks of integration work, while an older custom system with scattered records can take several months. Customer master data is often the slowest part, especially when it lives half in a CRM and half in spreadsheets. If you are weighing this up alongside wider upgrades, our guide to the cost of digitising a small business in Dubai covers how projects like these tend to be priced.
A readiness checklist
Ten minutes with this list will tell you roughly where you stand:
- Know your deadline — is annual revenue above or below AED 50 million?
- List every system and manual process that creates invoices today.
- Check whether your customer records hold validated TRNs.
- Confirm whether your software can export invoices as structured data, not just PDFs.
- Ask your vendor about PINT AE support and ASP connectivity, with dates attached.
- Confirm where your invoice data is physically stored.
- Shortlist an ASP well before your appointment deadline.
- Plan to test during the voluntary phase rather than going live cold.
Where to start
If most of that checklist came back "not sure", that is normal — the mandate is new and the guidance is dense. The useful next step is a systems-readiness review: a short, structured look at how your invoices are created today, what data is missing, and what the gap to compliance actually is in your case. We run these for businesses on custom software and off-the-shelf systems alike. Get in touch and we will tell you plainly whether you need an afternoon of configuration or a proper integration project. Either answer is easier to hear now than in December 2026.