Product updates7 Jul 20267 min read
Mandatory E-Invoicing: Cabinet Chooses July 1, 2030
The Dutch cabinet wants B2B e-invoicing mandatory from July 1, 2030, domestic too. Reporting follows in 2031. What ViDA, Peppol and your software mean now.
Co-founder

Introduction
The Dutch cabinet wants to make e-invoicing mandatory for business invoices from July 1, 2030, for both international and domestic B2B transactions. Digital reporting to the tax authority follows from July 1, 2031. This follows from the Dutch government news release of September 11, 2026 on the introduction of e-invoicing and reporting (ViDA). Businesses in the small business scheme (KOR) with a turnover of up to €20,000 per year remain exempt. The bill is expected to be submitted to the House of Representatives before the summer of 2027.
We build a lot of invoicing modules, client portals and integrations with accounting packages, so this legislation regularly lands on our drawing board. In this article we lay out what has been decided, what is still open, and what you need to arrange at which moment.
Last updated: October 14, 2026. What changed: the cabinet decision of September 11, 2026 is included, with the domestic obligation and the split deadlines of 2030 (e-invoicing) and 2031 (reporting). The KOR exemption has been added and the old wording about a pending cabinet decision has been removed. The article was originally published on July 7, 2026.
What Has Been Decided and When?
| What | Date | Status |
|---|---|---|
| EU ViDA agreement (VAT in the Digital Age) | March 11, 2025 | adopted |
| Cabinet chooses e-invoicing and reporting for domestic B2B as well | September 11, 2026 | policy decision |
| Draft bill public consultation | autumn 2026 (announced) | announced |
| Bill to the House of Representatives | before summer 2027 (expected) | announced |
| Mandatory B2B e-invoicing (NL, including domestic) | July 1, 2030 | policy goal |
| Mandatory digital reporting | July 1, 2031 | policy goal |
| KOR exemption (turnover ≤ €20,000/year) | remains after July 2030 | policy choice |
Source: Dutch government news release of September 11, 2026; consulted October 13, 2026. The ViDA agreement: Directive (EU) 2025/516.
Want to know whether your portal or webshop is ready for Peppol? We will walk you through it.
What Was Decided in Brussels
ViDA stands for VAT in the Digital Age, a package of revised VAT rules that the Council of the European Union adopted on March 11, 2025 (Directive (EU) 2025/516). From July 1, 2030, cross-border B2B transactions across the EU are reported digitally and per transaction. Invoices in principle follow the European EN 16931 standard and are sent in a structured format.
The goal is fighting VAT fraud: the EU VAT gap was an estimated 93 billion euros in 2020 (recital 3 of the directive). For the Dutch tax authority it means a fundamentally different information position: instead of periodic returns after the fact, the tax office sees the data of each transaction.
What the Cabinet Decided on September 11, 2026
The directive only mandates cross-border traffic. For domestic B2B invoices, member states can choose whether to extend the obligation. On September 11, 2026 the cabinet made that choice: e-invoicing and reporting also apply to domestic B2B transactions. The Netherlands thereby takes the same route as France, Germany and Belgium, among others.
For domestic transactions there are two dates: electronic invoicing from July 1, 2030 and reporting from July 1, 2031. These are two deadlines, not one. Businesses in the KOR with a turnover of up to €20,000 per calendar year are exempt, and that exception continues to apply after July 2030. The draft bill goes into public consultation this autumn; the cabinet aims to submit the bill to the House of Representatives before the summer of 2027. Until then this is a policy decision and not yet legislation.
What Actually Changes About an Invoice
An e-invoice is not a PDF you email. It is a structured data file, usually XML following the EN 16931 standard, that the receiving system can automatically read, validate and book. No retyping, no scan-and-recognize software that turns an 8 into a 3, no invoices stuck in someone's mailbox.
Peppol is already widely used in the Netherlands for invoicing the government and is the common route for structured invoices. Which infrastructure the bill will prescribe remains to be seen.
What Does This Mean for Your Software?
An e-invoice is usually a UBL message exchanged via Peppol, following EN 16931. For SMEs this often means: an accounting package that can send and receive e-invoices, a webshop or portal that speaks the same standard, and later a path to digital reporting.
The real work sits with companies that have custom software in the invoicing chain. Think of a webshop that generates its own invoices, a SaaS product with its own billing module, a client portal where invoices are published, or an ERP system with custom invoicing. Everywhere a PDF currently rolls out of a template, a valid EN 16931 invoice must come out instead, and everywhere purchase invoices come in, structured data must be received and processed.
In our projects, most of the time goes into normalising customer and order fields, not into "one more export button". What a well-scoped integration costs depends on the number of source systems. This is our own project experience and an indication, not a guarantee. We build these kinds of API integrations daily. You can find a first indication of costs in what an app or portal costs. Also keep your clients' security requirements in mind for integrations: see the Cyberbeveiligingswet (Dutch NIS2 law).
The Opportunity Hidden in the Obligation
It is tempting to see this as yet another compliance burden, but there is an efficiency opportunity too. A purchase invoice that arrives automatically, gets validated and sits ready for approval saves retyping and the search for lost or incorrect invoices.
For companies with high invoice volumes, that can be a business case in itself. Run the numbers: one hundred purchase invoices per month times five minutes of manual processing is more than a full working day per month. Whether an integration pays for itself depends on what it costs. Our calculator gives a first indication.
A Realistic Timeline Toward 2030
For most companies, mandatory e-invoicing is not a software replacement but an integration question. If you fold it into regular development, you will barely notice it later.
Jordan Munk, co-founder MG Software
There is no reason to panic, but there is reason to plan. The decision has been made and in the coming months the legislation becomes concrete: the public consultation on the draft bill this autumn, then the bill's journey through parliament. If you trade with other EU countries, your July 1, 2030 deadline is already fixed.
Our rule of thumb: in 2026, map where invoices originate and arrive in your processes and which systems are involved. In 2027–2028, ask your package vendor about Peppol/EN 16931 support, identify which custom software needs adapting and plan integrations well before 2030. That lets you include the changes in regular development work instead of an expensive rush job in 2029.
Conclusion
ViDA is coming and the cabinet has chosen: it wants to make e-invoicing mandatory on July 1, 2030, domestic B2B invoices included, and digital reporting on July 1, 2031. The bill still has to pass parliament, so until there is legislation it remains an intention. If you have custom software in your invoicing chain, mapping that chain now is time well spent.
Do you have custom invoicing, a client portal or integrations that will be affected? Take a look at our software integrations or get in touch and we will look at what is needed and when. In our experience it is usually less work than feared, as long as you start on time.
Sources (consulted October 13, 2026)
- Dutch government: Cabinet chooses to introduce e-invoicing and reporting for businesses (September 11, 2026, in Dutch).
- Directive (EU) 2025/516 (ViDA), EUR-Lex, March 11, 2025.
Frequently asked questions
Is domestic e-invoicing officially mandatory now?
Not yet in legislation, but it is a cabinet choice: the cabinet wants the obligation to apply from July 1, 2030, domestic B2B included. The bill follows (consultation autumn 2026, parliament before summer 2027).
What is the difference between 2030 and 2031?
July 1, 2030 = e-invoicing; July 1, 2031 = digital reporting per transaction.
Does this apply to me as a small business owner?
Businesses in the KOR with a turnover of up to €20,000 per calendar year remain exempt, according to the cabinet.
Will a PDF invoice still be enough?
Under the ViDA approach a structured e-invoice counts; a PDF alone will not suffice where e-invoicing is mandatory.
What should I do now?
Map where invoices originate (webshop, portal, Excel, accounting package) and whether those systems can handle Peppol/EN 16931 or need an integration.

Co-founder
Related posts
Product updatesWhat does a client portal cost in 2026? Honest price bandsRead article
Product updatesWhat Does Custom Software Maintenance Cost Per Year?Read article
Product updatesLegacy Software: 7 Signs It Is Time to Modernize (Before It Costs You Customers)Read article
Product updatesHow to Choose a Software Development Agency in 2026: 12 Questions That Reveal the TruthRead article