EU ViDA: Europe's e-invoicing harmonisation from 2030

In a nutshell

ViDA (VAT in the Digital Age) is a European Union legislative package modernising value-added tax. After years of negotiation, political agreement was reached at ECOFIN in March 2025; implementation runs via an amended VAT Directive (2006/112/EC) and its implementing regulations.

The package has three pillars:

1. Digital Reporting Requirements (DRR) — structured real-time reporting of cross-border B2B transactions
2. Platform Economy — new obligations for accommodation and passenger-transport platforms
3. Single VAT Registration (SVR) — one VAT registration covers most cross-border scenarios

For the e-invoicing topic pillar 1 is the central one.

Digital Reporting Requirements from 2030

From 1 July 2030 for cross-border B2B invoices within the EU:

• Issuing a structured e-invoice per EN 16931 is mandatory
• The window between taxable supply and invoice issuance shrinks to 10 days
• A real-time submission of the transaction data to the relevant national tax administration becomes mandatory
• The traditional Recapitulative Statement (EC Sales List) disappears — data flows automatically from the e-invoices

With that, EN 16931 becomes the de-facto foundation of all cross-border invoices inside the EU single market. Nationally, since May 2025: Member States may introduce domestic B2B e-invoicing mandates without prior Commission authorisation — Germany and France have taken exactly that route.

What changes for invoice senders

A company selling into the EU single market today must be ready by 2030 for:

• EN 16931-compliant invoices (XRechnung, ZUGFeRD, Peppol BIS, Factur-X — all acceptable)
• Faster delivery (max. 10 days; today typically 15 days after month-end)
• Real-time reporting to the sending state’s tax administration — technically via Peppol or equivalent channels
• Structured cancellations and corrections — no longer free-text attachments but specific BT fields for credit notes

What changes for recipients

• Receiving structured invoices must be technically possible — either your own Peppol / EN 16931 pipeline or a connected service provider
• Automated reporting to your own tax administration (mirror of pillar 1)
• Recapitulative Statement disappears — replaced by real-time invoice-driven data flow

Format freedom remains, semantics turn strict

ViDA does not prescribe a specific syntax (UBL vs. CII) or container (PDF/A-3 for ZUGFeRD vs. pure XML for XRechnung). Only the EN 16931 semantics are mandatory — the BT fields with their business rules. The existing tool landscape stays valid:

Format	ViDA-ready	Context
XRechnung 3.x	yes	DE B2G + B2B
ZUGFeRD 2.x from profile EN16931	yes	DE B2B
Factur-X 1.0.07+ from profile EN16931	yes	FR and cross-border
Peppol BIS Billing 3.0 (UBL)	yes	cross-border standard
ebInterface 6.x	yes	AT B2G + B2B
EDIFACT/INVOIC without mapping	no	must be mapped to EN 16931

Single VAT Registration — the less-noticed piece

ViDA reduces registration overhead for EU-wide activity dramatically: for most cross-border scenarios, companies only need one VAT registration in their home state. OSS (One Stop Shop) and IOSS are extended to cover B2C supplies and consignment-stock situations.

For the invoice itself this means: fewer divergent national mandatory fields, more coherence in the EN 16931 model, cleaner master data.

Timeline (summary)

Date	What applies
May 2025	Member States may introduce domestic B2B e-invoicing mandates (ViDA option)
01 Jan 2027	Platform-economy rules apply to Airbnb, Uber & co.
01 Jul 2028	Single VAT Registration takes effect
01 Jul 2030	Digital Reporting Requirements become mandatory for cross-border B2B
from 2035	Full harmonisation of national DRR systems

Individual dates may shift slightly during transposition into national law — the core logic “EN 16931 + real-time reporting from the early 2030s” is stable.

What already makes sense today

Even if July 2030 sounds far away: the technical switches are being set in the next 24 months. If you’re planning infrastructure now, you should:

1. Establish EN 16931 as the data model — independent of the output format
2. Build Peppol readiness — Peppol will de facto be the EU-wide transport path
3. Clean up master data — VAT IDs, addresses, payment details captured in structured form
4. Structure invoice corrections — credit notes as their own documents, not as text attachments

Already ViDA-ready with the Dokmatiq API

The API produces every variant ViDA expects — and validates against EN 16931 plus the relevant CIUS (XRechnung, Peppol, Factur-X, ebInterface):

# Cross-border Peppol invoice (ViDA-ready)
curl -X POST https://api.dokmatiq.com/v1/einvoice/peppol \
  -H "Authorization: Bearer $DOKMATIQ_KEY" \
  -d '{
    "customizationId": "urn:fdc:peppol.eu:2017:poacc:billing:3.0",
    "senderEndpoint": { "scheme": "9930", "id": "DE123456789" },
    "receiverEndpoint": { "scheme": "9915", "id": "AT-U12345678" },
    "invoice": { ... }
  }'

Common misconceptions

1. “ViDA forces everyone onto XRechnung” — no. EN 16931 is mandatory. XRechnung is one implementation among several.
2. “EDI is dead” — no. EDI flows remain permitted but must be mappable to EN 16931 semantics.
3. “There’s time until 2030” — national mandates in Germany, France and Poland kick in before ViDA. Anyone active there must switch earlier.
4. “Paper stays valid for domestic invoices” — only where nationally permitted. From 2030 the EU offers no exemption for cross-border B2B paper invoices.