The EY report on ViDA: what it says, what it omits, and what it means

A report with a conclusion — and a story around it

On 10 March 2026, the Dutch Ministry of Finance published a research report on the introduction of e-invoicing and digital reporting in the Netherlands, conducted by EY Tax Advisors. The report, delivered to the client on 23 January 2026, was triggered by the European ViDA directive (VAT in the Digital Age), which from 1 July 2030 will require all EU member states to report cross-border B2B transactions digitally. The report’s core conclusion is clear: the Netherlands should opt for the broader variant — ViDA-B — making e-invoicing mandatory for domestic B2B transactions as well, using Peppol as the prescribed infrastructure, phased in between 2030 and 2032.

That is an important recommendation, substantiated carefully. But anyone who reads the report closely will find several passages that raise more questions than they answer. This article surfaces those passages — not to undermine the report, but because the policy debate that must precede its conclusions is better served by precision.

The Netherlands is behind — and that has consequences for the entire chain

While Belgium has been fully operational with mandatory B2B e-invoicing via Peppol since January 2026, and France, Germany and Poland are rapidly preparing their systems, the Netherlands at the time of this report’s publication is still in the process of forming a position. Not implementing — forming a position. That is a meaningful distinction.

That delay is not purely an administrative problem. It puts pressure on every link in the chain simultaneously. Policymakers must translate legislation into appropriate policy instruments in time — and that requires decision-making that should already be underway. Software vendors and Peppol Service Providers must adapt, certify and scale their products and services — and they need implementation time that begins only once the policy framework is clear. And at the end of the chain stand businesses, government organisations and institutions, all of which must adapt their processes, staff and planning to a new reality.

The deadline of 1 July 2030 looks comfortable on paper. But anyone who traces the chain from back to front — from business to software vendor to policymaker — will see that every month of delay at the beginning multiplies at the end. This report is an important step. But it is a late one.

1. The Netherlands doesn’t really have a free choice

The central question in the report — ViDA-A or ViDA-B — implies that the Netherlands still has an open decision to make. But the report itself reveals something that relativises that framing: every country studied that has introduced or is about to introduce e-invoicing has opted for a domestic mandate. Belgium went live in January 2026. France follows in September 2026. Germany, Italy, Poland — all equivalent to ViDA-B.

The report calls this the waterbed effect: if the Netherlands is the only major EU economy not to introduce a domestic mandate, it becomes more attractive for VAT carousel fraud. Fraudsters migrate to the jurisdiction with the least oversight. In other words, the freedom of choice the research framework implies is more limited in practice than it appears. ViDA-B is the logical outcome — the question is only how and when.

What stands out in the report’s international comparison is which countries are absent. The Scandinavian countries — Norway, Sweden, Denmark and Finland — are referenced only briefly, through a cost savings study by a software vendor. Yet these countries have some of the most mature e-invoicing ecosystems in the world, with decades of experience building interoperable standards, broad adoption and public-private collaboration. Their lessons for the Netherlands go unexamined. The same applies to Latin America: Chile, Brazil, Mexico and others have had mandatory e-invoicing for decades as a VAT enforcement instrument. The report cites their tax revenue gains, but does not analyse what made those systems architecturally successful — and what the Netherlands could learn from them.

2. Almost no one in SMEs knows what ViDA is — and the clock is ticking

One of the most soberly worded findings in the report is also one of the most alarming: awareness of ViDA among small business owners is ‘very low’. Those are EY’s own words. At the same time, the report recommends starting the domestic e-invoicing mandate before 1 January 2030, precisely to prevent businesses from facing a big bang on the European deadline.

Anyone familiar with ERP implementation timelines, supplier selection and internal process adaptation knows that 2030 is closer than it sounds. For large companies, a two to three year horizon is workable. For SMEs — with limited IT budgets and often no dedicated finance team — a migration trajectory of 12 to 24 months is realistic. That means preparation should be starting now. Not after the public consultation. Not after legislation. Now.

