The pilot is live. ASP appointment closes in 107 days 30 October 2026

Proud of UAE — فخورين بالإمارات
Book a Demo
COMPLIANCE-AS-CODE. COMPLIANT.

The sovereign validation layer for UAE e‑invoicing.✦

Get every invoice right — before the regulator sees it.

Compliance-as-Code extracts every field with its source, recomputes every figure in exact decimals, and seals the result as tamper-evident evidence — before your accredited service provider transmits it.

Pre-flight
Precision
Deterministic
Calculations
Evidence Vault
& Audit Trail
PINT-AE 1.0.4
Compliant
In-Region
UAE Processing
Book a demo Run a free 12-month sweep
Aurenta tax invoice INV-2024-0876
Hover to inspect the sealed layer
Aurenta tax invoice INV-2024-0876, straightened for analysis
▮ SCANNING…

Every invoice, judged.
Every judgment, sealed.

The control plane your auditors will actually trust.

AURENTA·CONTROL PLANE PERIOD · Q3 2026 Illustrative data
Documents processed12,847
In review23
Recoverable identifiedAED 412,900illustrative
Evidence roots sealed214
Review queue5 of 23 · newest first
InvoiceVendorAmountVerdictSignal
INV-2026-1042Al Sarh Building Materials LLC AED 84,300.00PASS sealed ✓
INV-2026-1043Khaleej Foods Trading FZE AED 18,750.00BLOCKED DUPLICATE_INVOICE_NUMBER — disguised via zero-width character
INV-2026-1044Marjan Logistics DMCC AED 240,000.00REVIEW BANK_DETAIL_CHANGE — payee hash mismatch since last payment
INV-2026-1045Dana Gulf Hospitality LLC AED 9,600.00REVIEW INPUT_VAT_BLOCKED — Art. 53 (entertainment)
INV-2026-1046Sidra Technical Services AED 15,800.00PASS recomputed ✓ · sealed ✓
  1. Verdicts with reasons. Every run ends in exactly one of four verdicts — and every verdict carries a reason trail grounded to the source document.
  2. A human decides. REVIEW items queue for a person. Approving is one click; rejecting requires a written reason — recorded, sealed, attributable.
  3. The fraud firewall. Deterministic detectors flag what statistics and structure reveal: disguised duplicates, changed bank details, structured splits. Advisory, never blocking — releasing money is always a human act.
  4. Input-VAT recoverability. Every supplier invoice gets a recoverable / blocked / at-risk verdict with a reason trail — before it enters your return.
  5. Sealed, then provable. Each period rolls up to a Merkle root, signed and exportable. Your auditor can verify it offline — without trusting us.
  6. Regulator-ready in Arabic. The same evidence, as a plain-language narrative your board and your regulator can read — in English or Arabic.

Recover

Recover money you already lost.

That's the live view. Here's what it finds in your history: a deterministic backtest over 12–24 months of paid AP surfaces the money that already left — ranked, evidenced, and priced only on what your own approver verifies.

01 · Backtest

Historical Forensic Sweep

Upload 12–24 months of paid AP history. A deterministic backtest surfaces money that already left: duplicate payments — even under disguised invoice numbers — ghost vendors, shared-payee mule networks, post-approval bank-detail changes, arithmetic discrepancies. Ranked as a recovery worklist.

02 · Standing memory

Duplicate-Payment Ledger

A standing already-paid memory that catches the duplicate the moment it recurs — even via a different channel, VAT period, or provider. The boundary no single-batch check can see.

03 · Rate card

Contract-Rate Leakage

Every invoiced unit rate reconciled against your negotiated rate card, recomputed to the fils — the price-creep an ERP's invoice-to-PO match structurally cannot see.

04 · Art. 53

Input-VAT Recoverability

Every supplier invoice gets a recoverable / blocked / at-risk verdict with a reason trail, before it enters your return; sealed per-period roll-ups.

AED 500,000 The buyer's input VAT is the real uncapped enforcement — AED 500,000 at risk on a single AED 10M invoice. One hundred times the seller's annual fine cap. Illustrative scenario

You pay a success fee only on what your own approver verifies as recoverable — and the fee is computed from cryptographically sealed amounts, so neither side can move the number afterward.

Run a free 12-month sweep →

The fraud firewall

Catch the fraud before the money moves.

