A Companion, Not Another Overview

This is the implementation follow-up to our pillar guide — see E-Invoicing, ViDA & Peppol. That resource explains the concepts; this one tells tax, finance, and systems owners what to build, in what order, and by when. If you need VAT registration basics first, start with VAT Registration Thresholds; if transfer-pricing documentation competes for the same project budget, see Transfer Pricing.

Why the EU Is Rewriting VAT Reporting

The VAT gap — the difference between expected and collected VAT — has run into the tens of billions annually, driven substantially by missing-trader fraud in cross-border trade that periodic recapitulative statements detect months too late. ViDA replaces after-the-fact summary reporting with transaction-level digital reporting close to real time, so tax administrations can match supplier and buyer declarations while the goods are still moving. The compliance burden shifts from retrospective filings to invoice-issuance discipline: get the structured data right at issuance and reporting largely follows; get it wrong and every transaction becomes an exception.

The ViDA Package in Three Pillars

  1. Digital Reporting Requirements (DRR): near-real-time reporting of intra-EU cross-border B2B transactions, built on structured e-invoice data, replacing recapitulative statements for in-scope supplies.
  2. E-invoicing as the default: structured electronic invoices (EN 16931 standard) become the required format for in-scope cross-border B2B, with member-state options to mandate domestic e-invoicing on their own timetables.
  3. Single VAT registration + platform economy: an expanded single place of registration (OSS/IOSS evolution) so sellers register once instead of in every member state, plus deemed-supplier rules pulling platforms into the VAT chain for short-term accommodation and passenger-transport facilitation.

Implementation Timeline: The Milestones That Matter

flowchart LR
    A["2027:\nOSS/IOSS\nimprovements"] --> B["2028:\nplatform rules +\nsingle registration"]
    B --> C["July 2030:\nmandatory DRR +\ne-invoicing for\ncross-border B2B"]
    C --> D["Post-2030:\ndomestic mandates\nconverge"]

Work backward from July 2030: ERP and invoice-format projects need to complete during 2028–2029 to allow a full parallel-run year. That makes 2027 the design year (map flows, choose standards, budget the build) and 2028 the build year alongside the registration reforms. Businesses that treat ViDA as a 2030 filing change and start in 2029 will discover it is a 2028 systems project.

2027: OSS and IOSS Clarifications

The first wave improves the One-Stop Shop and Import One-Stop Shop mechanics that distance sellers already use: clearer scope boundaries, tightened compliance obligations, and administrative fixes that reduce the registration sprawl the later single-registration pillar completes. Practical action for 2027: rationalize existing OSS/IOSS registrations now — document every member state where you hold a local VAT number solely because OSS did not cover the flow, because those are the registrations the 2028 reforms should let you surrender. Keep the evidence file; de-registration without a flow map creates gaps auditors find later.

2028: Platforms and Single VAT Registration

Two changes land together. First, platforms facilitating short-term accommodation rentals and passenger transport services become deemed suppliers for VAT purposes in defined cases — meaning the platform, not the underlying provider, accounts for VAT on the facilitated supply. If you operate or sell through such platforms, renegotiate contracts now: who prices VAT-inclusive, who issues the invoice, who holds the valid VAT ID, and who remits. Second, the single-registration expansion lets more businesses report multi-state VAT through one member state of identification instead of maintaining parallel local registrations. Model the cash-flow effect: fewer registrations means fewer local refund positions and different payment timing — treasury should see the forecast, not discover it.

Cross-Border B2B Digital Reporting From July 2030

From July 2030, in-scope intra-EU B2B supplies must be reported transactionally within days of issuance (exact windows follow national implementation within the EU framework), with buyer-side matching. Design consequences: invoice data must be complete and valid at issuance — VAT IDs verified (VIES check logged), place-of-supply logic correct, and line-level data structured — because there is no longer a monthly filing cycle in which to quietly fix errors. Build validation before issuance (master-data checks, ID verification, format schema validation) rather than correction workflows after transmission; post-issuance corrections under DRR create amendment chains across two tax administrations.

Structured E-Invoicing: What “Compliant” Means

A PDF attached to an email is not a structured e-invoice. Compliance means EN 16931-conformant data (UBL or CII syntax in practice) carrying the mandated fields, transmittable through the agreed channel and archivable with integrity guarantees for the full retention period. Confirm with your provider: can you both issue and receive structured invoices, validate against the schema pre-send, handle buyer-mandated routing (including Peppol where counterparties require it — see the pillar guide), and store the structured original (not a rendered PDF) with an audit trail? Run a parallel test with your five highest-volume cross-border counterparties before committing the whole flow.

