— May 18, 2026 · 10 min read

ViDA 2030 — the real timeline the EU just passed and what it means for B2B

On 11 March 2025, the ECOFIN Council formally adopted the "VAT in the Digital Age" (ViDA) package, the result of nearly three years of negotiations on exemptions, deadlines and scope. Here is the timeline actually enacted, and what it means for B2B architectures.

Context: the three ViDA pillars

ViDA amends three existing directives (2006/112/EC VAT, 904/2010 administrative cooperation, 282/2011 VAT implementation) along three complementary axes: Pillar 1 — Platform Economy (VAT responsibility of platforms for short-term rentals and passenger transport), Pillar 2 — Single VAT Registration (One-Stop-Shop extension, VOEC threshold removal, OSS for intra-EU own movements), Pillar 3 — Digital Reporting Requirements (DRR) which mandates structured e-invoicing and near-real-time transactional reporting for all intra-EU B2B transactions.

The political compromise was reached in May 2024 under the Belgian presidency, with the final unblocking on Pillar 1 thanks to a 5-year opt-out granted to SME platforms. The final text was published in the OJEU in April 2025 under references Directive 2025/516/EU, Regulation 2025/517/EU and Implementing Regulation 2025/518/EU.

Precise timeline adopted

• 1 July 2027 — Pillar 2 takes effect: OSS extension to intra-EU own movements, removal of the small-amount exemption for non-EU B2C, OSS extended to B2C deliveries with installation.
• 1 July 2028 — Pillar 1 takes effect for short-term rental platforms (Airbnb, Booking, Vrbo) and passenger transport platforms (Uber, Bolt, Lyft) above the SME threshold: the platform becomes liable for VAT on behalf of the underlying supplier.
• 1 July 2030 — Pillar 3 DRR takes effect for all intra-EU B2B transactions: structured e-invoicing mandatory (EN 16931 format), transactional reporting within 10 days to tax authorities (vs monthly/quarterly recap declaration today).
• 1 January 2035 — absolute deadline for all existing national e-invoicing mandates (Italy SdI, Spain FACe, France Chorus Pro/PDP, Poland KSeF, Portugal Saft, Romania e-Factura, Hungary NAV Online, Germany XRechnung) to be fully aligned on EN 16931 / DRR.

Three major technical changes

1. EN 16931 becomes mandatory foundation

The European semantic standard EN 16931, published in 2017 and already mandatory for B2G flows since April 2020 (directive 2014/55), becomes the foundation for intra-EU B2B in July 2030. Existing implementations — PEPPOL BIS Billing 3 (UBL), Factur-X (CII hybrid PDF/A-3), German ZUGFeRD, Italian FatturaPA after the January 2024 alignment — remain valid provided they truly conform to EN 16931 semantics (61 mandatory business terms + 24 conditional). Purely national variants will need to align by 2035.

2. Disappearance of ESL recap declarations

EC Sales Lists (intra-EU operation recap declarations), today monthly or quarterly depending on the country, are removed as of 1 July 2030. They are replaced by near-real-time transactional reporting (within 10 working days), pushed by each operator through a standardised national XML/JSON endpoint. This is paperwork reduction for companies, but also unprecedented real-time fiscal visibility for administrations.

3. Intra-EU e-invoicing becomes default-on

As of 1 July 2030, issuing a paper or unstructured PDF invoice for an intra-EU B2B transaction becomes illegal (except SME exemption below a threshold defined by each Member State, capped at EUR 50k annual turnover). This massively expands the PEPPOL market and forces ERPs to expose EN 16931 natively.

Impact on B2B architectures

Four consequences to anticipate from 2026-2027:

• Peak capacity: on 30 June 2030, hundreds of thousands of companies switch simultaneously. PEPPOL operators and in-house hubs must scale for a 5-10x volume peak above the 2029 baseline. See our foundation on B2B capacity planning.
• Reporting latency: the "within 10 working days" SLA looks loose, but tax authorities actually expect sub-24h push. The weekly ERP→fiscal batch disappears.
• Archiving: 10-year retention becomes a uniform pan-EU obligation (Italy was already at 10 years, France at 6, Germany at 10, Hungary at 8… all aligned). Technically, event-sourcing becomes the default architecture — see our pattern Event Sourcing with append-only EDI log.
• Reconciliation mechanism: intra-EU partner must publish its (outgoing) invoice AND its buyer must declare its (incoming) invoice. Both flows should reconcile at the administration. Any gap triggers audit. Architectures must guarantee send/receive consistency, which pushes toward idempotency and saga patterns (see Saga Orchestration).

Precise legal references

• Directive 2025/516/EU — amends directive 2006/112/EC (VAT) to integrate Pillars 1, 2, 3 ViDA. Published in OJEU L-series 22 April 2025.
• Regulation 2025/517/EU — amends 904/2010 on administrative cooperation in VAT and mandates the structured transactional reporting format.
• Implementing Regulation 2025/518/EU — details the technical e-reporting format, EN 16931 alignment, reference XSD schemas.
• EN 16931-1:2017+A1:2019 — European semantic norm, published by CEN. standards.cencenelec.eu
• European Commission — Communication COM(2022) 701 final of 8 December 2022, founding document of the ViDA package. eur-lex.europa.eu

2026-2030 anticipation checklist

• 2026: map all intra-EU B2B flows sent and received, identify those not in EN 16931.
• 2027: launch EN 16931 compliance project, decide whether to operate via PDP/PEPPOL or self-host.
• 2028: dry-run transactional reporting on national fiscal API (pilots planned by each tax authority).
• 2029: capacity and DR (disaster recovery) sizing — see EDI DR foundation.
• 30 June 2030: go-live at midnight, gradual partner switchover plan.

For a global view, also see our previous article "ViDA 2025-2035 impact on EDI architectures" and the foundation "EU e-invoicing roadmap".