Is e-invoicing already mandatory in the Netherlands?
No, not for invoices between businesses. B2G invoices to the government have been mandatory via the Peppol network for years. But for B2B transactions, there is no legal obligation in 2026. The Ministry of Finance sent an advisory report to the House of Representatives in early 2026 pointing toward a mandatory Peppol-based system, in line with the European EN 16931 standard. A definitive cabinet position is expected in the second half of 2026, after which public consultation on draft legislation will follow. The intended phased implementation starts no earlier than 1 January 2030. Any reports of an obligation in 2026 or 2027 confuse the Dutch B2B situation with requirements in Belgium, Germany, or the broader ViDA plans coming out of Brussels.
Why is your finance team already feeling the pressure?
Practice is ahead of the law, and that is the core of the problem. Three situations are already occurring in practice. One: if you supply to the Dutch government or to Belgian customers, they already expect Peppol invoices. Two: large procurement departments at companies increasingly refuse to accept PDF by email as a form of digital invoicing. Three: you receive invoices from suppliers in a mix of formats. One supplier sends a Peppol message, another sends a PDF, a third sends an Excel attachment. That mixed landscape is exactly where manual work accumulates: someone opens the attachment, locates the invoice number, the amount, the VAT breakdown, and types it into the accounting system. That work already exists. It simply becomes more visible as pressure increases.
Does a PDF by email count as e-invoicing?
No, and this misconception costs businesses unnecessary time. Sending an invoice as a PDF via email is technically not e-invoicing in the legal sense. E-invoicing requires a structured, machine-readable format, such as UBL or Peppol BIS, so that the receiving party can automatically process the invoice data without manual intervention. A PDF is an image of an invoice, not a structured message. That distinction is precisely why the transition to genuine e-invoicing demands more than a software update: it affects the entire document flow, from how you send to how you receive, validate, and process. Accounting packages such as Exact Online, AFAS Profit, and Twinfield are actively working on Peppol integrations on the sending side, but receiving invoices in varying formats remains a separate operational challenge.
What will change in the incoming invoice flow towards 2030?
The timeline towards 2030 provides room to maneuver, but that room disappears quickly if you do not start in time. Two developments are running in parallel. On the outgoing side: if you sell to the government or to customers in countries that already have an active obligation, you must be able to send invoices in the correct format right now. On the incoming side: the invoices you receive in 2026 still arrive in every possible format. As long as those are not structured, manual work is still required to process them in your ERP or accounting system. And even when suppliers have switched to Peppol, you will need something that picks up those structured messages, validates them, and delivers them to the right place in your system. The format changes; the processing challenge remains.
When does automating invoice processing make sense?
The payback period varies by company. If you process twenty supplier invoices per month, automation is probably not yet urgent. But once you are moving towards a hundred or more invoices per month, every invoice is being manually keyed into an ERP or accounting system, and invoices arrive in varying formats from different suppliers, it becomes relevant. At that point it is not just about efficiency: it is also about reducing errors and freeing people to do better work than copying data. A system like dottle reads varying formats, PDF, Excel, and soon Peppol as well, recognizes the relevant fields, and delivers them where the work happens, with a person approving before the booking is final. No templates per supplier, no months-long implementation. That applies today for PDF invoices, and it will apply equally to the structured invoices arriving via Peppol.