E-Invoicing Readiness Assessment

What is actually being assessed

The mandate moves invoices from documents to structured data: Structured XML, UAE PINT AE specification, exchanged over the Peppol network. It applies to All persons conducting business, regardless of VAT registration status, so VAT registration is not the test — revenue band is.

That changes what an invoice has to contain and when errors surface. Today a slightly wrong invoice is sent, paid, and corrected in the next period. Under this model it is rejected at the network and does not arrive, which means the payment cycle stops. The failure moves from your accountant’s reconciliation to your sales ledger, in real time.

The assessment tests three things: which band you sit in, whether your system can produce and transmit compliant structured output, and whether the data in it would pass. In most SMEs the third is where the work is.

Who needs it

Every business conducting activity in the UAE, whether or not VAT registered. Practically, the businesses that need the assessment earliest are those with high invoice volume, complex billing arrangements, or an accounting system that was never designed for structured output.

Construction and contracting businesses, where milestone billing, retention and variations currently live outside the accounting system. Trading and distribution businesses with large item masters. E-commerce businesses whose checkout was never designed to collect tax registration numbers. And any business still invoicing from a spreadsheet or document template, where there is nothing to integrate until something is built.

How we do it

Every engagement is different in detail, but the shape is consistent:

1. Establish the band. Revenue determines your dates and everything else follows from it. This takes an hour and it is the step people skip.
2. Assess the system. Can your accounting software or ERP produce structured output in the required specification and connect to an accredited provider? For some SME packages the honest answer is no.
3. Audit the invoice data. Customer legal names against trade licences, tax registration numbers, structured addresses, item master consistency, and tax categories applied at line level rather than invoice level.
4. Map the difficult transactions — credit notes and their linkage to the invoices they correct, milestone billing, retention, advance payments, self-billing, intra-group.
5. Quantify the gap. How many customer records are incomplete, how many item codes are inconsistent, how many invoice types have no structured equivalent today.
6. Build the remediation plan with sequence, effort and owner, working backwards from your band’s go-live date.
7. Decide on the pilot, open from Open from 1 July 2026, which lets you fail in a test environment rather than a live one.
8. Set the provider selection criteria from your actual integration requirements, so procurement follows the technical position rather than preceding it.

The data problems we find, in order of effort

Every assessment turns up the same categories, and the ranking is consistent:

• Customer master data — legal names that do not match the trade licence, missing tax registration numbers, addresses held as one free-text field. The largest single piece of work, because it requires contacting customers
• Tax categorisation at line level — applied at invoice level today in most SME systems, which does not survive the structured format
• Item master — inconsistent descriptions, missing unit codes, duplicates accumulated over years
• Credit note linkage — credit notes issued without referencing the invoice they correct
• Billing arrangements outside the system — milestone, retention and advance payment schedules maintained in spreadsheets
• Invoice numbering — non-sequential, restarted, or duplicated across entities or branches

The first of these is the one that determines the timeline. Collecting tax registration numbers from a few hundred customers is not technically difficult and takes months, because it depends on other people responding.

Why the pilot is worth entering

The voluntary pilot opens Open from 1 July 2026. For a business in the under-AED-50m band, whose live date is 1 July 2027, that is a considerable head start.

Entering early means a rejected invoice is a test result rather than an unpaid one. You discover which of your invoice types fail, which customer records are incomplete, and how your system behaves under the actual specification — while there is still a year to fix it.

Businesses that wait will be discovering the same things in production, against a live deadline, competing for the same implementation resource as everyone else who waited. The cost difference between those two paths is substantial and it is entirely a function of timing.

Where this goes wrong

The same problems recur, and every one of them was cheaper to prevent:

• Acting on the wrong band’s deadline. The widely quoted 30 October 2026 belongs to businesses with Revenue AED 50 million or more.
• Treating provider selection as the project. It is weeks of procurement wrapped around months of data work.
• Assuming the provider will fix the data. They cannot — they do not know your customers.
• Discovering the system cannot do it in the quarter before go-live, when a migration takes two.
• Ignoring credit notes and milestone billing, which are the transaction types with no structured equivalent today.
• Skipping the pilot, and choosing to fail in production instead of in test.
• Assuming VAT-registered means in scope and unregistered means out. The mandate covers All persons conducting business, regardless of VAT registration status.

Timing and deadlines

Now, for anyone in either band. Working backwards from 1 July 2027 for most SMEs: the pilot from Open from 1 July 2026, provider appointed by 31 March 2027, integration and testing across the preceding quarters, and data remediation starting before all of it because it is the longest task and it depends on third parties.

Businesses with Revenue AED 50 million or more have materially less time: 30 October 2026 to appoint and 1 January 2027 to go live, and the data work needed to support that should already be running.

What you get

• Your revenue band and the dates that actually apply to you, in writing
• A system capability assessment, including whether migration is required
• A data gap analysis quantified by record count rather than described
• A transaction type map covering credit notes, milestones, retention and advances
• A remediation plan sequenced backwards from your go-live date
• Provider selection criteria based on your integration requirements
• A recommendation on the voluntary pilot

Documents we will ask for

What we ask for up front:

• Annual revenue, to establish the band
• Details of the accounting system or ERP and its version
• A sample export of customer master data
• A sample of invoices covering every type you issue
• Item or service master data
• Details of any billing arrangements maintained outside the system
• Monthly invoice volume
• Details of intra-group invoicing, where relevant

Fees

Fixed fee, scoped on invoice volume and the number of systems involved. A single-system business with straightforward invoicing is a contained assessment; a group with several entities, multiple billing systems and complex contract billing is larger.

Remediation is quoted separately once the gap is known, and much of it is work your own team can do with a specification rather than work that needs us. We would rather hand over a plan you can execute than sell you the execution.

Related

Frequently Asked Questions

Last reviewed 27 July 2026. Rates, thresholds and deadlines change — the e-invoicing provider deadline has already moved once. Confirm current requirements with the Federal Tax Authority before acting, or ask us to check your position.