ViDA: What Comes After the German E-Invoicing Mandate

Many companies treat e-invoicing as a German topic with a German timetable: receiving since 2025, issuing from 2027 and 2028. That is correct, but incomplete. Above this national staged plan sits a European reform that sets the long-term frame: VAT in the Digital Age, or ViDA, formally adopted on 11 March 2025 as Directive (EU) 2025/516. Anyone designing their e-invoicing architecture today only around the German deadlines is planning too short.

The key point up front: ViDA and the German mandate do not contradict each other, they interlock. Both rely on the European standard EN 16931 as the structured format. Whoever implements that standard cleanly is working in both directions.

The frame already shifted in 2025

An often overlooked building block is already in force. Since 14 April 2025, member states may introduce a domestic B2B e-invoicing mandate without needing a special EU authorisation, and without the invoice recipient having to consent. That is precisely the legal basis on which national mandates such as Germany’s now stand without a detour. The structured e-invoice under EN 16931 thereby moves from the special case to the European default.

2030 is the date that really matters

The German staged plan ends in 2028; the European reform only really begins afterwards. The central dates:

• 1 January 2027: minor clarifications for the One-Stop Shop and IOSS.
• 1 July 2028: new platform rules (deemed supplier) for short-term accommodation and passenger transport, plus steps toward a single VAT registration.
• 1 July 2030: Digital Reporting Requirements for cross-border intra-EU B2B transactions. The invoice must be issued in structured form under EN 16931, within 10 days of the taxable event. The current recapitulative statement is abolished.
• 1 January 2035: national real-time reporting systems must be aligned with the EU model.

For cross-border trade, 2030 is therefore the sharper break than 2028. Whoever thinks today only about domestic German issuance misses the reporting dimension that follows soon after.

Reporting is not the same as invoicing

The conceptual leap in ViDA lies less in the format than in the reporting path. So far the pattern is: issue the invoice, collect later, report periodically. In future, reporting moves close to the transaction. The structured invoice is at the same time the record reported to the tax administration almost in real time. That changes the requirements for data quality and timing: a format that only gets corrected after the fact does not fit a report due within days.

Whoever builds receiving and issuing processes today should therefore separate two things and consider both: the format (EN 16931, in Germany as XRechnung and ZUGFeRD) and the later reporting capability over interoperable routes such as Peppol.

What makes sense now

Three checks pay off: is the solution in use really EN 16931 compliant, or just PDF-with-attachment? Are cross-border B2B transactions cleanly separated in the process, since they are exactly the ones affected first in 2030? And is the architecture built for interoperable transmission, so that a later reporting obligation does not force a re-implementation?

Our own billing has issued invoices to EN 16931 from the start, with XRechnung and ZUGFeRD, aligned to the standard that underpins both the German mandate and ViDA. The point itself, though, is independent of any tool, namely to treat e-invoicing not as a German interim goal but as a building block of a European reporting system that goes live in 2030.

The German mandate is the first step. ViDA is the staircase.