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

**How it works:** 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.

**Where it applies:** Hong Kong, Canada, and the United Kingdom (until 2029) 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.

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

**The trend:** Post-audit is declining as a model for new mandates. 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 legislating transitions to more active models.

**How it works:** Buyers and sellers connect through certified access points (service providers). Invoices flow from the seller's access point to the buyer's access point over a shared network. The government may operate a registry, set format standards, and accredit service providers — but does not process individual invoices.

**Where it applies:** Singapore (InvoiceNow), Australia, New Zealand, Belgium, and the UAE (DCTCE model launching July 2026). The EU ViDA directive endorses this as the preferred model for intra-community B2B e-invoicing by 2030.

**PEPPOL's role:** PEPPOL (Pan-European Public Procurement Online) is the dominant network standard for decentralised exchange. 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.

**Technical implications:** Moderate integration. 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.

**The trend:** 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. In Asia-Pacific, Singapore and Australia are expanding PEPPOL beyond government procurement into B2B.

**How it works:** When a seller issues an invoice, a copy (or structured data extract) is simultaneously transmitted to the tax authority's platform. The invoice is not blocked or delayed — it reaches the buyer as normal — but the government has real-time visibility into the transaction. This is sometimes called "near-real-time reporting" when a short delay (e.g., 24 hours) is permitted.

**Where it applies:** India (e-Invoice with IRN through the Invoice Registration Portal), Malaysia (MyInvois platform), South Korea, and elements of Saudi Arabia's CTC framework. Saudi Arabia combines real-time reporting with clearance — B2B invoices require pre-clearance, while B2C invoices are reported within 24 hours with QR codes.

**Technical implications:** Significant. ERP systems must be configured to generate and transmit structured data to the government platform in real time. This 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.

**The trend:** Real-time reporting is the fastest-growing model globally. It gives tax authorities the revenue visibility they want without the operational friction of pre-clearance. 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.

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

**Where it applies:** Poland (KSeF), China (Golden Tax / Fapiao platform), Taiwan, and elements of the proposed German ViDA implementation. Italy's SDI (Sistema di Interscambio) is one of the most mature centralised platforms, having processed all Italian B2B and B2G invoices since 2019.

**Technical implications:** High. All invoice traffic must flow through the government platform, which becomes a single point of failure. ERP systems need certified connections to the platform, and businesses must handle platform-specific validation errors, downtime procedures, and archiving requirements. The platform dictates format, timing, and delivery.

**The trend:** Centralised platforms deliver the highest level of government control and data access, but they also concentrate risk. Italy's SDI has proven the model can work at scale (billions of invoices processed). Poland's KSeF, launching in February 2026, is the next major test — covering all VAT-registered businesses by April 2026.

**How it works:** The seller submits the invoice data to the tax authority's clearance platform. The platform validates the data, applies a unique authorisation code (fiscal stamp, UUID, QR code), and returns the cleared invoice to the seller. Only then can the seller issue the invoice to the buyer. An uncleared invoice has no legal standing.

**Where it applies:** Brazil (NF-e cleared by SEFAZ — goods cannot ship without authorisation), Chile, Argentina, Turkey (e-Fatura), and Kazakhstan. Saudi Arabia's ZATCA FATOORA platform applies clearance to B2B invoices specifically.

**Technical implications:** The highest integration burden. 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.

**The trend:** Clearance is dominant in Latin America and expanding into the Middle East. It provides the strongest revenue assurance for tax authorities — every transaction is pre-validated — but imposes the highest operational cost on businesses. Countries adopting clearance tend to be those with historically high VAT gaps or large informal economies where post-hoc enforcement has proven insufficient.

The five compliance models are not abstract categories — they directly determine your vendor requirements, ERP integration architecture, and operational risk profile. Here is how to use them:

**Map your countries to models first.** 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.

**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 have 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.

**Understand the operational risk gradient.** Post-audit and decentralised models impose lower operational 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.

**Watch for model transitions.** Several countries are actively transitioning between models. 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.