The VAT baseline: OSS and IOSS
Before ViDA, the ground most mid-market finance teams are standing on is the current EU VAT framework, and it is worth being precise about it because the reforms build on top of it rather than replacing it.
The One Stop Shop lets a business selling goods or services to consumers across multiple EU member states account for the VAT due in all of them through a single registration and return, rather than registering separately in each country where it has customers. For a company shipping to consumers in eight member states, OSS is the difference between one VAT return and eight. The Import One Stop Shop extends a comparable simplification to distance sales of imported goods below the low-value consignment threshold, letting the seller collect and remit import VAT through a single return rather than having it charged at the border.
These schemes are simplifications, but they are not automatic. They depend on correctly determining the place of supply for each transaction, applying the right member state's VAT rate, and reporting each country's VAT accurately within the OSS return. A finance system that cannot reliably identify where a supply takes place and which rate applies turns OSS from a simplification into a source of error.
Getting this baseline right matters more as ViDA approaches, because the digital reporting the reforms introduce will draw on exactly this transaction-level accuracy. A business whose place-of-supply and rate logic is already sound is well positioned. One relying on manual determination is exposed on both the current returns and the coming ones.
What ViDA changes, and when
VAT in the Digital Age is the EU's package of VAT reforms, and the responsible way to describe its timeline is measured, because the dates have moved during negotiation and are phased over several years rather than landing at once.
Three pillars sit inside ViDA. The first is digital reporting requirements based on e-invoicing for intra-EU B2B transactions: structured electronic invoices and near-real-time digital reporting of cross-border trade, intended to replace the existing recapitulative statements. The second is updated rules for the platform economy, shifting certain VAT collection responsibilities onto platforms in sectors such as short-term accommodation and passenger transport. The third is a move toward single VAT registration, extending the OSS logic so businesses need fewer separate registrations across member states.
On timing, the widely cited direction is that mandatory digital reporting and e-invoicing for intra-EU transactions is expected to apply from 2028 onward, with the platform economy and single-registration measures phased across the surrounding years. Treat these as expected and subject to confirmation rather than fixed, and note that individual member states are moving on their own domestic timelines underneath the EU framework. Several countries have introduced or announced national B2B e-invoicing mandates ahead of the EU-wide requirement, so the date that binds your business may be a national one that arrives before the EU-level phase.
The practical reading for a mid-market finance team is that this is a plan-for horizon, not a scramble. You have runway. What you should not do is architect around the assumption that PDF invoices and periodic summary reporting will remain acceptable for cross-border trade indefinitely, because the direction is settled even where the exact dates are not.
Peppol and the mechanics of structured invoicing
Structured e-invoicing is not a prettier PDF. It is machine-readable invoice data in a defined format, exchanged over a network that both parties connect to. Across the EU, the framework that recurs is Peppol.
Peppol is an interoperability network: rather than every business building a direct connection to every trading partner and every tax authority, each party connects once to an access point, and the network routes documents between them using a common format and addressing scheme. It underpins public-sector e-invoicing across much of Europe already, and the emerging model — sometimes described as five-corner — extends it so that tax authorities receive the digital report as invoices flow between businesses.
For a finance team, the mechanics that matter are these. Your system must be able to produce a compliant structured invoice, not just render a human-readable one. It must connect to an access point so those invoices can be sent and received over the network. And it must be able to generate the digital report the authority requires, derived from the same invoice data rather than compiled separately. When these three capabilities come from one platform, the structured invoice, the transmission, and the report are the same event seen from three angles.
The failure mode to avoid is the one that recurs in every compliance regime: a bolt-on that generates the structured format from an export, transmits it separately, and reports independently, held together by mappings a person maintains. That architecture works until a field changes or a mapping drifts, and then it fails quietly in a way you discover at audit. The lesson from clearance models in other regions applies directly here — compliance that is native to the transaction is durable in a way that a connector is not.
Consolidating multi-country operations
The deeper challenge ViDA surfaces for mid-market companies is not any single mandate. It is that a business trading across several EU member states is being asked to be compliant, in near-real time, in multiple regimes at once — and the common failure is running each country on its own island.
When each subsidiary or country operation runs a different local accounting system, cross-border VAT becomes a reconciliation exercise conducted after the fact. Intra-group transactions have to be matched across systems that do not share a data model. Each country's e-invoicing and reporting mandate is met by a separate local solution, and the group has no single view of its VAT position until someone assembles one from exports. As national mandates arrive on different timelines, the group ends up maintaining several compliance mechanisms in parallel, each a project of its own.
A consolidated platform changes the arithmetic. When every entity runs on one system with a shared chart of accounts and a common transaction model, intercompany transactions reconcile because both sides were recorded in the same place. Each country's structured invoicing and digital reporting is a configuration of one compliance engine rather than a separate integration. The group VAT position is visible without a consolidation exercise, and when a new national mandate arrives, it is switched on for that entity rather than built from scratch.
The preparation to do now is not to buy a ViDA product, because the mandates are still phasing in. It is to consolidate onto an architecture that can absorb each phase as it lands — structured invoicing, network connectivity, transaction-level reporting, and multi-entity consolidation in one place. Finance teams that use the runway to consolidate will meet each ViDA phase as a setting to enable. Teams that wait will meet each one as an emergency.