8 min readUpdated: Category: Compliance & e-invoicing
ViDA at a Glance – Stages, Deadlines and Impact on SAP Landscapes
ViDA replaces the periodic summary VAT return with transaction-based digital reporting and makes e-invoicing mandatory across the EU single market.
Before (Recapitulative Statement)
- Reporting at an aggregated level (customer's VAT ID)
- Monthly or quarterly
- No detailed invoice data
- Risk of VAT fraud remains high
Going forward (ViDA)
- Transaction-based digital reporting (near real-time)
- Transmission of invoice data (e-invoice)
- Uniform digital standard formats across the EU
- More transparency, less fraud, fairer competition
- E-invoicing mandatory across the EU single market
Stages and Deadlines
- 1LegislationAdoption of the ViDA directive by the EU Council11 March 2025 (Council adoption)
- 2National transpositionEU member states transpose ViDA into national lawby 31 December 2025 (transposition into national law)
- 3E-invoicing (B2B)Mandatory e-invoicing across the EU single marketfrom 1 July 2030
- 4Digital reporting (DRR)Transaction-based digital reporting, near real-timefrom 1 July 2030 (at the latest), possibly earlier
- 5Further developmentEU-wide standards, extensions and optimizationsongoing from 2030
Impact on Businesses
| Criterion | Before | Going forward (ViDA) |
|---|---|---|
| Reporting scope | Aggregated (by VAT ID) | Transaction-based (detailed invoice data) |
| Reporting timing | Monthly / quarterly | Near real-time (within a few days) |
| Invoice format | Paper / PDF / EDI (freely chosen) | E-invoicing mandatory (structured formats) |
| System requirements | Lower requirements | Higher requirements for data quality, IT processes and integration |
| Risk of non-compliance | Fines, back payments | Higher fines, possible loss of input VAT deduction |
| Opportunities | – | Process automation, fewer errors, transparency, competitive advantage |
Impact on Existing SAP Landscapes
| Area | Description |
|---|---|
| Data model & master data | Extension of invoice data (e.g. additional mandatory fields), high requirements for data quality |
| Processes & integration | Adjustments to Order-to-Cash and Procure-to-Pay processes, integration with tax authority reporting systems |
| SAP solutions | Use and extension of SAP S/4HANA, SAP Document Compliance (eDocument Cockpit), SAP Integration Suite |
| E-invoicing capability | Support for structured e-invoicing formats (e.g. EN 16931, Peppol BIS) |
| Compliance & reporting | Ensuring digital reporting (DRR), archiving, traceability and audit readiness |
| Action required | Early project planning, gap analysis, system adjustments, and testing & go-live well ahead of 2030 |
Key takeaway: Companies should set the course now — get processes, data and systems e-invoicing- and digital-reporting-ready for a compliant future in the EU single market.
What ViDA Is About
"VAT in the Digital Age" is the EU's reform package that adapts the VAT system to digital business models. It rests on three pillars: digital reporting and invoicing requirements, an extended VAT liability for platforms in short-term accommodation rental and passenger transport, and an expanded single VAT registration so businesses no longer have to register separately in every member state.
For most German companies, the first pillar is the one that matters most: it links the national e-invoicing mandate to a European reporting architecture. Anyone who treats the two separately ends up building the same thing twice.
The Stages and Their Deadlines
Since the package entered into force in 2025, member states have been allowed to introduce national e-invoicing mandates without prior derogation — the basis that lets Germany carry out its roadmap through 2028. From 1 July 2030, e-invoicing becomes mandatory for intra-Community B2B transactions, accompanied by a transaction-based digital report that replaces today's recapitulative statement.
By 2035, existing national reporting systems that predate the EU model must be aligned with it. For planning purposes, that gives a realistic horizon: the architecture decisions made in 2026 and 2027 for the German mandate will carry through to 2030 — or trigger a second rebuild there.
What Changes Operationally
The biggest shift isn't the format, it's the cadence. Instead of a periodic batch return, every affected transaction is reported individually, close to real time. That raises the bar on data quality sharply: an incorrect VAT ID, an unclear description of the supply, or a header retroactively amended is no longer something fixed in the next quarterly run — it's an immediate discrepancy.
Second, the leeway around invoice timing disappears. Invoices for intra-Community transactions must be issued within tight deadlines after the tax point. Processes that today rely on month-end batch invoicing need a new design for that.
Third, credit-note and cancellation logic comes into focus: correction documents are also reportable and must reference the original document unambiguously.
Impact on SAP Landscapes
In SAP systems, ViDA typically touches four areas: billing in SD, the master data model for business partners and tax numbers, outbound interfaces in the integration layer, and archiving. Companies that have already solved the German e-invoicing mandate through a central outbound channel can usually dock the reporting onto it rather than building a second channel.
Error handling is the critical part. A rejected report is a tax matter with a deadline, not a technical side process. We recommend the same discipline as with IDoc monitoring: clear status models, named ownership, defined retry procedures, and reporting that prioritizes open cases as deadlines approach.
Next Steps
A short stock-take built around three questions is a good starting point: which document types involve intra-Community B2B transactions, which systems generate them, and where do most data errors occur today? The answers almost always produce a manageable list of measures that can be worked through in parallel with the German mandate.
OXORY supports this analysis close to SAP and then takes on implementation and operation of the outbound channel — including validation, Peppol connectivity and audit-proof archiving. If you want to check your landscape against the 2027-2030 deadlines, get in touch.