ViDA, explained: VAT in the Digital Age and the 2030 EU e-invoicing mandate

ViDA — VAT in the Digital Age — is a package of EU reforms adopted by the Council on 11 March 2025 that amends the VAT Directive (2006/112/EC). Its centrepiece for invoicing: from 1 July 2030, structured electronic invoices and near-real-time digital reporting become mandatory for intra-EU cross-border B2B transactions, built on the same EN 16931 European standard the national mandates already use. ViDA is the umbrella; each country’s mandate is a national implementation underneath it.

The three pillars

ViDA moves on three fronts. Only the first changes how an invoice is built:

• Digital Reporting & e-invoicing — mandatory structured e-invoices and near-real-time reporting for intra-EU B2B, replacing the periodic recapitulative statements (EC Sales Lists). This is the pillar that touches your invoice format.
• Platform economy — “deemed supplier” rules that make certain online platforms account for VAT on short-term accommodation and passenger transport.
• Single VAT registration — a wider One-Stop-Shop so a business registers for VAT once instead of in many member states.

The timeline that matters for invoicing

• 2025, on entry into force — member states may impose domestic B2B e-invoicing mandates without first obtaining an EU derogation, and a structured e-invoice no longer needs the buyer’s prior acceptance. This is why national mandates have accelerated.
• 1 July 2030 — structured e-invoicing and Digital Reporting Requirements (DRR) become mandatory for intra-EU cross-border B2B. Invoices must be in a structured format compliant with EN 16931; reporting is near-real-time (broadly, transaction data filed within days, not on a monthly return).
• 1 January 2035 — member states that already ran their own domestic e-invoicing / continuous transaction control systems before ViDA (for example Italy’s SdI) must converge them with the EU standard.

What “structured” means here

ViDA narrows what counts as an e-invoice. A PDF emailed as an attachment is not a structured e-invoice. What qualifies is machine-readable XML in the EN 16931 semantic model — in practice Factur-X / ZUGFeRD (a hybrid PDF carrying CII XML) or standalone UBL / CII XML. If you want the underlying rules, see EN 16931 explained. The cross-border ViDA flow runs over interoperable networks (commonly Peppol-style exchange); domestically, France routes through a registered PDP.

National mandates already live under the umbrella

ViDA sets the 2030 floor for cross-border, but several member states have earlier domestic deadlines. Each follows the same EN 16931 core, so a file that validates against the core is the common starting point:

• France · Germany · Italy · Poland
• Spain · Belgium · Romania · Croatia

Where Slipstack fits — and where it does not

Slipstack is a format generator and validator. It turns the JSON you already use into an EN 16931 e-invoice document — a Factur-X / ZUGFeRD hybrid PDF or standalone CII / UBL XML — and validates the core rules. That is the artifact ViDA and every national mandate require. Slipstack does not transmit invoices over Peppol, file Digital Reporting to any tax authority, or act as a PDP, and it is not registered as one. You choose an access point or PDP for transmission and reporting; Slipstack produces and checks the file that flows through it.

Validate the document before it leaves

Whether Slipstack builds your XML or your own code does, paste or upload the CII (or UBL) into the free EN 16931 / XRechnung core validator — up to 20 checks a day, no signup. Scope, stated plainly: it checks the EN 16931 core schematron (ConnectingEurope release v1.3.16). It does not check the KoSIT XRechnung CIUS, Peppol BIS, or any country- or network-specific rules, which are stricter.