Here it is worth drawing a distinction the report does not make. The impact of e-invoicing does not differ primarily according to the size of a business or organisation, but according to the accessibility, flexibility and affordability of the permitted solutions. A freelancer who can send invoices via a simple accounting app or web portal faces a fundamentally different barrier than one whose app is not yet connected to Peppol — and who therefore has to wait for their software vendor to catch up, or switch to a different solution. The policy choice of which solutions are permitted — and how accessible the entry point is for small businesses — is therefore at least as decisive for the transition’s success as the implementation timeline itself.

3. ICV reporting is unworkable — but that is no surprise

One of the less well-known but practically significant components of the ViDA directive is the ICV reporting obligation: the requirement to report invoices received from other EU countries to the Tax Authority within five days. The report is notably direct on this point: implementation in 2030 is not advisable. Invoices are rarely approved within five days in practice, let alone processed. The result would be a flood of ‘false positives’ — reports that later need to be corrected — creating administrative burden for both businesses and the Tax Authority.

That the Tax Authority itself acknowledges this is presented in the report as a relevant observation. But there is a more honest way to frame it: the five-day deadline is not unworkable because it was poorly designed. It is unworkable because the Netherlands never created the infrastructural conditions for it. In countries where e-invoicing has been broadly adopted for years — Belgium, the Scandinavian countries, various Southern European countries — a five-day reporting deadline is a realistic standard, because invoice data already flows through systems in a structured and machine-readable way. In the Netherlands, that is not the case. And that is not a coincidence. It is the result of years of inaction on the e-invoicing file.

Other countries moved quickly to drive broad e-invoicing adoption, partly because they understood that European digital reporting obligations were coming. The Netherlands did not take that step. The finding by EY and the Tax Authority that the ICV deadline is unworkable is therefore less an observation about the directive than a quiet acknowledgement of policy failure. The report does not make that conclusion explicit — understandable in the context of an advisory report to the commissioning ministry. But anyone reading it is entitled to say so.

EY recommends as an alternative shortening the VAT filing period from quarterly to monthly. That is a pragmatic way out. But it does not resolve the underlying problem: as long as e-invoicing in the Netherlands has not reached a mature level of adoption, any form of real-time or near-real-time reporting will remain a theoretical obligation with a practical exemption.

4. There is an option the Netherlands is deliberately not taking — and few know it exists

Article 168 of the VAT Directive gives member states the option to link VAT deduction to receipt of a correct e-invoice. In practice, that would mean: no valid e-invoice received, no VAT deduction. A hard compliance incentive, but also a potentially far-reaching measure for businesses encountering technical failures or format errors during the transition period.

The report explicitly recommends against implementing this option. Industry is opposed, and EY endorses that concern. But the fact that this option exists at all — and that a deliberate policy choice is needed not to use it — is unknown territory for most businesses. It illustrates how multifaceted the ViDA implementation space is, and how important it is that businesses understand not just the final outcome, but also the choices being made in the policy process.

5. The main recommendation comes with a legal caveat — and a governance blind spot

The recommendation to mandate Peppol as the digital infrastructure for e-invoicing and reporting enjoys broad support — from software vendors, government bodies and business organisations alike. That support is genuine and the arguments are clear: Peppol is interoperable, scalable, internationally widely adopted, and connects to existing B2G infrastructure in the Netherlands.

But the report also contains a passage that has received little attention in public debate. EY notes that Peppol, as a non-qualified trust service, may not meet the eIDAS requirements that apply if it is designated as mandatory infrastructure. And that NIS2 cybersecurity requirements — not yet even implemented in the Netherlands via the Cybersecurity Act — will bring additional obligations. EY therefore recommends ‘further legal research’. The recommendation to mandate Peppol is already there, but its legal soundness still needs to be established.

