Continuous Transaction Controls (CTC) vs Periodic E-Reporting: How the Models Differ in 2026

Tax authorities across Europe and the Middle East no longer wait for the quarterly VAT return to see what businesses are invoicing. Under continuous transaction controls (CTC), invoice data reaches the tax administration as the transaction happens, and in some countries the invoice is not legally valid until the authority has approved it.

This guide explains how CTC differs from periodic e-reporting and from the traditional post-audit model. It shows which model each major EU and MEA country uses in 2026, and what that means for your ERP, your service provider and your compliance team. ViDA will bring digital reporting to every EU Member State from July 2030, so the choice between models is becoming an architecture decision, not just a legal footnote.

What are continuous transaction controls?

Continuous transaction controls are a group of VAT enforcement models in which structured invoice data is sent to the tax authority electronically, in real time or close to it, rather than summarised weeks or months later in a return. The term covers two main designs:

• Clearance. The supplier submits the invoice to a government platform (or through an accredited provider), the platform validates it, and only then is the invoice legally issued and delivered to the buyer. Italy's SdI, Poland's KSeF and Saudi Arabia's Fatoora (for standard B2B invoices) work this way.
• Real-time or near real-time reporting. The invoice is exchanged between the trading partners as usual, but its data must be reported to the authority within a short window, from minutes to a few days. Hungary's RTIR and Spain's SII are well-known examples.

What both designs share is that the tax authority sees transaction-level data almost as soon as the transaction occurs. That allows automated cross-checks between suppliers and buyers, pre-filled VAT returns and faster detection of fraud such as missing-trader schemes.

What is periodic e-reporting?

Periodic e-reporting means submitting structured tax data electronically on a fixed schedule (monthly, quarterly or annually) instead of transaction by transaction. Examples include SAF-T files, VAT invoice listings, EC Sales Lists and annual customer listings. The data is digital, but it arrives after the fact and usually in aggregated or batch form.

Periodic reporting is often combined with the post-audit model. Under post-audit, invoices are exchanged freely between trading partners and the authority only looks at them when it requests records or opens an audit. Germany's B2B e-invoicing mandate and Belgium's 2026 Peppol mandate are both post-audit. Businesses must issue structured e-invoices, but no government platform sits in the invoice flow.

CTC vs periodic e-reporting vs post-audit: side-by-side comparison

How the clearance model works in practice

In a centralised clearance model, the government platform is the "post office" for every in-scope invoice. A typical flow looks like this:

1. The supplier's ERP produces a structured invoice in the national format (for example, FatturaPA XML in Italy or FA(3) XML in Poland).
2. The invoice is submitted to the platform directly or through a service provider.
3. The platform validates the schema, mandatory fields and tax logic, then either rejects the invoice or assigns it an identifier.
4. The buyer receives the cleared invoice from the platform or through the supplier's channel.
5. The identifier and status are written back to the supplier's ERP for reconciliation and archiving.

Poland's KSeF is the most recent large-scale example in the EU. It became mandatory on 1 February 2026 for taxpayers with 2024 sales above PLN 200 million and on 1 April 2026 for other VAT taxpayers. Micro-businesses with low monthly off-system sales can wait until 1 January 2027, which is also when penalties start to apply. The legally valid invoice is the FA(3) document stored in KSeF, identified by its KSeF number. The official KSeF portal publishes the current schema and technical documentation.

Saudi Arabia runs a hybrid. Under ZATCA's Fatoora Phase 2, standard (B2B) tax invoices must be cleared before they are shared with the buyer, while simplified (B2C) invoices are reported within 24 hours of issue. Integration has been rolled out in waves. Wave 24, with a revenue threshold of SAR 375,000, had to integrate by 30 June 2026. See ZATCA's e-invoicing page for the official wave announcements.

Operational implications of clearance

• The platform sits on your critical path. If submission fails, the invoice does not exist, so you need retry logic, offline or emergency procedures (KSeF provides dedicated offline modes) and monitoring.
• Validation errors become billing errors. Master data issues such as wrong VAT IDs or invalid codes cause rejections that delay cash collection.
• EDI flows change role. In clearance countries, an EDI invoice sent directly to a buyer is no longer the legal invoice. It can still drive the buyer's matching, but it must reference the cleared document. Our article on EDI invoicing vs e-invoicing covers this in detail.

How real-time and near real-time reporting work

In a reporting model, the commercial invoice flow stays between the trading partners and a copy of the invoice data goes to the authority. Timing is what separates a CTC reporting model from periodic reporting:

• Hungary has required real-time invoice reporting to the NAV Online Invoice system (RTIR) since 2018. The scope was extended to all domestic invoices in 2020 and to B2C transactions in 2021.
• Spain's SII (Immediate Supply of Information) requires larger taxpayers to submit invoice records within four days. Separately, the Verifactu regime for invoicing software has been postponed: corporate taxpayers must comply from 1 January 2027 and other obliged taxpayers from 1 July 2027.
• France's e-reporting, which started on 1 September 2026 for large and mid-sized companies, covers transactions that are not domestic B2B e-invoices: B2C sales, international B2B supplies and payment data for services. Small and micro-enterprises follow on 1 September 2027.