Non-EU Businesses Selling Into Europe

ViDA does not stop at the border. Non-EU sellers using IOSS for distance sales of imported goods face the reformed scope and intermediary mechanics; B2B sellers face buyer-side pressure to deliver compliant structured invoices regardless of their own domestic rules; and any business holding EU VAT registrations must track which ones the single-registration expansion absorbs versus which local obligations (domestic supplies, certain simplifications) keep a local number alive. Decision for 2027: map every EU revenue flow to its registration and reporting path under both the current and 2028+ rules, then calendar the de-registrations and system changes as a program — not as ad-hoc reactions to auditor or counterparty demands.

ERP and Systems Preparation

Sequence the build in dependency order:

  1. Flow inventory: every cross-border B2B scenario with volumes, counterparties, current invoice format, and VAT treatment. No inventory, no credible project scope.
  2. Gap analysis: which flows already produce structured data, which need new mapping, where VAT-ID validation and place-of-supply logic live today (spreadsheet vs. system).
  3. Format and channel decisions: EN 16931 syntax choice, transmission channels per counterparty group, archiving solution with retention and retrieval tested.
  4. Validation layer: pre-issuance checks (IDs, mandatory fields, schema, duplicates) embedded in the issue workflow — this is the control auditors will walk through.
  5. Parallel run: dual issue (current + structured) with reconciliation of every field for at least one full VAT period per flow before cutover.

Budget jointly with e-invoicing mandates in non-EU markets where you operate; the same structured-invoice capability serves multiple regimes, and building it twice is the most expensive option. Staff the program accordingly: tax owns rule interpretation and ongoing monitoring of national implementations, finance owns issuance discipline and master-data quality, and IT owns formats, transmission, and archiving — with a single program owner empowered to resolve the cross-functional disputes that otherwise stall at each handoff. Train customer-facing teams too, because the first ViDA failures most businesses experience are commercial, not technical: a buyer rejecting a non-compliant invoice and holding payment while the correction chain runs.

Business Readiness Checklist

  • Flow map complete: every intra-EU B2B and distance-sales flow documented with volumes and current registration path.
  • 2027 actions owned: OSS/IOSS rationalization file, de-registration candidates identified with evidence.
  • 2028 contracts updated: platform deemed-supplier clauses, VAT-inclusive pricing, invoice-issuance responsibilities, and VAT-ID warranties.
  • E-invoicing capability confirmed in writing from the ERP/provider: issue, receive, validate, route, and archive structured invoices.
  • Pre-issuance validation designed: VIES checks, mandatory-field completeness, schema validation, duplicate prevention.
  • Parallel-run window booked in 2029 with counterparty cooperation agreements for the top-volume flows.
  • Retention and retrieval tested: structured originals recoverable with integrity evidence for the full statutory period.
  • Roles assigned: tax owns rules and monitoring, finance owns issuance discipline, IT owns formats and transmission — with one program owner across all three.

FAQ

Can member states require e-invoicing before 2030?

Yes — several already have or are introducing domestic mandates on their own timetables under the framework’s authorization. Track each member state where you issue domestic invoices separately from the cross-border July 2030 date; the earlier of the two governs each flow.

What happens to recapitulative statements (EC Sales Lists)?

For in-scope transactions they are superseded by digital reporting; out-of-scope flows may retain existing obligations during transition. Do not decommission EC-list processes until the national implementation confirms the replacement per flow.

How should we budget a ViDA program?

Scope by flow count and ERP readiness, not by revenue: a mid-size business with three cross-border flows on a modern cloud ERP may need configuration plus validation; the same business on a heavily customized legacy stack with EDI billing may need a format-conversion layer. Get the flow inventory done before accepting any vendor estimate.

Next Steps

  1. Read this guide’s pillar companion for the concept layer, then complete the flow inventory above — it is the input every downstream decision needs.
  2. Assign the program owner and book the 2028 registration review now; the 2030 reporting deadline is fixed, but the 2028 contract and registration work determines whether you meet it calmly.
  3. Start provider validation this quarter: a written confirmation of structured issue/receive/validate/archive capability, with a test invoice against the schema — not a roadmap slide.