What is CTC?
Continuous Transaction Controls (CTC) is the umbrella term for tax-compliance regimes in which businesses transmit transaction-level data to the tax authority at or close to the moment a transaction takes place, rather than aggregating it into a periodic VAT return weeks or months later. CTC turns VAT compliance from a retrospective filing exercise into a continuous data exchange between taxpayers and the administration, with the explicit goals of closing the VAT gap, increasing transparency and curbing fraud.
CTC is the conceptual opposite of the traditional post-audit model, where invoices are exchanged privately and the authority only inspects them if an audit is triggered.
The CTC sub-models
CTC is not a single mechanism. Most regimes fall into two broad families, with a few hybrids:
More broadly, analysts describe five global models: post-audit, decentralised exchange (Peppol), real-time reporting, centralised platform, and clearance. CTC covers everything except pure post-audit.
Why CTC matters for e-invoicing
CTC is the force driving the entire e-invoicing mandate wave. Because the tax authority now needs structured, machine-readable transaction data, governments mandate structured e-invoice formats (EN 16931 in Europe, FatturaPA in Italy, FA_VAT in Poland) instead of PDFs. The format mandate and the reporting mandate are two sides of the same CTC coin.
For an ERP or invoicing platform, adopting CTC means the invoicing pipeline acquires a synchronous dependency on a government endpoint. In a clearance model, an invoice cannot reach the customer until the platform (or its provider) has a successful response. This changes the engineering problem: validation must happen before submission, errors must be caught and explained, retries and idempotency must be handled, and the cleared identifier must be stored as part of the legal record.
How ERP vendors encounter CTC
Vendors meet CTC the moment a customer operates in a country with an active mandate. The recurring pain points are: (1) each country's CTC platform has its own schema, validation rules and error catalogue; (2) clearance latency and downtime become invoicing-blocking incidents; and (3) the same business invoice must be reshaped to satisfy both EN 16931 and a national CTC profile. A compliance safety layer exists precisely to absorb this variance — validating against the right ruleset before the invoice hits an unforgiving government gateway.
Relation to EN 16931 and ViDA
EN 16931 supplies the semantic model that European CTC regimes increasingly build on, and ViDA generalises CTC to the EU level: from 1 July 2030, cross-border intra-Community B2B transactions fall under harmonised Digital Reporting Requirements (DRR) — effectively a Union-wide CTC layer — with EN 16931 as the format. Member states that already run domestic CTC systems must align them with the EU model by 2035. Understanding CTC is therefore the key to understanding why national mandates and ViDA exist at all.