Thirty-plus deterministic detectors across three tiers — per document, behavioural, and network & file forensics. Screen the payment proposal CSV thirty minutes before money moves — a per-line pay/hold recommendation, sealed as evidence. And when a document is clean on its face, it's corroborated against registries, your buyer feeds and your own history — because a fabricated invoice can still be pixel-perfect.

Two sentences we treat as contract terms

Advisory, never blocking — releasing money is always a human act.

Every signal is deterministic and explainable — no ML black box.

See the full detector matrix →

The mandate

UAE e-invoicing is no longer coming.
It's running.

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.

1 July 2026 Pilot live

Not a future date — early adopters are transmitting production invoices now.

30 October 2026 ASP appointment deadline

Contract an accredited service provider by this date — extended once from 31 July 2026.

1 January 2027 Phase 1 mandatory

Revenue ≥ AED 50 million: issuance and near-real-time reporting become law.

July 2027 Next wave

The mandate widens to the next tranche of businesses.

The deadline moved once. Go-live didn't.

Non-compliance: AED 100 per non-issued e-invoice — penalties of up to AED 5,000 per month (Cabinet Decision No. 106 of 2025)

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
ERP→FTA ✕→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
ERP→AURENTA ✓→ASP→FTA
“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, Ed25519-signed — RFC 3161-capable and HSM-ready by design.

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.

ASP-agnostic — works with the systems you already run

Questions, answered

Before you ask the regulator.

When does UAE e-invoicing become mandatory?

In phases: a voluntary pilot opens in July 2026, accredited service providers must be appointed by October 2026, large taxpayers go live in January 2027, and all remaining businesses — including SMEs — join by July 2027.

What is PINT-AE 1.0.4?

PINT-AE 1.0.4 is the UAE's national e-invoice format — its profile of the international Peppol / UBL 2.1 standard, established under Ministerial Decisions 243 and 244 of 2025. Every invoice must be structurally and arithmetically perfect in this format to be accepted.

Are you an ASP?

No — and deliberately not. Aurenta is the ASP-agnostic correctness layer. You appoint any accredited service provider; Aurenta makes the invoice correct and defensible before your ASP transmits it.

What happens when an invoice fails validation?

Every run ends in exactly one of four verdicts: PASS (safe to proceed), REVIEW (a human checks a discrepancy first), BLOCKED (a fatal violation prevents filing), or REFUSED (data sovereignty could not be guaranteed, so the run fails closed). In every case the evidence is still sealed.

Can't an AI just fabricate a clean invoice?

Yes — pixels, arithmetic and conformance can all pass on a fabricated document. That's why Aurenta doesn't stop at the image: when an invoice checks out on its face, it's corroborated against out-of-document truth — public registries, your buyer feeds, and your own payment history. A first-time vendor paid into a first-time bank account raises an advisory REVIEW. Advisory, never blocking — releasing money is always a human act.

Does invoice data ever leave the UAE?

No. In sovereign mode, OCR, retrieval and telemetry run only on self-hosted, in-region models. If no in-region model is available, the system stops rather than silently falling back to a foreign cloud API — sovereignty is fail-closed by design.

What are the penalties for non-compliance?

Under Cabinet Decision No. 106 of 2025, failing to issue a compliant e-invoice carries a penalty of AED 100 per invoice, capped at AED 5,000 per calendar month — in addition to existing VAT penalties of AED 2,500–5,000 for each unissued tax invoice, and the operational cost of rejected filings.

Solutions by role

Built for the people who sign.

CFO

Recover what already left. Stop what's about to.

A ranked recovery worklist from your paid history — and a pay/hold screen on the payment run before money moves.

Recovery & the firewall → Head of Tax

The mandate, met before it's mandatory.

PINT-AE 1.0.4 correctness before your ASP transmits — and an input-VAT verdict on every supplier invoice before it enters your return.

The mandate & VAT recoverability → Internal Audit

Evidence you can verify without trusting us.

Every period sealed to a Merkle root you can recompute offline — an inclusion proof per record, no network, no database.

The offline verifier → CIO

Sovereign by construction. Integrated by contract.

Self-hosted in your region behind a fail-closed router — with a batch API whose retries can never double-submit.

Sovereignty & the API →

Get every invoice right —
before the regulator sees it.

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

Book a Demo Run a free 12-month sweep

Now onboarding a founding cohort ahead of the July 2026 pilot.

info@aurenta.ae·Abu Dhabi, United Arab Emirates

"A tax figure must be provable, not probable."— the Aurenta founding team