Resources
What to do before the mandate — on the page, not behind a form.
The UAE e-invoicing mandate has fixed dates and a precise technical dialect. This page keeps the useful material readable in plain HTML: a readiness checklist you can act on today, an explainer for PINT-AE 1.0.4, and a bilingual glossary of the vocabulary you will meet in every vendor conversation.
ASP readiness in ten steps — read it here, no download required.
- Map invoice volumes, flows, and legal entities. Count invoices issued and received per month, per entity, per system. The mandate applies per legal entity — a group with five TRNs has five readiness projects, not one.
- Confirm your revenue tier against the first wave. Phase 1 go-live on 1 January 2027 targets businesses at or above the AED 50 million revenue threshold; the next wave follows in July 2027. Establish which wave each entity falls into now, not in Q4.
- Inventory every system that issues or receives invoices. ERP, billing, procurement, point-of-sale, spreadsheets that became systems — each one is a source of structured data the mandate will judge.
- Appoint an accredited ASP before 30 October 2026. The appointment deadline lands before go-live; treat ASP selection as a procurement project with its own timeline, references, and exit terms.
- Validate your output against PINT-AE 1.0.4. Sample real invoices from each system and check them against the UAE data dictionary — required fields, code lists, and arithmetic that reconciles to the fils. See the explainer below.
- Reconcile master data. TRNs, legal names, addresses, and contract rate cards must match across your systems and your counterparties' records — master-data drift is where structurally valid invoices go to fail.
- Decide your correctness layer before transmission. An ASP transmits what you give it; something must make the invoice correct and defensible first. Whether you build that check in-house or buy it, keep it ASP-agnostic so the decision doesn't lock your provider choice.
- Define the exception workflow. Decide today who resolves an invoice that fails validation, how fast, and with what audit trail — exceptions at go-live are a certainty, not a risk.
- Prepare evidence retention. Decide what you keep, where it lives, and how an auditor verifies it years later — retention that can't be independently verified is storage, not evidence.
- Brief finance, tax, and IT owners together. Put the dates, the entity map, and the open decisions in front of all three functions in one session — readiness fails in the gaps between them.
The PDF request goes by email to info@aurenta.ae — there is no form to fill in, and the full checklist is already on this page.
Penalty-exposure calculator
Estimate what non-compliance could cost across your entities — the published framing is up to AED 5,000 per month (Cabinet Decision No. 106 of 2025). The calculator works through that per entity and per month against your own volumes.
Pending counsel verification of Cabinet Decision No. 106 of 2025 figuresPINT-AE 1.0.4, in plain language
PINT-AE is the UAE's profile of the international Peppol PINT invoice format, built on the UBL 2.1 standard and given legal force by Ministerial Decisions No. 243 and No. 244 of 2025. It defines exactly what a compliant UAE e-invoice is: which fields must be present, which code lists they draw from, and how the tax data inside them must be structured. Version 1.0.4 is the current data dictionary your systems will be measured against.
The profile is demanding in two distinct ways. Structurally, every mandatory element — TRNs, tax categories, document references — must be present and drawn from the right code list. Arithmetically, the numbers must be exact: line extensions, VAT category subtotals, and document totals have to reconcile precisely, because the receiving side revalidates the arithmetic rather than trusting yours. An invoice that is structurally valid but a fils off is still a failed invoice.
PINT-AE travels over a five-corner continuous-transaction-controls (CTC) model: the supplier hands the invoice to their accredited service provider, which exchanges it with the buyer's accredited service provider for delivery to the buyer, while the Federal Tax Authority — the fifth corner — receives the tax data of every exchange. Transmission is therefore an accredited-provider function by design, and validation happens in the network, not just at your desk.
Aurenta's place in that picture is deliberate: ASP-agnostic — we make the invoice correct before your accredited ASP transmits it. The correctness layer checks structure against the PINT-AE dictionary and recomputes the arithmetic with exact decimal arithmetic — never binary floating point — then seals what it found as tamper-evident evidence: Ed25519-signed evidence roots · HSM-ready (PKCS#11). You appoint any accredited service provider; the correctness layer travels with you.
The e-invoicing vocabulary, in both working languages.
| Term | المصطلح |
|---|---|
| E-invoiceA structured, machine-readable invoice — not a PDF of a paper one. | الفاتورة الإلكترونية |
| ASPAccredited Service Provider — the party that transmits on your behalf. | مزوّد خدمة معتمد |
| FTAFederal Tax Authority. | الهيئة الاتحادية للضرائب |
| PINT-AEThe UAE profile of the Peppol PINT invoice format. | PINT-AE — الملف الإماراتي لفواتير Peppol |
| CTCContinuous transaction controls — tax data reported as invoices move. | الرقابة المستمرة على المعاملات |
| Input VATVAT paid on purchases, potentially recoverable. | ضريبة المدخلات |
| Reverse chargeThe buyer accounts for the VAT instead of the supplier. | الاحتساب العكسي |
| TRNTax Registration Number. | رقم التسجيل الضريبي |
| Evidence rootA Merkle root committing to a batch of sealed records. | جذر الأدلة (جذر ميركل) |
| VerdictPASS · REVIEW · BLOCKED · REFUSED — the outcome of a check. | الحكم |
| Tamper-evidentAny alteration after sealing is detectable. | مقاوم للعبث |
| Payment runThe batch payment proposal screened before money moves. | مقترح الدفع |
Two of these terms come with sentences we treat as contracts, verbatim, wherever payment screening is discussed: Advisory, never blocking — releasing money is always a human act. and Every signal is deterministic and explainable — no ML black box.
Working through the checklist?
Tell us where you are on it — entity count, systems, wave — and we'll tell you honestly which steps Aurenta accelerates and which ones are simply yours to do.