Ebor Labs

UAE e-invoice file check

Check a UBL or PINT AE invoice file against the UAE mandate before your accredited service provider rejects it. Structure, mandatory fields, tax numbers and whether the totals reconcile.

If your revenue is AED 50 million or more: you must appoint an accredited service provider by 30 October 2026 and have e-invoicing running by 1 January 2027. Ministerial Decision No. (66) of 2026, which amended the earlier deadline of 31 July 2026. Below that revenue the Ministry has not yet published a date.

Your invoice file never leaves this device. Nothing is sent, nothing is stored, gone when you close the tab.

Check an invoice file

A UBL 2.1 or PINT AE invoice in XML. Checks structure, mandatory fields, tax numbers and whether the totals reconcile.

Drop an XML file here, or

Checking a customer list instead? Customer master data is handled by the data readiness workbench, which reads CSV and Excel, recognises the column names used by fourteen finance systems, and returns a corrected file alongside the exceptions.

Where your invoice file goes: nowhere

You can verify it in the network tab: open your browser's developer tools, go to Network, and run a check. You will see no request leave the page at all. Offline works too — disconnect from the internet after the page loads and every check still runs.

How far this has been checked

This tool evaluates 87 of the 88 UAE-specific assertions in the PINT AE Schematron, taken from the assertions themselves rather than from a reading of them. Each is checked against the specification's own validator, and each has a test that proves it fires on a bad document and stays silent on a good one. The one it does not evaluate cannot be evaluated by anyone: ibr-187-ae's test expression is literally true(), so it can never fire, whoever implements it.

That is one of two rule sets. A UAE invoice is also validated against the base PINT rules — 170 further assertions governing document structure, totals, dates and identifiers for every country using this format — and against 44 of those restated inside the UAE file. This tool evaluates all 214 of those as well, which is why the figure for what is checked is 301 of 302 rather than 87 of 88.

On the spreadsheet side there are 25 checks. 17 are measured against the same validator, by projecting a record into an invoice and comparing the verdicts. The remaining 8 are data-quality judgements that no specification makes at all — duplicates, malformed email addresses and the like — which can be right or wrong on their own terms but never on the specification's.

What none of this establishes is that an invoice this tool passes will be accepted in production. The comparison is against the specification's own validator on test documents; no invoice checked here has yet been submitted to an accredited service provider and had the outcome predicted. Every rule and every check is listed by identifier in docs/rule-coverage.md in the project repository, with what each one rests on.

Whether a supply is standard rated, zero rated, exempt or outside scope is a question for a registered UAE tax agent. This tool does not answer it and is not tax advice.

Where these rules come from

Where a judgement is needed we say so rather than deciding for you. How far each check has been verified is set out above.

Legal basis: Federal Decree-Law No. 16 of 2024 amending the VAT Law, with Ministerial Decisions No. 243 and 244 of 2025, No. 64 of 2025 on accreditation, and Cabinet Decision No. 106 of 2025 on penalties. Links may move; the Ministry’s site is the authority, not this page. Nothing here is tax advice.