This raises a deeper question the report does not sufficiently address: is it wise at all to enshrine the name of a specific network in legislation? As early as 2019, Hooghiemstra & Partners — commissioned by the Ministry of the Interior (BZK) — advised explicitly that the government should move towards a role in which it actively delivers or facilitates the trust structure of the e-invoicing infrastructure, rather than leaving that question to the market. The report introduced the ‘Stuurman’ (Helmsman) model for this: a government that acts proactively and as executor, delivering the trust structure itself. The opposite — a government as ‘Reder’ (Shipowner) that merely sets conditions and only intervenes when the public interest demands it — was explicitly assessed in that advice as insufficient for a system of public interest. The EY report does not reference this advice, and thereby poses the same question seven years later that was already asked — and answered — in 2019.

The parallel with eHerkenning is instructive: that system was not placed in legislation by brand name either, but as a framework of agreements that must meet statutory requirements and on which the RDI exercises oversight. That same approach — the government as active deliverer of trust structure, with admission based on objective criteria and statutorily grounded oversight — gives the government steering capacity that directly mandating the Peppol brand name does not, and keeps legislation future-proof.

The report itself acknowledges that OpenPeppol is a private legal entity based in Belgium, with its own interests that do not automatically align with Dutch policy objectives. And that when Peppol is designated as mandatory infrastructure, its private governance ‘effectively becomes part of a publicly mandated system’ — requiring further legal analysis that has not yet been done. What is also missing is any analysis of how the Dutch government can secure governance influence within OpenPeppol: who sits at the table, which countries have voting rights, and does the Netherlands have comparable positions to those it holds in other international financial and technical organisations? The report does not ask the question.

Finally, the report states that the RDI ‘already has practical experience with oversight’ of Peppol. But formal supervisory authority in the sense of administrative law — the power to verify compliance with statutory requirements — requires a statutory designation. That designation does not currently exist. The report’s framing creates an impression of formal supervisory authority that is not yet in place. This too is a gap that must be addressed before Peppol can be designated as mandatory infrastructure.

6. The Tax Authority will soon have real-time insight — but the legal framework is lagging

The essence of ViDA-B is not just that businesses invoice electronically, but that invoice data is reported to the Tax Authority in near real-time. That is a fundamental shift: where the Tax Authority currently receives periodic returns and audits retrospectively, it will soon have transaction-by-transaction insight into the accounts of businesses.

The report acknowledges the opportunities — less VAT fraud, a partly pre-filled VAT return, more efficient oversight. But it also addresses the risks: prematurely classifying errors as fraud, incorrect fiscal conclusions based on incomplete data, and questions about which analytical methods the Tax Authority may use. What is missing is an answer. The legal frameworks governing how the Tax Authority may use that data have not yet been established. The GDPR assessment has not been completed. The Data Protection Authority has not yet been formally involved. The report rightly recommends this — but the urgency of that step is not always felt in the follow-up process.

7. A note on representativeness — a small one and a large one

An observation that is not a criticism of the report’s quality, but is relevant for the policy formation that follows from it. The interview list contains twenty parties: seven government bodies, nine technology companies — including SAP, Microsoft, IBM and a number of specialist e-invoicing vendors — and two industry associations. In addition, three anonymous SME businesses were consulted.

Those are the only individual businesses represented, in a population of over 2.5 million registered companies in the Netherlands. Industry associations like VNO-NCW and the Platform for Independent Entrepreneurs represent their members at an abstract level, but are not businesses themselves. The technology parties have a legitimate perspective, but also a commercial interest in the outcome: they sell precisely the services businesses will need under a mandate.

That does not make the conclusions wrong. But it underscores why the public consultation recommended by EY itself is so important — and why that consultation needs to be broad and accessible. The experience of the installer, the bookkeeper and the freelancer is different information from the strategy of an ERP vendor.

Then the larger observation. The report was commissioned by the Ministry of Finance, and that is visible in its scope. E-invoicing is treated as a fiscal question: VAT enforcement, digital reporting to the Tax Authority, fraud prevention. That perspective is legitimate and forms the core of the ViDA directive. But e-invoicing is simultaneously an infrastructure question — and for that, a different ministry bears policy responsibility.

