Drop or paste an invoice. See every problem, where it is and how to fix it, in English and Arabic. Free, and nothing is stored.
1 Jan 2027Revenue of AED 50m or more
1 Jul 2027Every other business
31 Mar 2027Last day for them to appoint an ASP
What it checks
The UAE rules of PINT AE: TRN format, emirate codes, transaction-type flags, AED amounts per line, credit-note reasons, reverse charge, foreign currency.
The shared Peppol rules: required fields, dates, totals that add up, VAT breakdowns per category, two decimals.
Each problem gets its official rule ID, where it is in the file, and the fix.
BoxAI's own check of the published PINT AE 1.0.4 rules. Not the official validator and not your ASP's validation, which is final.
For the people building it
UAE test invoices, valid and broken on purpose.
Standard rated, a discount, zero rated, exempt, US dollars with AED totals, and a credit note. Plus twelve broken copies, each named by the one rule it breaks, so you can test that your system catches them.
From your code and CI
Check every invoice your system makes.
The same check as an API. Without a key, 50 a day. With Pro, 500 a day and up to 50 per request, so every build checks its invoices.
No. Accredited service providers send your invoices over Peppol to the FTA. BoxAI is the test bench before that: it finds the problems an ASP would reject, while you can still fix them cheaply.
Do you keep my invoices?
No. The invoice is checked in memory and forgotten. Only a count of checks is kept, to apply the daily limit.
Which rules does it check?
The UAE-specific rules of PINT AE 1.0.4 and the core shared Peppol rules (required fields, totals, VAT breakdowns, formats). A few rules need full code lists we only approximate; your ASP's validation is final.
Are the dates final?
They are the Ministry of Finance dates as announced in 2026. Check mof.gov.ae and tax.gov.ae before you plan around them.