The Netherlands Sets Its ViDA Dates
Most governments announce an e-invoicing mandate and its technical plumbing in the same breath. The Netherlands has just done something less common: it has locked in the calendar while explicitly deferring the decision on how invoices will actually travel.
On 11 September 2026, State Secretary for Finance Eelco Eerenberg delivered an outline letter to the House of Representatives, written jointly with the Minister of Economic Affairs and the State Secretary for the Interior, setting out how the country intends to implement the EU’s VAT in the Digital Age package. The headline commitment is that the Dutch reform will not stop at the European minimum. Rather than confining the obligation to cross-border trade, the cabinet will extend both electronic invoicing and digital reporting to purely domestic transactions between businesses, placing the Netherlands alongside France, Germany, Belgium, Poland and Italy.
What the letter does not settle is the exchange infrastructure. Peppol is the obvious candidate and was formally recommended to the government, but ministers have withheld a decision while a competing option, the European Business Wallet, continues to take shape in Brussels. For anyone planning implementation work, that distinction between a fixed date and an unfixed network is the defining feature of the Dutch approach.
Key Dates
| Date | Milestone |
| 11 September 2026 | Cabinet outline letter delivered to the House of Representatives |
| Autumn 2026 | Public internet consultation on the draft bill opens |
| October 2026 | Supplementary research on infrastructure and data exchange concludes |
| Before summer 2027 | Bill submitted to the House of Representatives |
| Before 1 July 2028 | Parliamentary process completed, leaving a two-year run-up and room for testing |
| 1 July 2030 | Mandatory e-invoicing for domestic and intra-Community B2B transactions |
| 1 July 2030 | Per-transaction reporting of intra-Community supplies and acquisitions begins |
| 1 July 2031 | Digital reporting of domestic transactions begins |
A Deliberately Broad Reform
The ViDA Directive obliges every member state to bring cross-border B2B trade within the EU into a per-transaction digital reporting regime from July 2030, underpinned by structured invoices that meet a single European standard. Member states may then choose whether to apply the same machinery domestically. Many are exercising that option, and the Netherlands has now joined them.
The government’s reasoning rests on three arguments. Fragmented national VAT reporting rules currently act as a brake on intra-European trade, which matters disproportionately for an economy as export-oriented as the Dutch one. Transaction-level data gives the tax administration a far sharper instrument against VAT fraud than today’s periodic, aggregated returns. And once businesses have absorbed the initial investment, automated invoicing should reduce the ongoing administrative load rather than add to it.
There is also a practical consistency argument. Any business trading across EU borders will have to build EN 16931 capability regardless of what the Netherlands decides domestically. Running a parallel legacy process for home-market invoices would preserve exactly the duplication the reform is meant to eliminate.
Why Invoicing and Reporting Are Separated by a Year
The staggering of the two obligations is not incidental. E-invoicing arrives first, in July 2030, for both domestic and intra-Community flows. Domestic reporting to the tax administration follows twelve months later, in July 2031.
The logic is sequential. Digital reporting extracts a defined subset of fields from the electronic invoice and forwards it to the authorities. That extraction only functions once structured invoices are genuinely circulating throughout the economy. Compelling businesses to report before the invoicing layer has bedded in would mean building the roof before the walls. The interval gives companies a full year of live invoicing experience before the reporting obligation attaches on top.
Cross-border reporting, by contrast, starts immediately in July 2030 because the EU deadline permits no flexibility. From that date, the current aggregated intra-Community listings give way to reporting at individual transaction level, covering both outbound supplies and inbound acquisitions.
One Standard, No National Variants
On format, the cabinet has taken an unambiguous position: only the European standard EN 16931, as referenced in Commission Implementing Decision (EU) 2017/1870, will be recognised. No supplementary national standards will sit alongside it, and this applies to domestic invoices just as it does to cross-border ones.
This restraint is worth appreciating. Several countries have layered country-specific extensions on top of the European norm, obliging software vendors to maintain divergent local profiles and complicating life for multinational groups. By declining to do so, the Netherlands keeps its domestic requirement identical to the European baseline, which should make cross-border interoperability straightforward and limit development work on the software side.
A related change concerns timing. In line with ViDA, the window for issuing an invoice will contract to ten days following the supply of goods or services. Businesses that presently rely on monthly summary invoicing will need to revisit that practice, since the compressed deadline leaves considerably less room for batching.
The Unresolved Question: Which Rails?
Here the letter is candid about what remains open. The government has not chosen the infrastructure through which invoices will be exchanged.
Peppol is the incumbent favourite. The network is already compulsory for invoicing central government in the Netherlands, service providers are established in the market, and the independent study commissioned by the government recommended mandating it for business-to-business exchange. On evidence and maturity, it is the natural answer.
The complication is the European Business Wallet, a Commission initiative still under development that could eventually serve as a trusted channel for exchanging business documents at the highest assurance level. The cabinet has decided it would be premature to entrench a national infrastructure choice before that European component is clearer.
Supplementary research running until October 2026 is examining interoperability, how the invoicing and reporting layers should connect, secure and reliable data exchange, competitive dynamics among service providers, and how supervision and enforcement will operate. In parallel, an external consultancy is quantifying the administrative burden by business category, to be followed by an SME test, a business impact assessment and an implementation test by the tax administration.
For service providers and software vendors, this argues for modular design. The obligation itself is settled; the transport layer is not. Architectures that isolate invoice generation and validation from the transmission mechanism will absorb the eventual decision far more comfortably than those wired to a single assumed network.
Exemptions and Scope
The cabinet has opted against creating a dedicated micro-business threshold. The relevant carve-out instead follows the existing small business scheme (kleineondernemersregeling, or KOR): businesses with annual turnover at or below €20,000 are exempt from both domestic e-invoicing and domestic reporting, and that exemption survives beyond July 2030.
One qualification deserves attention. Exemption from the domestic obligation does not necessarily extend to cross-border activity. A KOR business making intra-Community acquisitions may still fall within the reporting requirement for those transactions, since that obligation derives from European rather than national law. Small businesses buying from suppliers in other member states should verify their position rather than assume blanket relief.
Beyond the KOR, the government intends to preserve existing invoicing exemptions wherever this is workable, which should leave the treatment of special VAT regimes broadly unchanged.
Data Protection as a Hard Precondition
The letter devotes notable space to safeguards around commercially sensitive information, reflecting a concern that has featured prominently in the Dutch debate.
The cabinet frames secure and responsible handling of business data not as a desirable feature but as a firm condition of implementation. Access to submitted data will be governed by authorisation and role-based controls, restricting tax administration staff to the information genuinely required for their duties. Every access and processing event will be logged, capturing who consulted the data, when, and for what purpose. The administration will operate a retention limit of ten years.
Reporting itself will follow the same data-minimisation principles being developed at European level. Only a defined subset of invoice fields will be transmitted, not the complete document. The draft bill will be referred to the Dutch Data Protection Authority for advice, and a data protection impact assessment will be conducted.
The Route to Legislation
The draft bill enters public internet consultation this autumn. The government then intends to submit it to the House of Representatives before the parliamentary recess in summer 2027, with the objective of completing the legislative process before 1 July 2028.
That target date is chosen deliberately: it preserves a full two years between enactment and entry into force, which the government regards as the minimum realistic window for businesses to adapt their systems and for a testing phase to run. Given that infrastructure questions remain unresolved and that considerable technical detail will only emerge through the consultation, that cushion looks less generous than the raw calendar suggests.
Preparing While the Network Is Still in Play
The uncertainty around infrastructure is no reason to defer preparation, because the substantial work sits below the transport layer.
Audit how invoices currently move. PDF attachments, paper, and bilateral EDI arrangements all fall short of what will be required. Anything that does not produce or consume EN 16931-compliant structured data will have to change before July 2030.
Test the ten-day issuance rule against existing practice. Monthly consolidated invoicing, common in some sectors, may not survive the shortened deadline in its present form.
Separate reporting data from invoicing data in the system design. The reporting subset must be extractable independently of the invoice exchange itself. Building this as a distinct capability rather than an afterthought avoids rework when the domestic reporting obligation lands in 2031.
Establish where intra-Community acquisitions sit. Inbound cross-border purchases attract reporting obligations from July 2030, including for some businesses that might expect to be outside the scope.
Ask software and ERP suppliers for a dated roadmap. Vendors that cannot articulate a concrete plan for EN 16931 support and digital VAT reporting are a risk worth identifying now rather than in 2029.
