Aurenta — the sovereign validation layer for UAE e-invoicing Proud of UAE — فخورين بالإمارات
Aurenta tax invoice INV-2024-0876
Hover to inspect the sealed layer
Aurenta tax invoice INV-2024-0876, straightened for analysis

The mandate

UAE e-invoicing is becoming law —
on a hard clock.

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.

JUL 2026 Voluntary pilot

Early adopters begin transmitting live invoices.

OCT 2026 ASP appointed

Deadline to contract an accredited service provider.

JAN 2027 Large taxpayers live

Mandatory issuance and near-real-time reporting.

JUL 2027 All businesses

Small and medium businesses join the mandate.

Non-compliance: penalties from  AED 5,000 / month

The problem

“Send, then fix” is a penalty machine.

TODAY

Send, then fix

  • Errors surface only after the FTA rejects the invoice
  • Penalties are already incurred by the time you know
  • No reliable proof of what was sent, or when
ERPFTA ✕penalty
WITH AURENTA

Fix, then send

  • Every field extracted and grounded to its source
  • Every figure recomputed deterministically in code
  • Every rule validated, then sealed as evidence
ERPAURENTA ✓ASPFTA
“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

PASSfigures reconcile — safe to proceed
REVIEWdiscrepancy — a human checks first
BLOCKEDfatal violation — filing prevented
REFUSEDsovereignty at risk — fails closed

The doctrine

Six rules it never breaks.

01

Sovereignty, fail-closed

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.

02

Computed, not generated

Every regulated figure is recomputed in code with exact decimals. Money never travels as a floating-point number — or an AI guess.

03

Grounding required

Every extracted value carries its exact source span in the document. A value that cannot be grounded is dropped, not imagined.

04

Evidence-first

Every field becomes tamper-evident proof: hash-chained, Merkle-committed, RFC 3161 timestamped and HSM-signed.

05

Data minimization

Personal data is tokenized before any log or evidence record exists. One invoice can be proven without exposing any other.

06

Human-in-the-loop

Anything irreversible — an actual filing above all — is gated for a person to approve. The system prepares; a human decides.

Where it sits

One step before the regulator.

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.

Your ERP UBL · PDF · scans
AURENTA Compliance-as-Code Extract · Compute · Validate · Seal
Accredited ASP transmission
FTA near-real-time reporting

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

Engineered to prove itself.

0automated tests
0%code coverage
0/23mutation-testing score
0UAE requirements, each mapped to a test that fails loudly

Deterministic EN16931 arithmetic — validated against the regulator's own OpenPeppol Schematron.

Get every invoice right —
before the regulator sees it.

The sovereign correctness-and-evidence layer for UAE e-invoicing.