Electronic invoicing becomes mandatory for domestic B2B invoices: what the Dutch cabinet announced in September

On 11 September 2026, Dutch state secretary for finance Eelco Eerenberg sent a policy letter, a contourenbrief, to the House of Representatives. The title sounds dry, electronic invoicing and reporting, but the content touches almost every business that sends or receives invoices in the Netherlands. The cabinet does not just want to comply with the EU's ViDA directive for cross-border invoices, it wants to make e-invoicing and digital VAT reporting mandatory for invoices between Dutch companies too.

That is a deliberate choice. The EU directive only requires e-invoicing from 1 July 2030 for intra-community B2B transactions, invoices between businesses in different member states. For purely domestic invoices, the Netherlands would not have had to act at all. The cabinet is choosing to go further anyway, arguing that one system for all B2B invoices is simpler than a patchwork of domestic PDF invoices alongside mandatory structured e-invoices for cross-border trade.

What changes, and when

According to the policy letter, two obligations arrive in sequence. From 1 July 2030, businesses would need to send a structured electronic invoice for domestic B2B transactions, a file software can read automatically, instead of a PDF a person has to retype. From 1 July 2031, digital reporting is added on top: a selection of data from those invoices would go to the Dutch tax authority automatically. Both dates come from the policy letter and are not yet law. The actual bill still needs a public consultation and the full parliamentary process.

Which standard will apply

The cabinet is choosing the European standard EN 16931, without adding a separate Dutch standard on top. That is good news for software vendors and accountants, since it means one format instead of a Dutch variant that would need to be built separately. The cabinet also wants to shorten the legal deadline for issuing an invoice to ten days after delivery of the goods or service, compared to the looser term in common use today.

How this connects to Peppol

Invoices to the Dutch central government already have to go through Peppol, the international network for electronic invoicing. That infrastructure already exists and larger suppliers already use it in practice. The expectation within the industry is that the new obligation will lean on that same infrastructure, although the policy letter does not confirm that outright. For organisations that are already Peppol-ready for government contracts, the step to broader e-invoicing is therefore smaller than for those that have never worked with structured invoices.

What the tax authority does with your data

One sensitive point in the letter is what happens to all that data. The Dutch tax authority would collect and store business-sensitive information from millions of invoices. The cabinet acknowledges that risk and states that access to the data will be logged and restricted, with a proposed retention period of ten years. For organisations already working out who inside the company may access financial data, this is a good moment to also consider who at the tax authority gets access, and how that compares with your own internal rules.

What this means for your invoicing system

The practical impact is not really about 2030, it is about the software choices you make now. Do you still send invoices as a PDF by email, or does your accounting package already send and receive invoices as structured files? Does your current system work with a network such as Peppol, or would that still need to be connected? For organisations already considering a new accounting package, an invoicing module, or a link between CRM and financial software, it makes sense to choose a solution that can already handle structured e-invoices. That avoids a forced migration a few years from now, under time pressure.

This touches more than the finance department alone. A webshop that generates invoices automatically, a CRM that turns quotes into invoices, or a link between a point-of-sale system and the books: wherever an invoice is created today, it will eventually need to happen in a way an automated system can read. Anyone already renewing or reconnecting systems over the coming years can build that project so e-invoicing is part of it from the start, rather than a separate job bolted on later.

What you can do now

Nobody needs a new system tomorrow. The first obligation would take effect at the earliest in 2030, and still has to pass through parliament. Still, a few low-cost steps now will save time later. Map out which invoicing and accounting software you currently use and whether it already supports e-invoicing. Ask your accountant or bookkeeper how they are following the development, they are often the first to see what vendors are actually building. And if you are already working on connecting systems, for example a new accounting integration or a renewed CRM, add e-invoicing as a requirement instead of solving it separately later.

Earlier this year, the Cyberbeveiligingswet already showed that Dutch regulation can move faster than organisations expect. With e-invoicing there is still time, but the direction is set: structured data instead of PDFs, and a link with the tax authority that goes beyond today's VAT return. This is Dutch tax policy rather than an EU-wide rule, so the specific dates and scope apply within the Netherlands. Want to know whether your current software and integrations are ready for this change, or do you need help connecting your invoicing and accounting systems? Contact Zarioh for a no-obligation conversation.