Key Takeaways
- Continuous transaction controls move VAT reporting closer to the moment an invoice is created or exchanged
- CTC rules can affect invoice validity, payment timing, ERP setup, data quality, and audit readiness
- Clearance models usually require tax authority approval before an invoice is legally issued
- Reporting models allow invoices to be exchanged first, but transaction data must be reported quickly
- Businesses operating internationally need a country-by-country CTC exposure map, not a single global e-Invoicing setup
What Continuous Transaction Controls Actually Mean for Businesses
Continuous transaction controls are digital tax controls that give tax authorities access to invoice or transaction data in real time, near real time, or shortly after the transaction takes place. The OECD describes digital continuous transactional reporting regimes as systems that typically require near-real-time reporting of invoice or transactional data for VAT purposes.
In a traditional VAT process, a business issues an invoice to its customer, records the sale or purchase internally, stores the invoice, and reports totals in a periodic VAT return. The tax authority usually sees the transaction only after the fact.
Under CTC, that sequence changes. The invoice may need to be created in a structured digital format, transmitted through a government platform or approved provider, validated against specific data rules, and either cleared or reported before, during, or shortly after issue.
That means VAT compliance starts much earlier. A missing tax ID, incorrect VAT code, unsupported invoice format, or failed platform connection can stop an invoice from being issued correctly. This is why e-Invoicing compliance is no longer just a tax department concern. It involves finance, IT, legal, master data, ERP configuration, accounts payable, accounts receivable, procurement, and customer operations.
The policy reason is clear: governments are trying to reduce the VAT gap, which is the difference between the VAT revenue expected under full compliance and the VAT actually collected. The European Commission defines the VAT compliance gap as the estimated difference between potential VAT revenue under full compliance and actual VAT collected.
For a broader understanding of how VAT operates, see our guide on how VAT works.
The Two CTC Models Every Business Operating Internationally Needs to Know
Most CTC regimes fall into two broad categories: clearance models and reporting models. The exact design varies by country, but the distinction is important because it affects how invoices move through a business.
A clearance model requires invoice data to pass through a tax authority platform, or an approved exchange network, before the invoice is legally issued to the buyer. The authority may validate the invoice, assign a unique identifier, apply a digital stamp, or return an approval message. Italy’s Sistema di Interscambio is a well-known example: since 2019, Italian VAT-registered businesses have had to issue and transmit B2B and B2C electronic invoices through the SdI platform in the FatturaPA XML format.
A reporting model allows the invoice to be exchanged between supplier and buyer, but key invoice data must also be reported to the tax authority within a defined timeframe. Reporting may be real time, near real time, daily, or periodic depending on the mandate.
The practical difference is timing. In a clearance model, the tax authority sits inside the invoice issue process. If clearance fails, the invoice may not be legally valid. In a reporting model, the invoice may still reach the customer, but the business can face penalties, rejected submissions, audit queries, or VAT return mismatches if the reporting obligation is missed.
International businesses often need to support both models at once. One country may require pre-clearance before issue, another may require post-issue reporting, and another may require structured e-Invoicing without immediate tax authority reporting. This is where a single “PDF invoice plus monthly VAT return” process breaks down.
From Invoice to Clearance: What Happens Inside a CTC System
Imagine a supplier creating a domestic B2B invoice in a country with a clearance model.
First, the invoice is generated in the company’s ERP or billing platform. At this stage, the system must capture all mandatory fields: supplier and buyer tax IDs, invoice number, issue date, taxable amount, VAT rate, VAT amount, product or service descriptions, currency, and transaction classification.
Next, the invoice is converted into the required structured format. This may be XML, UBL, CII, Factur-X, Peppol BIS Billing, or a local schema. The key point is that a human-readable PDF is usually not enough. The tax authority needs structured data that can be validated automatically.
The invoice is then transmitted to the relevant government platform, accredited provider, or network. The platform checks the invoice against technical and business rules. It may verify whether mandatory fields are present, whether tax numbers are valid, whether invoice totals reconcile, whether VAT rates are acceptable, and whether the invoice has already been submitted.
If the invoice passes validation, the system returns a clearance response. This may include a unique invoice ID, timestamp, QR code, digital stamp, or approval status. Only then can the invoice be treated as legally issued and sent to the customer.
If the invoice fails validation, the business must correct the error and resubmit. This can delay billing, payment collection, and revenue recognition. It can also create operational friction if teams are not monitoring rejection queues or if ERP data cannot be corrected quickly.
Finally, the cleared invoice and related audit trail must be stored. The business needs evidence of what was submitted, when it was accepted, what response was received, and what version was sent to the customer.
The 2026 CTC Map: Which Markets Are Live, Rolling Out, or Incoming
The global CTC landscape is uneven. Some countries already operate mature clearance or real-time reporting systems. Others are introducing mandatory structured e-Invoicing first, with reporting obligations to follow.
Live or established CTC and e-Invoicing markets include Italy and Malaysia. Italy has operated mandatory B2B and B2C e-Invoicing through SdI since 2019. Malaysia’s phased e-Invoicing regime is also active, with implementation continuing into 2026 through the Inland Revenue Board’s MyInvois framework. Malaysia’s official e-Invoice guideline confirms phased implementation dates, including 1 July 2026 for certain newer businesses with annual turnover or revenue of at least RM1 million.
Markets rolling out or expanding in 2026 include Poland, France, Belgium, and Croatia. Poland’s KSeF system became mandatory for B2B e-Invoicing in early 2026. France is introducing mandatory B2B e-Invoicing and e-reporting from September 2026, with phased issuing obligations for large and mid-sized companies in 2026 and smaller businesses in 2027. Belgium requires structured domestic B2B e-Invoicing from 1 January 2026, with near-real-time reporting expected later.
Markets with incoming or phased mandates include Germany, Spain, and the wider EU. Germany introduced the ability to receive compliant e-invoices from 1 January 2025, with issuing obligations phased in for larger businesses from 2027 and all businesses by 2028. Spain’s B2B e-Invoicing framework continues to develop, with the Council of Ministers approving a royal decree for mandatory B2B e-Invoicing in March 2026. The mandate is expected to come into force in October 2027.
For businesses, the key message is that CTC compliance is not one project. It is a rolling programme of country-specific mandates, formats, timelines, platforms, and operating models.
How ViDA Will Reshape CTC Requirements Across the EU
VAT in the Digital Age, usually shortened to ViDA, is the EU’s major VAT modernisation package. It aims to reduce fraud, simplify compliance, and align VAT rules with the digital economy.
The most important CTC-related change is the move toward digital reporting requirements for intra-EU B2B transactions. The European Commission says the new system introduces real-time digital reporting for cross-border trade based on e-Invoicing, helping member states fight VAT fraud, including carousel fraud.
In practice, ViDA will push businesses toward structured e-Invoicing and faster transaction-level reporting across the EU. It will also create pressure for member states to align domestic systems with EU standards over time. Cross-border B2B digital reporting requirements are due from 1 July 2030, while member states with domestic real-time reporting obligations must align with EU standards by 1 January 2035.
For multinational businesses, ViDA matters even before the main 2030 reporting date. It is shaping national policy decisions now. Countries introducing domestic e-Invoicing mandates are designing systems with EU interoperability, structured formats, and future digital reporting in mind.
This means finance teams should not treat ViDA as a distant regulatory event. The practical preparation starts with today’s invoice data: customer VAT numbers, product taxability, exemption codes, credit note logic, invoice sequencing, archiving, and ERP integration.
For a broader VAT foundation, see our guide on how digital VAT processing improves reclaim success rates.
The Key System Gaps That Lead to CTC Non-Compliance
The most common CTC failures are not caused by a lack of awareness. They happen because business systems were built for periodic VAT reporting, not real-time validation.
The first gap is poor master data. If customer names, VAT IDs, addresses, entity registrations, product codes, or tax classifications are incomplete, invoices can fail validation before they are issued.
The second gap is format readiness. Many legacy invoicing workflows still rely on PDFs, spreadsheets, manual uploads, or email-based approval. CTC mandates usually require structured invoice data, not just a document image.
The third gap is weak ERP integration. A company may have compliant invoice data, but if its ERP cannot connect to a government platform, Peppol access point, accredited provider, or local API, the invoice flow still breaks.
The fourth gap is unclear exception handling. Rejected invoices need ownership. Someone must monitor failed submissions, correct data, resubmit invoices, communicate with customers, and reconcile status updates with accounting records.
The fifth gap is country-by-country rule fragmentation. A business may assume one e-Invoicing vendor or configuration will work globally, only to discover that each country has different fields, formats, transmission channels, deadlines, archiving rules, and buyer communication requirements.
The sixth gap is VAT reporting reconciliation. CTC data, VAT returns, ledgers, sales reports, and purchase records must align. If real-time submissions show one version of the transaction and the VAT return shows another, the discrepancy can trigger audits or blocked deductions.
For businesses comparing e-Invoicing tools, see our guide to the best e-Invoicing compliance solutions.
Next Steps: Mapping Your CTC Exposure Before the Next Mandate Lands
The first step is to build a CTC exposure map. List every country where your business is VAT registered, has a fixed establishment, issues domestic invoices, receives supplier invoices, sells cross-border, or operates through marketplaces or platforms.
Then classify each market by mandate status: live, rolling out, incoming, or under consultation. For each market, identify the model: clearance, reporting, structured e-Invoicing only, or hybrid.
Next, map your invoice flows. Separate sales invoices, purchase invoices, credit notes, self-billing, intercompany charges, exports, intra-EU supplies, domestic B2B, B2C, and services. CTC rules often apply differently depending on transaction type.
After that, test system readiness. Can your ERP create the right data fields? Can it generate the required format? Can it connect to the required platform? Can it receive status messages? Can it store the cleared invoice and audit trail?
Finally, assign ownership. CTC compliance cannot sit only with tax. It needs a shared operating model across finance, IT, tax, legal, procurement, and customer-facing teams.
Prepare Your VAT Operations for Real-Time Reporting
CTC mandates are arriving market by market, but the direction is clear: VAT compliance is becoming digital, transactional, and real time.
VAT IT helps businesses understand their VAT exposure, strengthen digital compliance processes, and prepare for evolving e-Invoicing and reporting obligations across jurisdictions.
Need to assess where your business is exposed to CTC requirements? Speak to our team about mapping your VAT compliance risks before the next mandate goes live.
Frequently Asked Questions
1. Are services treated the same as goods under CTC mandates?
Not always. Some CTC mandates apply broadly to goods and services, while others treat services differently depending on whether the transaction is domestic, cross-border, B2B, B2C, or exempt. Services can also trigger different VAT place-of-supply rules, invoice fields, and reporting obligations. Businesses should assess services separately instead of assuming goods rules apply automatically.
2. What data format do CTC submissions typically require?
Most CTC systems require structured electronic data rather than a PDF. Common formats include XML, UBL, CII, Peppol BIS Billing, or country-specific schemas. The required format depends on the jurisdiction and platform. The important point is that the invoice data must be machine-readable, validated, and capable of being processed by tax authority systems.
3. Can a business use the same invoicing software across all CTC countries?
A business may use one global invoicing or ERP platform, but it usually needs country-specific configurations, integrations, formats, and workflows. CTC rules differ by market, including clearance steps, reporting deadlines, accepted schemas, archiving rules, and buyer delivery methods. The software must support local compliance rather than only generic e-Invoicing functionality.
4. Does a business need to store CTC-submitted invoices separately from its own records?
Usually, businesses must retain both their accounting records and compliant invoice evidence, including the submitted invoice, clearance status, timestamps, unique identifiers, and any authority response. Whether this requires separate storage depends on local law and system design. The key is being able to prove what was issued, submitted, accepted, corrected, and archived.
