UAE e-invoicing: the October 2026 checklist for finance and IT teams

UAE businesses with annual revenue above AED 50 million must appoint an Accredited Service Provider by 30 October 2026, and their mandatory e-invoicing begins on 1 January 2027. This checklist walks finance and IT teams through what to decide, clean up and test before the deadline, in the order that avoids rework.

The UAE e-invoicing programme has moved from announcements to dates. As of September 2026, the pilot programme and voluntary adoption are available from 1 July 2026. Businesses with annual revenue above AED 50 million must appoint an Accredited Service Provider (ASP) by 30 October 2026 (extended by the Ministry of Finance from 31 July 2026) and go live on 1 January 2027; businesses below AED 50 million appoint by 31 March 2027 and go live on 1 July 2027; government entities appoint by 31 March 2027 and go live on 1 October 2027. The Ministry of Finance sets the thresholds and can adjust them, so treat the dates below as the plan to verify against, not the final word.

What follows is the checklist we run with clients. It is ordered deliberately: the decisions at the top shape the work at the bottom, and doing them in the wrong order is how businesses end up paying twice.

1. Confirm which phase you are in

The phases are defined by revenue, and the first mandatory wave targets businesses above AED 50 million in annual revenue. Confirm your figure with your auditors, confirm which legal entities are in scope if you run a group, and confirm whether any entity has a different VAT registration that changes the picture. Write the answer down with the date you confirmed it, because the question will be asked again in every meeting.

2. Understand the five-corner model before you talk to vendors

The UAE model runs on the Peppol network. Your business (corner one) sends invoice data through your ASP (corner two) to your customer’s ASP (corner three) and on to your customer (corner four), while the tax data is reported to the Federal Tax Authority (corner five). The practical consequence is that your ASP transmits what your systems give it. It does not repair incomplete invoices, and it cannot create a tax registration number that your ERP never captured.

3. Inventory every system that issues an invoice

Most businesses discover during this step that invoices come from more places than the ERP. List every source: the ERP or accounting system, point-of-sale terminals, subscription billing tools, a custom portal, a project-management system that raises progress invoices, and any spreadsheet a department still uses for exceptions. Each source either has to feed the ASP directly or be consolidated into one that does.

4. Check what each system can actually produce

• Can it export structured invoice data, through an API, a database view or a supported file format, rather than only a PDF?
• Does it capture the fields the UAE format requires, including the customer’s tax registration number, line-level tax treatment and the correct units and currencies?
• Does the vendor commit in writing to supporting the UAE requirements, and by which date?
• Can it handle credit notes, partial deliveries, foreign-currency invoices, intercompany transactions and free-of-charge items correctly?

A system that fails these checks is not automatically a system you replace. In most cases a thin integration layer collects the data, validates it, fills the gaps and handles the ASP connection, while your team keeps working the way they work.

5. Clean the master data now, not during testing

Data quality is where UAE and Saudi projects lose the most time. Missing tax registration numbers, duplicated customers, items with no meaningful description and inconsistent units of measure all surface as rejected invoices in testing. Fixing them is finance work that can start today, in parallel with vendor selection, and it shortens the integration phase more than any technical decision.

6. Choose the ASP on the criteria that matter in month six

Every provider on the accredited list has passed the same accreditation. Compare them on existing connectors to your ERP, support presence and language in your time zone, the pricing model as your document volume grows, where invoice data is stored and what you can export if you leave, and contract terms including notice periods and exit assistance. We wrote a separate guide on choosing an ASP if you want the long version.

7. Decide who owns the integration

Three parties can build the connection between your systems and the ASP: the ASP itself, your ERP vendor, or an independent integrator. The right answer depends on how many source systems you have and how much customisation sits in them. Whoever builds it, insist on one named owner for the end-to-end flow, because the failure mode in every e-invoicing project is a rejected invoice that the ASP blames on the ERP and the ERP vendor blames on the ASP.

8. Test the edge cases, not the happy path

• A standard B2B invoice with multiple tax treatments on different lines
• A credit note that partially reverses an earlier invoice
• An invoice in a foreign currency with the AED equivalent
• An intercompany invoice between two entities in your group
• A self-billed invoice if your business receives them
• A rejected invoice: who is notified, how fast, and what the correction process looks like

9. Plan the monitoring before go-live

Once invoices stop clearing, revenue stops moving. Someone has to notice within minutes, not at month-end. Define who watches the queue, what alerts fire, and what the manual fallback is if the ASP connection drops during a quarter close.

10. Keep the paper trail

Record the phase confirmation, the ASP contract, the integration design, the test evidence and the go-live sign-off. The FTA can ask for it, your auditors will ask for it, and the next finance director will thank you for it.

The October date is not when invoicing changes. It is the last sensible moment to make the decisions that need three months of work behind them.

PluginZ is not an accredited service provider, by design. We are the engineering partner that assesses your systems, cleans the data flow, integrates your ERP, POS or custom software with the ASP you choose, and tests every edge case before it carries real money. If you want to know where your business stands against this checklist, a readiness assessment is the first step, and we will say plainly if little work is needed.