Reporting models are less disruptive than clearance because invoicing does not stop if the reporting channel is unavailable. The trade-off is that data quality problems may only surface later, when the authority's cross-checks flag a mismatch between your report and your trading partner's.

The decentralised CTC model: France, the UAE and Belgium's next step

A newer group of countries is building CTC on top of decentralised networks instead of a single government hub. Certified private providers exchange the invoice and pass the tax data to the authority.

• France. Since 1 September 2026, domestic B2B invoices must travel through a plateforme agréée (approved platform). All businesses must now be able to receive e-invoices, and large and mid-sized companies must issue them. The platforms send invoice data to the tax administration, and the public portal's role is now limited to the central directory and data concentration.
• United Arab Emirates. The UAE's Decentralised Continuous Transaction Control and Exchange (DCTCE) uses a Peppol-based 5-corner model. The Accredited Service Provider reports invoice data to the Federal Tax Authority. Businesses with revenue of AED 50 million or more must appoint an ASP by 30 October 2026 and issue e-invoices from 1 January 2027. Other businesses follow from 1 July 2027.
• Belgium. Belgium's B2B mandate, live since 1 January 2026, is post-audit over a four-corner Peppol network. The government plans near real-time e-reporting from 1 January 2028 through a five-corner model, with the exact dataset still to be confirmed by Royal Decree. Belgium shows how a country can move from post-audit to CTC without changing the exchange network.

For businesses, the decentralised model means that your choice of provider largely decides your compliance. The provider's accreditation, Peppol connectivity and status handling become part of your VAT control framework.

Country overview: which model applies where (October 2026)

Mandates change often. Our Compliance Tracker follows updates country by country.

Where ViDA fits: digital reporting requirements from 2030

The EU's VAT in the Digital Age (ViDA) package, formally adopted on 11 March 2025, moves the whole EU towards a CTC-style framework:

• Member States no longer need an EU derogation to impose domestic B2B e-invoicing, which is why so many national mandates have been announced since 2025.
• From 1 July 2030, e-invoicing based on the European standard EN 16931 becomes the default. Intra-EU B2B supplies will be subject to transaction-based digital reporting requirements (DRR), with invoices issued within 10 days of the chargeable event. This replaces recapitulative statements such as the EC Sales List.
• Member States that already run domestic reporting systems must align them with the EU model by 2035.

The practical consequence is that periodic listings are on their way out for intra-EU trade, and transaction-level reporting is becoming the EU norm. The European Commission's ViDA page sets out the official milestones. For the data model underneath DRR, see our EN 16931 explainer.

What CTC means for your systems and processes

Whether a country uses clearance, real-time reporting or decentralised CTC, compliance teams and IT managers face the same core requirements:

1. Structured data at source. CTC regimes validate every field. Your ERP needs clean master data (VAT IDs, addresses, tax codes, units of measure) and an EN 16931-compatible output.
2. Status-aware integration. Clearance IDs, KSeF numbers, rejection messages and reporting acknowledgements must flow back into the ERP so finance can see which invoices are legally valid.
3. Exception handling. Define who fixes rejected invoices and how quickly, and how you will invoice during platform outages under the local fallback rules.
4. One architecture for many models. A multinational may need clearance in Poland and Saudi Arabia, approved platforms in France, an ASP in the UAE and Peppol in Belgium and Germany. Building one connector per country quickly becomes unmanageable. A single hub that translates one ERP output into each local model reduces cost and change risk.
5. Archiving. Keep the structured original, plus clearance or reporting evidence, for the local retention period.

For a framework covering all of these steps across countries, read The Complete Guide to Global E-Invoicing Compliance.

FAQ: continuous transaction controls

What is the difference between CTC and e-reporting?

E-reporting is the transmission of transaction data to the tax authority. It becomes a form of CTC when it happens in real time or near real time at invoice level. Periodic e-reporting, such as monthly SAF-T files, is not CTC because the data arrives after the fact and often in aggregated form.

Is Peppol a CTC model?

Peppol on its own is an exchange network, not a tax control model. It becomes part of a CTC system when the tax authority is added as a "fifth corner" that receives invoice data, as in the UAE and in Belgium's planned 2028 e-reporting.

Which countries use the clearance model?

In the EU and MEA, examples include Italy (SdI), Poland (KSeF) and Saudi Arabia for standard B2B invoices. Egypt also clears invoices through its Tax Authority's e-invoicing system. France and the UAE use decentralised models in which accredited providers handle the exchange and pass data to the authority.

Will ViDA require clearance in every EU country?

No. ViDA requires transaction-based digital reporting for intra-EU B2B supplies from 1 July 2030, but it does not impose a single clearance model. Member States keep flexibility for domestic transactions, subject to alignment with the EU framework by 2035.

Conclusion: plan for CTC, whatever your current model

The direction is consistent across Europe and the Middle East. Post-audit and periodic reporting are giving way to transaction-level controls, whether through a central clearance platform, real-time reporting or a decentralised network of accredited providers. Companies that design their e-invoicing architecture around CTC now, with structured data, status handling and one hub for many countries, will absorb the next mandate as a configuration change rather than a new project.

Infinite IT Solutions connects your ERP to clearance platforms, Peppol and accredited networks across the EU and MEA, including KSeF and UAE ASP services. Contact our team to map which CTC models apply to your entities and get a compliance roadmap for each country you trade in.