Why middleware?
Your ERP wasn’t built for PINT-AE. It doesn’t have to be.
The case for a compliance layer between your ERP (Corner 1) and your Accredited Service Provider (Corner 2) — instead of wiring the mandate directly into either one.
Two bad options
Every team facing this mandate picks one of two paths.
Direct API integration
A standard enterprise integration into an Accredited Service Provider’s API runs around 10 weeks — and every time the 300+-field PINT-AE spec changes, your engineering team rewrites the ERP code that talks to it.
~10 weeks, repeated on every spec changeDo nothing
Miss the ASP-appointment deadline and the penalty meter starts — AED 5,000 for every month you’re not connected, once your business is in a mandatory phase.
AED 5,000 / month, and countingThe mandate is a network, not a file format
The 5-corner model, explained once.
UAE e-invoicing runs on the Peppol 5-corner Decentralized CTC and Exchange model. Your invoice never goes straight to the tax authority — it moves seller → your Access Point → the network → the buyer’s Access Point → buyer, with the FTA receiving its copy from the network side. Getting a validated, audited path into that network is the actual integration problem. That path is what we built.
We sit in front of your Accredited Service Provider, in every submission — the layer that decides whether an invoice is ready before it ever reaches the network.
Architecture
The 5-Corner DCTCE Network
Decoupled ERP
When the spec changes, your ERP doesn’t.
The Ministry of Finance amends the PINT-AE spec, and a direct-API client has to find and rewrite the ERP code that built the old field set. A Clarix client’s ERP is untouched — we absorb the schema translation in our layer, not yours.
Direct API
Spec changes → ERP code changes
With Clarix
Spec changes → our layer changes
The messy-data reality
Legacy exports in. Canonical fields out.
Most invoicing data doesn’t start out clean — it starts as a CSV or Excel export from a legacy system, with inconsistent column names and no PINT-AE structure at all. Our AI ingestion maps that mess to the canonical 62 fields in hours, not weeks.
Legacy CSV / Excel export
Unstructured62 canonical PINT-AE fields
Hours, not weeksASP-agnostic, by design
We don’t replace your ASP. We feed it clean data.
Bring whichever Accredited Service Provider you’ve already chosen. Clarix’s BYOK bridge connects to it directly — your ASP credentials are encrypted end-to-end and never leave your control. No vendor lock-in, no re-platforming if you switch ASPs later.
Real-time validation vs. periodic reporting
The FTA sees invoices near-real-time. Your error checking should too.
PINT-AE isn’t a return you file at quarter-end — the network reports each invoice as it moves. Catching an error before it’s transmitted is a different problem than catching one after the fact, and it needs a different kind of tool.
Periodic reporting
Errors surface at filing time — long after the invoice already went out.
Clarix’s validation sandbox
Every check runs before the network ever sees the invoice — the same pipeline as submission, with zero persistence.