Is my invoice data uploaded anywhere?

No. The file is read and checked by JavaScript in your browser. This page carries no analytics script and makes no network request with your data; closing the tab removes it.

Which rules does the check apply?

Four PINT AE rules where an identifier exists (IBR-128-AE emirate subdivision codes, IBR-104-AE AED line amounts, IBR-002-AE exchange rate decimals, IBR-154-AE transaction type code) plus eleven readiness checks: mandatory fields, unique invoice numbers, ISO dates, seller and buyer TRN format, lines present, quantity times price, VAT category and rate, line VAT arithmetic and header totals reconciling to lines.

What export format does it need?

A CSV with one row per invoice line and the header fields repeated on each row, which is the shape most accounting systems export. Column names are matched automatically and can be corrected on screen.

Home / E-invoicing / Readiness check

E-invoicing · PINT AE

Run your invoice export against the rules first.

Drop a CSV export from your accounting system. Fifteen checks run in your browser: the four PINT AE data rules that reject ordinary UAE invoices, plus the readiness checks a provider would fail you on. You get every finding with the value as exported and the field to fix.

Nothing is uploaded. This page carries no analytics script, makes no request with your data, and closing the tab removes it. If you would rather see it work first, load the sample export.

Drop your CSV here

One row per invoice line, header fields repeated on each row. Up to a few thousand rows is fine.

Read only. Your file is not sent anywhere. Sample data is invented and carries the faults we see in real exports.

Readiness

Invoices

Lines

Findings

Fix list, by the field that causes it

Findings by rule

Rule	What it checks	Findings	Severity	Source

Every exception, HIGH first

Sev	Invoice	Line	Rule	Field	Value as exported	Finding	Fix

Want the fixes made, not just listed? We correct the master data at source, derive the fields nothing stores, and run the month again until it passes. Twenty minutes to scope it, no charge.

Book 20 minutes WhatsApp

What the fifteen checks are

IBR-128-AE Emirate is a PINT AE subdivision code (AUH DXB SHJ UAQ FUJ AJM RAK), not an ISO 3166-2 code. HIGH.
IBR-104-AE AED line amount and AED VAT amount on every foreign currency line. HIGH.
IBR-002-AE Exchange rate present on foreign currency invoices, at most six decimals. HIGH.
IBR-154-AE Transaction type code is up to eight characters of 0 and 1. HIGH.
R-01 Mandatory header fields present (emirate only required for UAE buyers). MEDIUM.
R-02 Invoice numbers unique in the export. HIGH.
R-03 Issue date is ISO 8601 and not in the future. MEDIUM.
R-04 Seller TRN is 15 digits. HIGH.
R-05 Buyer TRN present for UAE business buyers, and 15 digits when present. MEDIUM.
R-06 Every invoice has at least one line. HIGH.
R-07 Mandatory line fields present. MEDIUM.
R-08 Quantity times unit price equals the line amount (discounts must be a separate field). MEDIUM.
R-09 VAT category is one of S Z E O AE and the rate agrees with it. MEDIUM.
R-10 Line VAT equals line amount times rate. MEDIUM.
R-11 Header totals reconcile to the lines, and total equals net plus VAT. HIGH.

Sources: PINT AE v1.0.3 jurisdiction rules on docs.peppol.eu, Ministerial Decision 244 of 2025 as amended 10 May 2026, FTA TRN format. Deadlines: revenue AED 50 million and above appoint an accredited provider by 30 October 2026 and go live 1 January 2027; below AED 50 million appoint by 31 March 2027 and go live 1 July 2027. The same rules run as a Python tool with an Excel report: see it on the Work page. Background: UAE e-invoicing readiness and the five fields to fix first.

Run your invoice export against the rules first.

Fix list, by the field that causes it

Findings by rule

Every exception, HIGH first

What the fifteen checks are

One clear conversation can changehow you see your entire business.

One clear conversation can change
how you see your entire business.