5 Compliance Models That Define How the World Does
e-Invoicing

Hong Kong, Canada, and the United Kingdom (until 2029) all operate post-audit models. Many countries in early-stage e-invoicing adoption, where the government encourages electronic invoicing but does not mandate a specific exchange mechanism, fall into this category too.

The mechanics are straightforward: the seller creates an invoice, sends it directly to the buyer, and both parties retain records. The tax authority has no real-time visibility into individual transactions. Compliance is verified retrospectively through audits, SAF-T filings, or VAT return reconciliation.

Of all five models, post-audit carries the lightest integration burden. Businesses choose their own formats and exchange methods. ERP systems do not need to connect to any government platform. The primary compliance requirement is record-keeping and the ability to produce structured data on demand (e.g., SAF-T for audit purposes).

That said, post-audit is declining. Tax authorities worldwide are moving toward models that provide real-time or near-real-time transaction visibility. Countries that currently operate post-audit systems, including the UK and several Nordic markets, are already legislating transitions to more active models.

PEPPOL (Pan-European Public Procurement Online) is the dominant network standard here.^[5] It defines the message format (PEPPOL BIS Billing 3.0, based on UBL 2.1 and UN/CEFACT CII), the transport protocol (AS4), and the service provider accreditation process. Countries can add domestic profiles: Belgium requires EN 16931 compliance, while the UAE uses a PINT AE (PEPPOL International) standard with additional fields.

The model is live in Singapore (InvoiceNow), Australia, New Zealand, Belgium, and the UAE (DCTCE model launching July 2026). The EU ViDA directive endorses it as the preferred model for intra-community B2B e-invoicing by 2030. Buyers and sellers connect through certified access points, and invoices flow from one access point to another over a shared network. The government may operate a registry and accredit service providers, but does not process individual invoices.

Integration requirements are moderate. Businesses must connect to a certified access point (or become one). Format compliance is enforced by the network, not by the tax authority. The key vendor decision is which access point provider to use and whether they cover the specific PEPPOL jurisdictions you need.

Decentralised exchange is the EU's structural bet for cross-border e-invoicing. ViDA requires all 27 member states to support PEPPOL-compatible exchange for intra-community transactions by July 2030. The UK has confirmed a decentralised 4-corner model for its 2029 mandate, with PEPPOL as the expected standard.^[4] In Asia-Pacific, Singapore and Australia are expanding PEPPOL beyond government procurement into B2B.

Real-time reporting is one of the fastest-growing compliance models globally,^[1] and the logic is simple: it gives tax authorities the revenue visibility they want without the operational friction of pre-clearance. When a seller issues an invoice, a copy (or structured data extract) is simultaneously transmitted to the tax authority's platform. The invoice reaches the buyer as normal, with no blocking or delay, but the government sees the transaction in real time. Some jurisdictions allow a short delay (e.g., 24 hours), sometimes called "near-real-time reporting."

India (e-Invoice with IRN through the Invoice Registration Portal), Malaysia (MyInvois platform), and South Korea all use this approach. Saudi Arabia combines it with clearance: B2B invoices require pre-clearance, while B2C invoices are reported within 24 hours with QR codes.

The integration effort is significant. ERP systems must generate and transmit structured data to the government platform in real time, which typically requires API integration, retry logic for failed transmissions, and the ability to handle platform downtime gracefully. Format requirements are strict: the tax authority defines the schema, not the business. Countries with large informal economies or VAT gaps are adopting CTC because it closes the information asymmetry between what businesses report on VAT returns and what they actually invoice.

Italy's SDI (Sistema di Interscambio) is the proof case: it has processed all Italian B2B invoices since the January 2019 mandate,^[2] building on the B2G requirement active since 2014 and handling billions of transactions through a single government-run exchange. Poland (KSeF), China (Golden Tax / Fapiao platform), and Taiwan follow the same approach. Elements of the proposed German ViDA implementation also lean this way.

The seller submits the invoice to the government platform. The platform validates it against business rules and format requirements, stores a copy, and makes it available to (or delivers it to) the buyer. There is no direct seller-to-buyer transmission. The government platform is the single point of exchange.

All invoice traffic must flow through that platform, which becomes a single point of failure. ERP systems need certified connections, and businesses must handle platform-specific validation errors, downtime procedures, and archiving requirements. The platform dictates format, timing, and delivery. Poland's KSeF, launching in February 2026, is the next major test, covering all VAT-registered businesses by April 2026.

In Brazil, goods cannot ship without a SEFAZ-cleared NF-e. That single fact captures the clearance model's defining feature: the tax authority must approve every invoice before it is legally valid. The seller submits invoice data to the clearance platform, which validates it, applies a unique authorisation code (fiscal stamp, UUID, QR code), and returns the cleared invoice. Only then can the seller issue it to the buyer.

Chile, Argentina, Turkey (e-Fatura), and Kazakhstan all follow the same approach. Saudi Arabia's ZATCA FATOORA platform^[3] operates a hybrid model: B2B invoices require pre-clearance, while B2C invoices must be reported within 24 hours via near-real-time CTC reporting. Clearance is dominant in Latin America and expanding into the Middle East, and it provides the strongest revenue assurance for tax authorities, since every transaction is pre-validated.

The integration burden is the highest of any model. ERP systems must make synchronous API calls to the clearance platform for every invoice, handle rejection responses, and manage the operational dependency on government platform availability. If the clearance platform is down, the business cannot legally issue invoices. Most clearance countries have defined contingency procedures (offline modes, batch clearance) for platform outages, but the hard dependency remains.

The five compliance models are not abstract categories. They directly determine your vendor requirements, ERP integration architecture, and operational risk profile.

Start by mapping your countries to models. Before evaluating any vendor, classify each country in your compliance footprint by model type. A business operating in France (decentralised/PEPPOL), Brazil (clearance), and India (real-time reporting) needs a vendor (or combination of vendors) with proven capability across three distinct architectural approaches.

Then evaluate vendor strength per model, not just per country. A vendor strong in PEPPOL-based European markets may have deep integration with Belgium, Singapore, and the coming EU ViDA framework, but no capability for Brazil's SEFAZ clearance or Saudi Arabia's FATOORA platform. The Vendor Match Wizard scores vendors across your specific country and model requirements.

Consider the operational risk gradient too. Post-audit and decentralised models impose lower dependency on government infrastructure. If the PEPPOL network has issues, invoices can often be sent through alternative channels. Clearance models create hard dependencies: if SEFAZ is down, Brazilian invoices stop. Your business continuity planning must account for the models you operate within.

Finally, watch for model transitions. The UK is moving from post-audit to decentralised (2029). Germany is layering centralised platform requirements onto a PEPPOL-compatible base. Saudi Arabia blends clearance and real-time reporting. These transitions create compliance complexity that static vendor certifications do not capture. You need vendors who track the evolving requirements, not just the current ones.

Use the country comparison tool to evaluate compliance models side by side, and the interactive timeline to track how mandates and model implementations are evolving across your markets.