On 1 July 2030, Council Directive (EU) 2025/516 deletes Articles 265 to 271 of the VAT Directive. That single provision abolishes the recapitulative statement — the periodic summary of intra-Community supplies, filed after the fact, that has been the archetype of reporting later for three decades. In its place: transmission of transaction data at the moment the invoice is issued.
That is the whole shift in one legal fact. Not new reporting — the same reporting, moved from monthly batch to per-transaction, which is only affordable if it’s derived automatically from a structured invoice. The stated reason is fraud. The Commission’s own evidence for that reason is weaker than almost anyone selling this will tell you, and it’s worth understanding why before you build to it.
What “report later” actually was
The old model has a retronym now — periodic transaction controls, PTC — but its defining feature was never the periodicity. It was that the tax authority saw nothing until it asked.
The 2016 edition of the E-Invoicing and Retention in Europe compendium, compiled by Peters, Schönberger & Partner across 22 European countries, is a complete snapshot of that world. The recurring question in every chapter is how a business ensures authenticity of origin and integrity of content — and the recurring answer is business controls creating a reliable audit trail, matching the invoice against purchase orders and other existing documents. The taxpayer builds the evidence. The taxpayer keeps the evidence, for five years in Greece and Poland, eleven in Croatia, up to 22 in Austria for immovable property. The authority arrives later, if at all.
The clearest expression of the old logic is a small Czech rule the compendium records: invoices may be stored outside the Czech Republic only where there is continuous remote access, and after prior notification to the tax authority. Read that carefully. The authority wanted continuous access to the archive — a standing right to reach the data, exercised on demand. Continuous transaction controls invert it: the authority no longer reserves a right to come and look, because the data arrives on its own.
Same objective, opposite mechanism. Which is why “faster reporting” undersells it.
Nobody called it PTC at the time
Worth stating plainly, because it dates the vocabulary: neither “continuous transaction controls” nor “periodic transaction controls” appears anywhere in the 2016 PSP compendium, in the Euro Retail Payments Board’s 2016 working group report on e-invoicing solutions, or in Billentis’s 2017 business case. Several hundred pages, written by specialists at the centre of European e-invoicing, and the terms are simply absent.
PTC is a retronym. It exists to have something to contrast CTC against, the way “acoustic guitar” only became necessary once electric ones existed. In 2016 this wasn’t a model with a name. It was just how VAT worked.
One detail cuts against the neat chronology, though. Greece’s 2016 answer on ensuring authenticity already listed, alongside signatures and EDI, both special safe appliances (electronic tax machines) and clearance of sales transactions through a payment service provider. The country that would go on to build myDATA was already describing clearance mechanisms in a post-audit questionnaire. The shift was visible before it had a label.
What replaces it, and when
The mechanics under ViDA are precise, and the dates are the deliverable:
- Invoice deadline compresses. For intra-Community supplies and reverse-charge transactions, the invoice must be issued within ten days of the chargeable event (Article 222) — down from the fifteenth day of the following month.
- The report leaves at issue. Data is transmitted per individual transaction at the moment the invoice is issued or should have been (Article 263(1)). Self-billed invoices get five days. The customer reports within five days of receiving the invoice, unless the member state waives it (Article 262(4)).
- The payload is fixed. Ten data points for the supplier — Article 226 points 1 to 4, 6, 7, 8, 11, 16 and 17, plus 11a where applicable (Article 264). Identical in every member state, with no possibility of requesting additional data.
- Missing the report has teeth. Article 138(1a) removes the exemption for an intra-Community supply where the supplier hasn’t met the transmission obligation, or where the data transmitted doesn’t contain the correct information — unless the failure can be duly justified to the competent authorities.
- Summary invoices survive, narrowed. Article 223 keeps periodic invoices where VAT on the different supplies becomes chargeable in the same calendar month, issued within ten days of month end — and lets member states exclude them entirely in fraud-sensitive sectors. Note this: the original ViDA proposal abolished summary invoices outright. The adopted text kept them. Commentary written from the draft still says otherwise.
- Domestic systems get five more years. Member states with a domestic real-time transaction-based reporting obligation in place on 1 January 2024 have until 1 January 2035 to align.
Reporting later doesn’t disappear so much as shrink to a residue: the VAT return itself survives, and Article 273 explicitly lets member states keep national tools like SAF-T alongside the real-time obligations. What dies on 1 July 2030 is the periodic transaction listing.
The official case for it — and where the numbers don’t hold
ViDA’s recital 3 makes the argument: the VAT gap was estimated at €93 billion across the Union in 2020, a significant part of it fraud, and in particular intra-Community missing trader fraud, estimated at around €40 to €60 billion. Recital 4 supplies the mechanism: transaction-by-transaction transmission lets administrations cross-check data, increases control capacity, and deters non-compliance.
Then compare that with what the Commission has published since.
The VAT gap in Europe — report 2025, released on 11 December 2025, puts the EU VAT compliance gap at €128 billion for 2023 — 9.5% of the total VAT liability, against total VAT revenue of €1,223 billion. That’s an increase of 1.6 percentage points on 2022, and the Commission’s own Mind the Gap report describes it as reversing the progress observed during the pandemic. Over the longer run the picture is better: 11.1% in 2019 down to 9.5% in 2023. Both statements are true, which is why you’ll see the same report cited as evidence of success and of failure.
The harder problem is the fraud number. A Commission-commissioned study estimating the MTIC gap at EU level using Intrastat mirror-trade statistics put it at between €12.5 billion and €32.8 billion annually across 2010 to 2023 — an average annual loss of 1.2–3.1% of actual VAT revenue. Set that beside the directive’s own €40–60 billion. The upper bound of the Commission’s later estimate is below the lower bound of the figure in the recital.
And the study’s conclusion is more awkward still: the MTIC gap has been broadly stable over time, which the Commission reads as suggesting that factors other than MTIC fraud drive the fluctuations in the VAT compliance gap. If carousel fraud is stable and the gap moves anyway, then the gap is mostly being moved by something CTC doesn’t target — bankruptcies, insolvency, administrative error, real-terms revenue decline. The 2025 report’s own context supports that: between 2021 and 2023 theoretical VAT liability rose 17.3% while actual revenues grew 14.4%, and bankruptcies rose across most of the EU.
Three more figures worth holding:
- The two best-performing member states run no CTC mandate. Austria’s 2023 compliance gap is about 1.0%, Finland’s about 3.0% — the lowest in the EU. Neither has continuous transaction controls. Whatever they’re doing works without it.
- The gap is concentrated. Around 75% of the EU compliance gap comes from six countries: France, Germany, Italy, Poland, Romania and Spain. This is not an EU-wide compliance problem being solved with an EU-wide instrument.
- The policy gap dwarfs the compliance gap. Revenue forgone through reduced rates and exemptions ran to roughly €743 billion in 2023 — around six times the entire compliance gap. The largest hole in EU VAT revenue is a deliberate policy choice, not fraud.
None of that makes CTC pointless. Faster data genuinely does help administrations that are under-resourced rather than under-informed, and the Commission’s own analysis attributes diverging national trends partly to digital reporting reforms. But the honest summary is that the reforms have yet to reverse the recent increase in the EU-wide gap, and the specific fraud they target is a smaller and steadier problem than the directive that targets it asserts. Anyone quoting €40–60 billion in 2026 is quoting a recital, not a measurement.
Why it’s happening anyway
Because the argument for CTC was never really only about fraud — it’s about latency, and latency is what the sources actually show changing.
Look at what the working implementations do. SAP’s August 2024 guide for Greek e-invoicing describes real-time submission through a certified service provider, with myDATA returning a MARK, a UID and an authentication code that must then be printed on the invoice. Sigitek’s SAP solution for India pushes every billing document as JSON to the Invoice Registration Portal via an authorised GSP, which validates the reference number against the GST system’s central registry, signs the data, returns it with a QR code, forwards it to the GST and E-Way Bill systems — and auto-populates the GSTR-1 return on a T+1 basis.
That last clause is the point. The return isn’t abolished; it’s pre-filled. Once the authority holds the transaction data, the periodic filing stops being a declaration the taxpayer composes and becomes a statement the authority proposes. That is a different relationship, and it’s a far more attractive prize for a tax administration than any individual fraud case.
It’s also why e-reporting drives e-invoicing rather than the reverse. The new Article 217 defines an electronic invoice as one in a structured format allowing automated processing — “at least in relation to the data referred to in Articles 262 and 271b”, the reporting articles. Recital 11 is explicit that the invoice should carry all the data to be transmitted, in structured format, so the transmission can be automated from it. The authority’s data needs set the floor for the document your buyer receives.
What to do about it
Three things follow, regardless of what you think of the fraud case.
Model latency, not frequency. The design constraint isn’t “report more often”. It’s that the report is emitted by the act of invoicing, synchronously, with a legal consequence on failure. Any architecture that treats reporting as a nightly job is building the wrong thing.
Assume the return gets pre-filled. India already does it on a T+1 basis. If your reconciliation process assumes you are the authoritative source of your own VAT position, that assumption has a shelf life.
Watch the domestic layer, not the EU one. The intra-EU set is ten fields, fixed everywhere from 2030. Domestic reporting is optional for member states and its content is defined nationally under Article 271b(4) — that’s where the divergence and the cost live, and it runs to 2035.
Frequently asked questions
What are continuous transaction controls?
Any regime where transaction data reaches the tax authority at or near the moment of the transaction, rather than in a periodic filing afterwards. It covers both clearance models, where the authority validates the invoice before it’s valid, and real-time reporting, where a copy or subset travels to the authority on a separate leg. ViDA mandates the second for intra-EU supplies from 1 July 2030.
Is the VAT return being abolished?
No. ViDA abolishes recapitulative statements — the periodic listing of intra-Community transactions — from 1 July 2030 by deleting Articles 265 to 271. The VAT return itself remains, and Article 273 lets member states keep national reporting tools such as SAF-T. What changes is that the return increasingly gets pre-populated from data the authority already holds.
Does CTC actually reduce VAT fraud?
The evidence is more equivocal than the marketing. ViDA’s recital estimates missing trader fraud at €40–60 billion a year; a Commission study using mirror-trade statistics puts the MTIC gap at €12.5–32.8 billion and finds it broadly stable across 2010–2023. The EU compliance gap rose to €128 billion in 2023 while digital reporting was spreading. Digital reporting is one of several factors the Commission credits for diverging national trends — but the causal claim is not settled, and the two lowest-gap member states have no CTC at all.
When does my country switch?
For intra-EU B2B, 1 July 2030 everywhere. Domestically it varies: member states have been free to mandate e-invoicing without a derogation since 14 April 2025, which is why national mandates are arriving first, and those with a real-time domestic system already in place on 1 January 2024 have until 1 January 2035 to converge.
Do summary invoices still work?
Yes, with limits. Article 223 as amended allows periodic invoices covering supplies whose VAT becomes chargeable within the same calendar month, issued within ten days of month end, and lets member states exclude them in fraud-sensitive sectors. The ViDA proposal would have removed them entirely; the adopted directive did not.