UAE e-invoicing: what a small business actually has to do

Every few weeks somebody forwards me an article about UAE e-invoicing and asks whether it applies to them. The answer is almost always yes, and the reason they think it might not is the same every time.

The headlines lead with AED 50 million. If you run a workshop with 6 staff, that number reads like permission to stop reading.

What the threshold actually decides

The AED 50 million line sorts businesses into phases. It does not sort them into in and out.

Here are the dates as they stand:

• Revenue at or above AED 50 million: appoint an accredited service provider by 30 October 2026, issuing e-invoices from 1 January 2027.
• Revenue below AED 50 million: appoint a provider by 31 March 2027, issuing from 1 July 2027.
• Government entities: appoint by 31 March 2027, live from 1 October 2027.

A voluntary pilot has been running since 1 July 2026, which is where the accredited providers have been testing their side of it.

The part that catches people out

E-invoicing here does not work by logging into a government website and typing your invoice in. Invoices are exchanged through an accredited provider in a standard format, and the provider passes them on.

So the readiness question is not really about software. It is about whether the information on your invoices exists somewhere structured enough to hand over.

That is where most of the small businesses I work with will struggle, and it has very little to do with tax.

Where invoice data actually lives in a small business

I spend a lot of my time watching how UAE businesses run day to day, and the pattern repeats. Ask an owner where an invoice comes from and you get a clean answer. Watch it happen and you get something else.

The customer name is in a WhatsApp thread. The agreed price was verbal and somebody wrote it on a job sheet. The item description gets retyped from memory because there is no list. The tax number arrived as a photo of a document 8 months ago and nobody can find it now.

None of that is unusual. It works because a person holds it together. It stops working the moment a machine has to read it.

An accredited provider can transmit an invoice. It cannot invent details that were never written down.

What I would do between now and next year

None of this needs to wait for a vendor, and the first step costs nothing.

Trace one invoice backwards. Take a recent one and find where every field came from. Customer details, line items, price, tax number, dates. For each one, note whether it was read from a system or remembered by a person.

Count how much gets retyped. Anything typed twice is a place where 2 versions can disagree, and disagreement is what gets an invoice rejected.

Find your gaps before somebody else finds them for you. Missing tax numbers, customers with 3 different spellings, prices that live only in a chat thread. These take weeks to clean up and minutes to discover.

Then appoint a provider. The Ministry of Finance maintains the accredited list and there is a real number of them already. That part is a procurement decision, and it gets easier once you know what you are handing them.

What I am not

I am not an accredited service provider, and Implemnt does not transmit invoices. What I do is the part before that: making sure the information exists, in one place, in a form that can be handed over cleanly.

If your invoice details currently live across a POS, a notebook, 3 WhatsApp threads and one person's memory, that is the work. The deadline just puts a date on it.

If you are weighing up whether to fix that with new software or by connecting what you already run, our custom versus off-the-shelf breakdown covers how that decision usually goes.