UAE E-Invoicing 2027: What Your ERP, POS and Billing Software Needs
The UAE's e-invoicing mandate starts on 1 January 2027. The deadlines, how the Peppol five-corner model works and the development work your ERP, POS or SaaS product needs.
Table of Contents
The UAE is moving all B2B and B2G invoicing onto a national e-invoicing system, and the first businesses go live on 1 January 2027. If you run an ERP, POS, billing platform or SaaS product used by UAE companies, your software has to produce structured invoice data and hand it to an accredited service provider instead of emailing a PDF. This guide explains what is changing, the deadlines, and what development work it takes.
What is changing
Under Ministerial Decision No. 244 of 2025, VAT-registered businesses in the UAE must issue and receive e-invoices through an Accredited Service Provider (ASP) listed by the Ministry of Finance. An e-invoice here is not a PDF: it is a structured electronic document in the UAE's PINT AE format, exchanged over the Peppol network. B2C invoices are outside the mandate for now, until the Minister decides otherwise.
Deadlines
| Who | Appoint an ASP by | Go-live |
|---|---|---|
| Voluntary early adopters | — | From 1 July 2026 |
| Businesses with revenue of AED 50 million or more | 30 October 2026 (extended from 31 July) | 1 January 2027 |
| Businesses with revenue below AED 50 million | 31 March 2027 | 1 July 2027 |
| Government entities | 31 March 2027 | 1 October 2027 |
The ASP deadline for large businesses was extended, but their go-live date was not. Software vendors serving those businesses effectively have until the end of 2026 to be ready.
How the five-corner model works
The UAE uses a decentralised "five-corner" model built on Peppol:
- Corner 1 — the supplier creates the invoice in its own system.
- Corner 2 — the supplier's ASP validates it and sends it over Peppol.
- Corner 3 — the buyer's ASP receives it.
- Corner 4 — the buyer gets the invoice in its own system.
- Corner 5 — the Federal Tax Authority receives the tax data from the ASPs.
Your software sits in corners 1 and 4. It doesn't talk to the tax authority directly; it talks to the business's chosen ASP, usually through a REST API or a file exchange.
What your software needs to do
1. Capture complete, structured data
Every field the PINT AE specification needs must exist in your database, not just on the printed layout: supplier and buyer legal names and tax registration numbers, Peppol identifiers, invoice type, line items with quantities, unit prices and VAT categories, totals, currency and payment terms. Free-text fields that hold several values ("TRN / address / phone") need to be split.
2. Map your invoices to PINT AE
Build a mapping layer that turns your internal invoice, credit note and debit note objects into valid PINT AE documents. Keep it separate from your invoicing logic so you can update it when the specification changes — it will.
3. Integrate with one or more ASPs
Each customer chooses its own ASP, so a SaaS product usually needs a connector framework rather than a single integration. Handle authentication, submission, status callbacks and retries, and show the status of each invoice in your UI.
4. Handle rejections and corrections
Invoices can fail validation. Your users need to see why, fix the data and resubmit, and corrections must go through credit or debit notes rather than editing an issued invoice.
5. Receive invoices too
Businesses must also receive e-invoices. Accounts-payable modules should import incoming PINT AE documents from the ASP, match them to purchase orders and route them for approval, rather than waiting for PDFs by email.
6. Keep records
Store the structured invoice, the ASP's responses and timestamps, so you can show auditors exactly what was sent and when.
A practical timeline for software teams
- Now: audit your invoice data model against PINT AE and list the missing fields.
- Next 4–6 weeks: add the fields, build the mapping layer and pick the first ASP to integrate with your earliest customers.
- Before go-live: test end to end in the ASP's sandbox, including rejections, credit notes and incoming invoices, then pilot with a small group of customers.
How we can help
We build and update ERPs, POS systems and billing platforms for businesses in the Gulf — including an all-in-one ERP for Dar Al Eitemad Center in the UAE — and integrate them with tax platforms such as Saudi Arabia's ZATCA FATOORA. See how we work with UAE businesses or explore our custom software development service.
This article is a technical guide, not tax advice. Confirm your obligations and dates with your tax adviser and the Ministry of Finance.
