The short answer: by 30 October 2026 a large UAE business needs a signed agreement with an Accredited Service Provider (ASP), an ERP that can produce every mandatory field of the UAE invoice format, and a tested connection between the two. From 1 January 2027 a PDF attached to an email stops counting as an invoice for VAT purposes between businesses. The date was confirmed again in May 2026, when the Ministry of Finance moved the provider deadline but kept the go-live where it was.
The Dates That Matter
| Who | Appoint an accredited provider by | Issue and receive e-invoices from |
|---|---|---|
| Revenue above AED 50 million | 30 October 2026 | 1 January 2027 |
| Revenue of AED 50 million or less | 31 March 2027 | 1 July 2027 |
| Government entities (business to government) | As published | 1 October 2027 |
The thresholds and dates come from Ministerial Decision No. 244 of 2025, amended on 10 May 2026 to push the first provider deadline from 31 July to 30 October 2026. The same announcement put the number of approved providers at 32, with more in the final stages of accreditation. Sales to consumers are outside the mandate for now, as are a small number of exempt categories, so a retailer's till receipts are not affected, but its supplier invoices are.
What Counts as an E-Invoice Here
The UAE has adopted a decentralised model on the Peppol network. Your system hands the invoice data to your provider, the provider converts it into the UAE profile of the Peppol format (PINT AE), sends it to the buyer's provider, and both providers report the tax data to the Federal Tax Authority. Nothing is uploaded to a government portal by hand, and the buyer receives the invoice as structured data, not as a document to retype.
Three consequences follow. A PDF, a scanned image or a Word document is not an e-invoice, even if it is sent electronically. Every invoice must carry the mandatory data set published by the Ministry of Finance in February 2026, which runs to around fifty fields plus conditional ones, including tax categories, the buyer's identifiers and line-level detail. And an invoice can be rejected by the buyer's provider for a missing or malformed field, which turns a formatting problem into a cash-flow problem.
What Changes Inside Your ERP
Most of the work is not the connection to the provider; it is the data behind the invoice. In the ERP implementations we run on Odoo, ERPNext, SAP Business One and Microsoft Dynamics 365 Business Central, the gaps we find first are the same every time:
- Customer and supplier master data. Tax registration numbers, legal names and the identifiers your provider will use to address the other party. Records created over years by different people are rarely complete.
- Invoice content. Tax category codes per line, unit codes, discount handling, currency and exchange-rate fields, and credit and debit note references back to the original invoice.
- Document flows the format does not expect. Proforma invoices used as real invoices, invoices edited after issue, and consolidated monthly bills that mix tax treatments.
- Status handling. Your ERP needs to know whether each invoice was accepted, rejected or is still pending at the provider, and someone needs to own the rejections.
- Archiving and reporting. The structured invoice, not the PDF, is now the record, and your VAT return has to reconcile to what the provider reported.
The major ERP vendors and their partners are adding the UAE format through connectors and the providers' own integrations. Whether your installation is ready is a different question: a standard product can carry the fields, but only if your configuration captures them and your team enters them.
A Six-Step Plan That Fits in the Time Left
- Inventory your invoice flows. Every system that issues or receives invoices, including the ones outside the ERP: the online store, the subscription tool, the branch that still uses Excel. Each flow either moves into the ERP or needs its own connection.
- Choose the provider. Shortlist from the Ministry's accredited list on three things: a certified connector for your ERP version, how rejections and status updates reach your team, and what the contract says about volumes and support hours. Appoint before 30 October 2026, with enough weeks left to test.
- Clean the master data. Tax numbers, legal names and addresses for every active customer and supplier, validated rather than assumed. This is the step most companies underestimate, and the one that drives most rejections later.
- Configure and map. Tax codes, document types, numbering, credit note links and the field mapping to PINT AE, done in a test environment with real invoices from the last quarter.
- Test with partners. Send and receive with two or three large customers and suppliers before the deadline. Rejections during testing are cheap; rejections in January are not.
- Train and go live with monitoring. Accounts payable and receivable need a daily view of pending and rejected invoices, and a procedure for correcting and reissuing within the rules.
Where SoftwareBiz fits. Our ERP and CRM implementation team configures the platform, maps the fields and connects the provider; our data integration team cleans and matches the customer and supplier records; and our finance and accounting outsourcing team can run the daily issuing, rejection follow-up and reconciliation inside your accounting system once it is live. The formats in Saudi Arabia and Pakistan differ, but the data problems are identical, and we configure all three from one clean master data set when a finance team covers several entities.
If You Also Invoice in Saudi Arabia or Pakistan
Companies with entities across the region are now dealing with three different mandates. Saudi Arabia's ZATCA Phase 2 reached its final wave on 30 June 2026, so the work there is fixing integrations that still reject invoices. Pakistan's FBR requires all sales-tax-registered persons to issue digital invoices through a licensed integrator, with corrections allowed only within 72 hours of issue. A single ERP configured once for all three, with one set of clean master data, is cheaper than three separate projects, and it is the approach we recommend when the entities share a finance team.
What to Do This Week
Confirm which band your revenue puts you in, list every system that issues invoices, and ask your ERP partner one direct question: which PINT AE fields does our current configuration not capture? If the answer is a shrug, that is the gap to close first. The provider can be appointed in a day; the data takes weeks.