UAE e-invoicing and the 30 October deadline

What the Ministry actually announced in May

On 10 May 2026 the Ministry of Finance announced targeted amendments to the decisions governing the eInvoicing system, amending Ministerial Decision No. 244 of 2025 and Ministerial Decision No. 64 of 2025.

The headline: the deadline for appointing an Accredited Service Provider moved from 31 July 2026 to 30 October 2026, for persons subject to the system whose annual revenues exceed AED 50 million. The Ministry attributed the change to an assessment of market readiness and to feedback asking for broader technical options and more competitive pricing.

What did not move is the part that matters. Those same businesses must be fully implemented by 1 January 2027. The Ministry was explicit about it.

Three extra months to choose a vendor. Not three extra months to be ready.

The dates, in one place

The timeline runs across four decisions and gets reported in fragments. Here it is whole.

The legal framework sits in Ministerial Decision No. 243 of 2025 on the Electronic Invoicing System and Ministerial Decision No. 244 of 2025 on its implementation, with Ministerial Decision No. 64 of 2025 covering service provider accreditation. The FTA published updated Electronic Invoicing Guidelines, version 1.1, in June 2026.

How the five-corner model works

Businesses expecting a government portal to upload invoices to are expecting the wrong thing.

The UAE has adopted a five-corner Peppol model. Your invoice goes from you, to your Accredited Service Provider, to the buyer's Accredited Service Provider, to the buyer. The fifth corner is the Federal Tax Authority, which receives the reported data in parallel rather than sitting in the middle of the exchange.

Three consequences follow, and each one surprises somebody.

There is no clearance step. You are not waiting for approval before an invoice is valid, which is a meaningful difference from the systems in some neighbouring countries. There is no QR code requirement of the kind Saudi businesses will be familiar with. And you cannot participate without a service provider, because the network is the delivery mechanism, not an optional convenience.

The format is PINT AE, a UAE-specific profile of the Peppol international invoicing standard, exchanged as structured XML. Participants are identified by a Peppol identifier derived from the first ten digits of the TRN, and every document carries a unique identifier.

What is in scope, and what is not

In scope: business to business, and business to government. Both directions of the domestic supply chain.

Out of scope, at least for now: business to consumer. A retailer's till receipts are not part of this phase.

The published carve-outs cover sovereign government activities, exempt financial services, and certain international transport operations by airlines. VAT groups have a transition period for invoices between members.

One point in the June 2026 guidelines deserves attention, because it widens the net beyond what most people assume. The framework is expressed to cover persons conducting business in the UAE irrespective of VAT registration status. If you have been treating e-invoicing as a VAT-registrant problem and you are not registered, that assumption is worth testing against the current guidelines rather than against last year's summary of them.

What non-compliance costs

Cabinet Decision No. 106 of 2025, issued on 24 November 2025, sets the administrative penalties. They are structured to punish delay rather than to produce one large fine.

Businesses using the system voluntarily, ahead of their phase, are not exposed to these penalties. That is a quietly generous feature of the pilot: you can get it wrong in 2026 at no cost, or get it wrong in 2027 at AED 100 a document.

Put like that, the pilot stops looking optional.

The part everybody underestimates

It is not the software. Service providers do this for a living and the integration is a project with a known shape.

It is the data.

A structured format validates. That is the whole point of it, and it is why the transition hurts. Fields your PDF template has been quietly leaving blank for eight years must now be populated, correctly, on every document, or the invoice is rejected before it reaches your customer. The usual casualties are customer TRNs held inconsistently or not at all, legal entity names that differ between your ledger and the trade licence, addresses stored as one free-text line, item descriptions that say "services rendered", and unit and currency codes that were never standardised because nothing ever checked them.

A rejected invoice is not a compliance abstraction. It is an unpaid invoice.

The mistake we see most, watching businesses approach this: treating master data cleanup as a task for the implementation project. By then it is the critical path, and it is being done under time pressure by people who also have a quarter to close.

What to ask a service provider

Vendor selection is where the three extra months are meant to be spent, and demonstrations are designed to answer questions you did not ask. Six that are worth asking.

Have you integrated with our exact ERP, at our version? Not the product family. The version. Connectors age badly.

What happens when an invoice is rejected? Who is told, how quickly, through what channel, and what does the retry look like. This is the single most important operational answer, because a rejected invoice is an unpaid invoice.

How do you handle credit notes and cancellations? They carry the same AED 100 exposure as invoices and they are handled worse by most implementations.

What are your volume limits and what happens at peak? Month-end is when the whole country transmits at once.

How is our master data validated before go-live? A provider that runs your customer file through validation early is doing you the largest favour available. One that discovers problems in December is not.

What is the contracted response time when your platform is down? Failure to notify the Authority of a system failure within the timeline carries AED 1,000 for each day. Make sure the contract obliges them to tell you fast enough that you can comply.

Ask all six of every shortlisted provider, in writing. The answers separate them quickly.

What to do between now and October

Five things, in this order.

1. Confirm which phase you are in. Annual revenue above AED 50 million puts you in the first wave, appointing by 30 October 2026 and live on 1 January 2027. If you are close to the line, work it out properly rather than assuming.
2. Audit your master data now. Customer TRNs, legal names matching the licence, structured addresses, item codes, currency and unit codes. This is the long pole and it does not need a vendor to start.
3. Shortlist from the accredited list. The Ministry of Finance publishes the accredited and pre-approved service providers. Ask each one about your actual ERP, your invoice volume, and what happens on a rejection, rather than about features.
4. Join the pilot. Voluntary participation opened on 1 July 2026 and carries no penalty exposure. Run real invoices through it. Everything you learn is free until January.
5. Fix the process, not only the file. Somebody has to own rejections, and somebody has to notify the Authority if the system fails. Both have penalties attached at a daily rate.

The deadline that matters is not 30 October. Appointing a provider is a purchase order. The deadline that matters is 1 January, and the work in between is yours.