The mandate
Under the Continuous Transaction Control model, every VAT-registered business must issue invoices in PINT-AE 1.0.4, transmit them through an accredited service provider, and report to the FTA in near-real-time — with data that never leaves the UAE.
Early adopters begin transmitting live invoices.
Deadline to contract an accredited service provider.
Mandatory issuance and near-real-time reporting.
Small and medium businesses join the mandate.
The problem
“A number sent to a tax regulator cannot be a guess — language models still hallucinate on more than 10% of arithmetic over real figures.”
Every run ends in exactly one of four verdicts
The doctrine
OCR, retrieval and telemetry run only on self-hosted, in-region models. If none is available, it stops — it never falls back to a foreign cloud.
Every regulated figure is recomputed in code with exact decimals. Money never travels as a floating-point number — or an AI guess.
Every extracted value carries its exact source span in the document. A value that cannot be grounded is dropped, not imagined.
Every field becomes tamper-evident proof: hash-chained, Merkle-committed, RFC 3161 timestamped and HSM-signed.
Personal data is tokenized before any log or evidence record exists. One invoice can be proven without exposing any other.
Anything irreversible — an actual filing above all — is gated for a person to approve. The system prepares; a human decides.
Where it sits
Deliberately not another accredited pipe. Aurenta is the ASP-agnostic correctness layer — it makes the data right and defensible first, then hands the validated payload to any accredited provider.
Any input, one standard of output: structured UBL is parsed directly, born-digital PDFs are text-extracted, scans are read by in-region vision-OCR — and every input is recomputed, validated and sealed.
Proof, not promises
Deterministic EN16931 arithmetic — validated against the regulator's own OpenPeppol Schematron.
The sovereign correctness-and-evidence layer for UAE e-invoicing.