What Is ViDA, the EU's E-Invoicing Mandate?

What Is ViDA?

ViDA (VAT in the Digital Age) is an EU regulatory package that modernizes VAT compliance through electronic invoicing and digital reporting requirements, with changes taking effect from March 2025 onward. It's not a single e-invoicing mandate you can point to and say "that's ViDA" — it's a legal framework that reshapes how VAT gets reported across the entire bloc, with the headline change being that mandatory digital reporting for intra-EU cross-border transactions begins on July 1, 2030.

The package was approved by the Council of the European Union on March 11, 2025 and from April 14, 2025, EU member states have the option to implement e-invoicing and e-reporting requirements for domestic supplies. That last point matters: it's the legal gate that let countries like Belgium and Poland move on their own domestic timelines without waiting for Brussels.

ViDA runs on three pillars, and Digital Reporting Requirements focuses on implementing mandatory e-invoicing for B2B intra-EU transactions, establishing digital reporting systems to facilitate the exchange of tax information between EU countries, and standardizing e-invoicing processes across member states. The other two pillars cover VAT on platform economy services (Uber, Airbnb-style marketplaces) and a single EU VAT registration to cut down on multi-country VAT filings. If you work in EDI or supply chain IT, pillar one is the only one that lands on your desk.

ViDA vs. National E-Invoicing Mandates (Don't Confuse These)

ViDA is the EU-wide legal umbrella. The country mandates you've likely already dealt with — Belgium, Poland, France — are each individual governments acting under that umbrella on their own schedules, years before ViDA's own EU-wide deadline arrives.

Here's the distinction in practice:

Notice the pattern: Belgium has required all VAT-registered businesses to exchange e-invoices since January 2026, Poland's KSeF covers large taxpayers from February 2026 with most businesses following in April, and France requires all businesses to receive e-invoices from September 2026 with large enterprises issuing from the same date. None of these dates are ViDA deadlines. They're sovereign decisions, made possible by ViDA's legal green light, running well ahead of the 2030 EU-wide requirement.

What ties them together technically is EN 16931, the semantic data standard. Belgium's default format is Peppol BIS Billing 3.0 (UBL 2.1), aligned with EN 16931, and the same standard underpins most other national formats, even when the wrapper differs. Domestic formats still vary by country — XRechnung for Germany, Factur-X for France, FatturaPA for Italy, Peppol BIS for Belgium, and KSeF for Poland. ViDA's 2030 layer is where the EU finally asks for one structured format and one reporting rhythm for cross-border trade specifically, rather than leaving it to each country.

ViDA vs. EDI: What Changes for EDIFACT/X12 Shops

ViDA does not retire EDIFACT or X12. What it does is add a tax-compliance layer on top of (or alongside) your existing invoice flows for cross-border transactions, with its own format rules and its own clock.

The structural shift is from periodic summary reporting to transaction-level reporting. The biggest change in ViDA is the move from periodic EC Sales Lists to transaction-by-transaction digital reporting based on e-invoices, and from July 2030 those recapitulative statements (European Sales Listings) will be replaced by DRR entirely. Your finance team used to file a monthly or quarterly recap. From 2030, each qualifying cross-border invoice gets reported close to real time.

Three mechanical details matter for anyone running EDI translators:

• Timing: cross-border e-invoices must be issued within 10 days of the chargeable event — tighter than most batch EDI cycles currently run.
• Format: from July 2030, electronic invoices must use structured formats that enable automated processing, while unstructured PDFs and JPEGs will no longer qualify. EDIFACT INVOIC and X12 810 are structured, but that doesn't automatically mean they carry the semantic fields EN 16931 demands.
• Legacy systems get a longer runway: member states with qualifying domestic real-time reporting systems established by January 1, 2024, have until 2035 to align with ViDA standards — relevant if you're dealing with Italy's SDI, which predates all of this.

How This Plays Out in Practice

Walk through the mandates already live and you can see the mechanics without needing a hypothetical. A Belgian seller and a Belgian buyer already settle B2B invoices as Peppol BIS Billing 3.0 documents, because that's been mandatory since 1 January 2026. A Polish seller invoicing another Polish business is routing through KSeF, with the invoice only legally "delivered" once it's been submitted through KSeF in FA(3) XML format. Neither of those is a ViDA requirement — both are domestic rules.

Now take the same Belgian seller invoicing a customer in Poland. Today, that's a cross-border B2B transaction governed by whatever bilateral VAT reporting exists now (EC Sales Lists). From 1 July 2030, it falls under ViDA's Digital Reporting Requirements: a structured EN 16931 invoice, issued within 10 days of the chargeable event, reported digitally to both tax authorities. Given Belgium's existing Peppol infrastructure, that invoice is very likely to travel over the same Peppol network already used domestically — just with the DRR reporting obligation bolted on.

This is where transport and freight invoicing gets interesting too. A freight bill between a shipper and a carrier operating across a Belgium-Poland lane is itself a cross-border B2B supply, which means transport management platforms processing those invoices need to either generate EN 16931-compliant structured documents or ingest them cleanly from a carrier's Peppol access point — not just pass along a legacy EDIFACT INVOIC and call it done. Platforms like Cargoson that reconcile carrier invoices against transport orders will increasingly need that reconciliation logic to understand EN 16931 field structures, not only flat-file EDI formats. The same applies to EDI and e-invoicing vendors bridging this gap commercially — names like EDICOM, Pagero, Comarch, SPS Commerce, TrueCommerce and Cleo all sit in this space, translating between legacy EDI and the structured formats tax authorities now expect.

What EDI and IT Teams Should Do Now

You don't need a 2030 project plan yet, but you do need a 2026 inventory. Concretely:

• Map which trading partner invoice flows are intra-EU cross-border versus purely domestic — ViDA's 2030 deadline only touches the first group.
• Ask your EDI translator or managed service provider directly what their EN 16931 output roadmap looks like, and get a date, not a promise.
• Check whether your current VAN, AS2 connection, or Peppol access point already supports Peppol BIS Billing 3.0 — if you're trading with Belgian partners, this isn't optional anymore.
• Don't anchor all your planning to 2030. Poland, Belgium, and France will all make electronic invoicing mandatory for business-to-business transactions years before the EU-wide rule applies, and if you have partners or subsidiaries in those countries, you're already exposed.
• Loop in your tax/finance function early — ViDA compliance crosses departmental lines in a way most EDI projects historically haven't.

FAQ

Does ViDA replace EDI?
No. It adds a structured e-invoicing and digital reporting layer for intra-EU cross-border B2B trade. Purchase orders, ASNs, and other EDI transaction sets are unaffected.

When does ViDA's e-invoicing mandate actually take effect?
Mandatory digital reporting for intra-EU cross-border transactions begins on July 1, 2030. Domestic mandates in individual countries are arriving much sooner.

Do non-EU companies need to comply?
If you're invoicing an EU counterparty on cross-border (intra-EU) B2B transactions, the transaction falls in scope regardless of where your own headquarters sits.

Is my EDIFACT INVOIC automatically ViDA-compliant?
Not necessarily. EDIFACT INVOIC is structured, but that doesn't guarantee it carries the specific semantic data elements EN 16931 requires. You need a mapping check, not an assumption.

What's the difference between ViDA and Peppol?
ViDA is the legal mandate; Peppol is a transmission network and message standard that many member states have chosen to meet their own obligations. Peppol is not a single EU-wide mandate — each member state decides its own e-invoicing rules, which is exactly why Belgium runs on Peppol while Poland runs its own KSeF platform instead.