Check
Drop an invoice and get every problem with its official rule ID, where it is, and the fix. Free, nothing stored.
BoxAI checks UAE invoices against the PINT AE rules and tells you what is wrong, where, and how to fix it, in English or Arabic. Then test your system with invoices broken on purpose.
No sign-up · nothing stored · English and Arabic
IBR-128-AEThe emirate “Dubai” is not a UAE code. Use DXB in CountrySubentity.
AccountingSupplierParty/Party/PostalAddressIBR-193-AEThe unique identifier (UUID) is missing. Every UAE invoice needs one.
InvoiceIBR-104-AELine 1 needs its amount and VAT in AED.
Invoice/InvoiceLine[1]Fix these three and it passes.
Why now
Every UAE invoice must be PINT AE XML, sent through an accredited service provider. The UAE adds about 130 rules to the Peppol standard, and it is easy to miss one.
What you get
Drop an invoice and get every problem with its official rule ID, where it is, and the fix. Free, nothing stored.
UAE test invoices for the cases that trip systems up: discounts, zero rated, exempt, US dollars, credit notes. Plus copies broken on purpose, one rule each.
Call the same check from your code and CI with an API key, so every build proves its invoices still pass.
Who it is for
Plans
$0 forever
$19 a month
$79 a month
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.
No. The invoice is checked in memory and forgotten. Only a count of checks is kept, to apply the daily limit.
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.
They are the Ministry of Finance dates as announced in 2026. Check mof.gov.ae and tax.gov.ae before you plan around them.