Leadership
This isn't a software decision. It's an integration path with a fixed deadline.
The 5-corner e-invoicing model means every in-scope enterprise needs a path from its own systems to an Accredited Service Provider. That path is the thing being built here: not a dashboard, not a report, the actual pipe.
The two dates that matter
Oct 30, 2026 is the sharper deadline.
Wave-1 enterprises (revenue at or above AED 50M) must appoint an Accredited Service Provider by Oct 30, 2026. Mandatory use under the 5-corner DCTCE model and PINT-AE follows from Jan 2027. The ASP appointment is the nearer, concrete decision; the integration behind it is what determines whether that appointment actually works on day one.
Wave-1 deadline
Due Oct 30, 2026Enterprises ≥ AED 50M revenue must appoint an Accredited Service Provider by this date. Mandatory use for the wider market follows from Jan 2027.
Why this is an integration problem
An ASP is only one corner of five.
Appointing an ASP satisfies the letter of the requirement. Getting invoices to that ASP correctly formed, validated, and traceable is the part that determines whether Wave-1 is a smooth switch or a scramble.
Corner 2 is the part everyone underestimates
Normalizing arbitrary internal invoice data to the official PINT-AE shape and MoF field set is the work that sits before the ASP handoff, and the work most internally-built timelines don't budget for.
UAE-first, not a checkbox on a global platform
Built for one mandate, aligned to the actual MoF field set and Peppol PINT-AE codelist, not adapted from a platform built for a different market first.
An audit trail exists from day one
An append-only, trigger-enforced audit trail is part of the ledger from the start, not a reporting feature added after the first audit request.
Nothing is silently dropped
Every invoice reaches a terminal ledger state, cleared, or a specific failure state with a webhook, so a stalled invoice is visible immediately, not discovered at reconciliation.
How engagement starts
Design-partner track, before pricing is fixed.
Every engagement currently starts on the early-access design-partner track: direct engineering access, input on the field-mapping roadmap, and priority on our ASP adapter roadmap, where the first adapter in the routing layer is furthest along and five more are scaffolded behind it.
Going live on the transmission pipeline requires a one-time business verification (Trade License and FTA TRN Certificate, manually approved); the sandbox is open immediately so integration work can start before that clears.
The view once you’re live
One screen for what’s invoiced, what’s stuck, and what needs attention.
Once the integration is live, this is what is waiting on the other side: an Executive Snapshot built so one person can check the state of e-invoicing without pulling anyone into a meeting.
It is built from invoices issued, not invoices paid. There is no cash flow, collections, or accounts-payable visibility here, because that data doesn’t exist in the product yet.
Invoiced amount and VAT exposure by period
The gross AED invoiced this period, and the VAT sitting on top of it, tracked by period instead of waiting for a spreadsheet at close.
Rejection rate and stuck invoices
What share of submissions were rejected or failed to transmit, and how many invoices have gone quiet, so a stall is visible before someone has to ask.
Penalty exposure, labeled as what it is
A running estimate of potential FTA penalty exposure, shown as an estimate every time, never presented as a number the FTA has actually assessed.
Alerts the moment something needs attention
The same snapshot surfaces an alert as soon as something crosses a threshold, so leadership hears it from the dashboard first, not from a downstream problem.