Your software is ready. Is your data?

There are two deadlines, and most businesses only know about one

The UAE Ministry of Finance implementation timeline sets a go live date for each category of business, and separately an earlier date by which an accredited service provider must already be appointed. The appointment deadline is the one that is routinely missed, because public discussion focuses almost entirely on the go live dates.

Large and major companies, meaning revenue of 50 million and above, had to appoint an accredited service provider by 31 July 2026 and go live on 1 January 2027. Small and medium companies, meaning revenue up to 50 million, must 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. Voluntary exchange and the pilot phase both opened in July 2026.

Revenue is assessed on the latest financial statements, or on projected revenue for the ongoing financial year in the case of a newly established company. The full table, its footnotes and the governing legislation are published by the Ministry of Finance on its e-invoicing initiative page.

For a small or medium business the practical deadline is earlier than the official one. The large companies you sell to go live on 1 January 2027. From that date your invoices to them enter a network that expects a structured document, and your own 2027 date stops being the one that governs your revenue.

What every customer record must carry

A UAE e-invoice is addressed, not sent. Each participant on the network holds a unique identifier, and the buyer cannot be reached without one. That identifier has to exist on the customer record before an invoice referencing it can be built.

Alongside it, each customer requires a legal registration identifier type selected from a fixed set of permitted kinds, together with the matching number. The permitted kinds are a commercial or trade licence, an Emirates ID, a passport, and a cabinet decision. Choosing trade licence makes the licence number itself a required field.

Entities established in a free zone carry an additional beneficiary identifier. Business to consumer customers sit outside the current scope, which means a customer record has to be classified correctly in the first place, because misclassification silently changes whether an invoice is reported at all.

For most UAE businesses this is the single largest gap. Customer masters built over years for the purpose of printing an address rarely carry a network identifier or a registration type, and the requirement applies to every active account, not to new ones only.

What every item must carry

Every line of an e-invoice must classify what was actually sold. Each item requires a type classification identifying it as goods, as a service, or as both.

Goods require a customs classification code, commonly known as an HS code. Services require a service classification code. An item that is genuinely both requires both codes present. This is mandatory rather than advisory, and it is enforced at the line level, which means a single unclassified item can stop an otherwise correct invoice.

This is where the work is genuinely large. A trading company holding a few thousand active items, none of which has ever needed a customs classification for its own accounting, is looking at a classification exercise across the entire catalogue. The volume is knowable in advance, which is why it should be measured before it is scheduled rather than discovered during a go live.

What every address must carry, and the field almost nobody has

The issuing company must hold a properly structured address flagged as its own company address, and that address must record the emirate as a discrete field.

This is the requirement most often missed, because in practice the emirate is usually typed into a street or city line as free text. Free text is not a field. A structured document has nowhere to put it, and an address that reads correctly on a printed invoice can still fail validation on a structured one.

What every invoice line must carry

Each line requires a VAT category. The UAE set contains six: standard rated at 5%, zero rated, exempt, reverse charge, not subject to VAT, and margin scheme. Four of these are widely known. Reverse charge and margin scheme are frequently absent from systems configured before the mandate, and reverse charge in particular is ordinary in UAE business to business trade.

Two categories carry conditional requirements. An exempt line requires an exemption reason code drawn from the authority’s published list. A reverse charge line requires a nature code. Neither can be left blank and neither can be improvised.

The categories are also arithmetically enforced. A line declared standard rated must carry a rate of 5.00. A standard rated line with a zero rate is rejected outright, with a rule reference naming the exact field at fault, which means a tax configuration that has quietly drifted becomes visible only at the moment of submission.

The invoice header carries its own requirements: a document type code, a tax point date distinct from the issue date, and period codes where the billing is recurring. Recurring arrangements outside the standard frequencies require a written reason rather than a code alone.

Credit notes, and the documents arriving in the other direction

A credit note is not simply a negative invoice. It requires a reason code drawn from the authority’s own list, distinguishing a cancellation from an amendment, from a supplier driven correction, from a buyer driven one, from an adjustment of amounts, from a void. The reason is part of the record, not part of the covering email.

The direction most businesses have not considered is inbound. Under the network model a supplier’s sales invoice becomes your purchase record automatically. The document arrives structured and already reported, and it references items and a supplier that your system may not recognise.

That changes the nature of the problem. Today an unfamiliar supplier invoice is a filing question resolved at month end. Under e-invoicing it is a live record entering your books, and whether your master data can receive it determines whether your payables stay clean.

Why the software was never the hard part

The integration layer that connects a business system to the network is widely available, including as open source. Availability was never the constraint and it is not a differentiator.

The constraint is that a compliant system cannot manufacture data it does not have. Install anything you like: if the customer has no network identifier, if the item has no classification code, if the address has no emirate, the invoice does not validate. The system will tell you so, one invoice at a time, at the least convenient moment.

The requirement is also retrospective. It applies to records created years before this mandate existed, which is why the honest first question is not which platform to choose. It is how much of your existing data already satisfies the list above, expressed as a number rather than an impression.