Find the invoices that will be rejected — before you pay for an ASP.
The UAE e-invoicing system checks every invoice against 51 mandatory PINT AE fields. Records that passed for a decade start failing. I check yours first.
The problem
From 1 January 2027, VAT-registered businesses in the UAE must issue invoices as structured data, transmitted through a Ministry of Finance accredited service provider. Every invoice is validated automatically against the PINT AE specification.
Most companies are carrying years of records that nothing has ever validated — missing or malformed TRNs, addresses with no country code, dates and currency codes in the wrong format, duplicate invoice numbers. None of it mattered before. All of it fails now.
The expensive way to discover this: appoint a provider, integrate, go live, and then watch invoices bounce one at a time — after the money is spent and the deadline has passed.
What I do
I run 31 validation rules, mapped to the PINT AE requirements, against an export of your customer master and invoice history. You get back:
- A report listing every record that would be rejected, and the rule it fails
- A defect workbook your team can work through, row by row
One working day. The first scan, on one dataset, is free — you see the output before any money is discussed.
What I am not
Sijil Data is not an accredited service provider. I do not transmit invoices and I do not submit anything to the Ministry of Finance or the FTA.
This runs before your ASP, not instead of it. If you have already chosen a provider, nothing here competes with that — it just means fewer of your invoices bounce when you switch on.
Your data
Two ways to do this. You pick.
1 Send an export. I send you the exact list of columns the rules read, first. You delete every other column before anything leaves your side. The scan does not need them and does not want them.
2 Send nothing. I send you the scanner and you run it on your own machine. No data moves at all.
Sijil Data is a US sole proprietorship. If cross-border data handling is a question for your compliance team, option 2 removes the question entirely.
Scope — worth being precise about
This validates the invoices you issue — outbound, accounts receivable — against PINT AE.
It does not do supplier-invoice work: duplicate payment detection, purchase-order price variance, three-way invoice/PO/GRN matching, supplier anomaly detection. That is a different problem and a different product, and this is not it.
The timeline
| Phase | Who | Appoint ASP by | Mandatory |
|---|---|---|---|
| Wave 1 | Revenue ≥ AED 50m | Oct 2026 | 1 Jan 2027 |
| Wave 2 | Revenue < AED 50m | Mar 2027 | 1 Jul 2027 |
| Government | B2G | — | 1 Oct 2027 |
Dates per the Ministry of Finance e-invoicing programme. Verify against the MoF site for your own planning — I am not your tax adviser.