The three models of e-invoicing: post-audit, clearance (CTC) and Peppol
Why does every country’s e-invoicing mandate look different? The three underlying models — post-audit, clearance / CTC (Italy’s SdI, Poland’s KSeF) and the Peppol interoperability network — explained, and what each means for your business.
If you have looked at more than one country’s e-invoicing rules, you have probably noticed they barely resemble each other. Italy routes every invoice through a government platform. Belgium just says “use Peppol”. France invented its own mix. It looks like chaos — but underneath there are only three models. Once you know which one applies to you, every mandate suddenly makes sense.
Why the rules look so different
Countries are chasing the same goal — closing the VAT gap by making invoices machine-readable and visible to the tax authority — but they picked different ways to get there. The things you actually fight with (formats, portals, deadlines) all flow from which model a country chose. There are three.
Model 1 — Post-audit (the old world)
For decades this was the default. You send an invoice straight to your customer — PDF, email, paper or EDI — and the tax authority only looks at it later, if it audits you. Nothing is checked in real time. It is simple, and it is still what most B2B invoicing outside a mandate looks like today. The catch: tax authorities get no live visibility, so this model is being phased out mandate by mandate.
Model 2 — Clearance / CTC (the invoice goes through the government first)
In a clearance model — the technical name is Continuous Transaction Controls (CTC) — your invoice must pass through, or be reported to, a government platform before or at the moment it reaches your customer. The platform validates and registers it, gives it an ID and timestamp, and often forwards it. Only a “cleared” invoice is legally valid.
This is Italy’s SdI (Sistema di Interscambio) with the FatturaPA format, and Poland’s KSeF with the FA(3) schema. In these countries you must produce the exact national format and route it through the platform — usually via an accredited provider — not just hand a file to your customer.
- Italy — every invoice clears through SdI in the FatturaPA format.
- Poland — B2B invoices clear through KSeF in the FA(3) structured format (mandatory in 2026).
- The UAE — a “5-corner” variant (DCTCE) that bolts the tax authority onto the Peppol network as a fifth corner.
What it means for you: the format is national and non-negotiable, and there is a mandatory route. Get either wrong and, legally, the invoice does not exist.
Model 3 — Interoperability (the Peppol network, four-corner)
Here there is no single government inbox. Instead, a network of certified Access Points exchanges standardised documents: your Access Point sends to your customer’s Access Point — the classic four-corner model. You produce a Peppol BIS 3.0 document (built on EN 16931) and hand it to an Access Point; the network does the rest.
Belgium’s 2026 B2B mandate works this way, as does most EU public-sector (B2G) invoicing and Norway’s EHF. Reporting to a tax authority can be layered on top, but the exchange itself is peer-to-peer over Peppol.
What it means for you: produce one valid Peppol BIS 3.0 invoice and connect to one Access Point — and you can reach every other participant on the network, in any country, without a separate integration per partner.
The hybrids — where France (and the future) sits
Real mandates are not always pure. France combines mandatory e-invoicing through certified platforms (PA, ex-PDP) with separate e-reporting of transaction and payment data to the tax authority — a decentralised model that borrows from both clearance and interoperability. The UAE’s 5-corner model is clearance built on top of the Peppol network. Expect more of this: the models are converging, not staying in neat boxes.
Which model applies to you? A 10-second test
- Does your country name a government platform — SdI, KSeF, Chorus Pro / PPF? → Clearance (CTC).
- Does it just tell you to “use Peppol” (BIS 3.0)? → Interoperability.
- Does it still allow a PDF by email for B2B? → Post-audit — for now.
Most businesses end up dealing with more than one, because you invoice customers in more than one country. That is the real reason “we support e-invoicing” is never a single job.
What every model has in common
Here is the good news hiding under the fragmentation: they are all moving to the same place — a structured, machine-readable invoice instead of a PDF. And most of them share a common semantic core, EN 16931, the European standard. Peppol BIS, XRechnung and Factur-X are all built on it; a few clearance formats (Italy’s FatturaPA, Poland’s FA(3)) use their own national schema, but map cleanly from the same underlying invoice data.
So the hard part is not really the transport model — it is turning your invoice data into the correct structured document. Get that right once, in a canonical model, and switching country or model becomes a change of output, not a new project.
Where MyInvoice fits
MyInvoice handles that last mile for every model. It turns the data you already export — CSV, Excel, UBL, CII, EDIFACT — into the exact validated document each model needs: FatturaPA or KSeF FA(3) for clearance countries, Peppol BIS 3.0 for the interoperability network, XRechnung for German B2G, Factur-X for France — all checked against XSD and the EN 16931 rules before they leave. Transmission — submitting to SdI/KSeF or handing off to a Peppol Access Point — is the thin layer on top.
Convert one of your invoices in the browserRead the API docs