The Ministry of the Interior and Kingdom Relations (BZK) is, within the framework of the Generic Digital Infrastructure (GDI) and the Digital Government Act, the ministry responsible for e-invoicing as part of the government’s digital infrastructure. BZK is the principal of Logius — the implementation organisation that manages the Peppol network for central government. BZK is the principal of the national digital infrastructure inspectorate (RDI) — the supervisory body repeatedly cited in the report as the authority overseeing Peppol. And BZK is the body that established the Dutch Peppol Authority (NPa).

BZK does appear in the steering committee — this emerges from a single subordinate clause in the research methodology section. It is the only time the ministry is mentioned by name in the entire report. In the main text, the analysis, the recommendations and the conclusions: no mention. Yet three of the five government bodies on the interview list — Logius, RDI and the NPa — fall directly under BZK’s policy responsibility. The implementation organisations were consulted; the policy principal of those implementation organisations was not.

The questions this raises are fundamental: how does the fiscal policy of Finance relate to the infrastructure policy of BZK? Who bears ultimate responsibility for the choices recommended in this report? And how will the governance structures of the NPa, Logius and RDI be embedded in a statutory framework drafted by Finance, while the implementation rests with BZK bodies? The report provides no answer. The question is whether it was ever asked.

8. The real opportunities of e-invoicing are being underestimated

The report presents cost savings as the primary benefit of e-invoicing. International studies are cited: 55 to 70 percent savings per invoice compared to paper-based processes, a Scandinavian business case of 19 billion euros per year, a Dutch potential of 10 to 12 billion euros with full adoption. These are impressive figures. But they deserve two caveats the report does not make.

The first: cost savings only materialise once e-invoicing is the only permitted method and the entire chain participates. As long as paper invoices, PDF emails and portal solutions continue alongside e-invoicing, it is an additional cost for most businesses — not a replacement. And even after a full mandate, savings are only realisable if every element is structurally in place: identification and authentication, digital signing, timestamps, secure connections, standardised messages, authorisation management and Know Your Business processes. That is a systemic change, not a software update.

The second caveat is more fundamental: cost savings are probably not the most interesting benefit of e-invoicing. Implementing the European invoice standard EN 16931 enables the exchange of structured financial data — data that is machine-readable and analysable for both parties in a transaction. That opens the door to a new generation of fintech applications. Consider factoring that no longer depends on manual assessment, but on continuous insight into the financial cycle of a business. Consider supply chain finance where a supplier’s reliability can be inferred from their invoicing history. Consider automated credit assessments based on real transaction data rather than annual accounts. These are not speculative scenarios — in countries with mature e-invoicing infrastructure, these business models already exist. The report does not mention them. That is a missed opportunity in a study that is meant to help the Dutch government make a strategic decision.

What now?

The EY report provides a solid basis for policy decisions. The conclusion that the Netherlands should opt for ViDA-B — broad implementation, Peppol as infrastructure, phased timeline — is well-founded and aligned with what other EU countries are doing. The urgency is real.

But the report also reveals how much still needs to be worked out: the legal basis for Peppol as mandatory infrastructure, the GDPR assessment of data fields, the legal position of businesses when data is analysed by the Tax Authority, and the concrete design of exemptions for small businesses and specific sectors. That work requires time, broad consultation — and a deliberate choice to include the voice of individual businesses.

The pressure on the chain is real. Policymakers who decide now give software vendors the space to build. Software vendors who build in time give businesses the space to implement. And businesses that implement on time will not find themselves under pressure at the 2030 deadline. That chain only works if the first link — policy — starts moving. That is the real urgency behind this report.

Sources

• EY Tax Advisors, ‘ViDA e-invoicing and digital reporting’, commissioned by the Dutch Ministry of Finance, delivered 23 January 2026, published 10 March 2026.

• Hooghiemstra & Partners, ‘Advies publiek belang SI — Definitieve rapportage versie 1.0’ [Advisory report on public interest in SI], commissioned by the Dutch Ministry of the Interior and Kingdom Relations (BZK), 16 September 2019.

At Peppol.now, we follow ViDA policy developments closely. Want to know which reliable Peppol Service Providers are available for your organisation? Browse the overview at Peppol.now.