What does the Belgian e-invoicing mandate 2026 actually entail?
From 1 January 2026, Belgian VAT-liable businesses must exchange invoices with other Belgian businesses as structured electronic documents via the Peppol network. A PDF sent by email, however neatly formatted, no longer qualifies legally as a valid invoice. Belgian businesses that do not comply risk fines. The core requirement: machine-readable XML documents sent and received via an accredited Peppol access point, not an attachment in a mailbox. That is a fundamentally different infrastructure from what most Dutch finance teams use today.
As a Dutch supplier, am I covered by the Belgian mandate?
Legally, no. Belgian law applies to businesses that are VAT-liable in Belgium. A Dutch supplier invoicing from the Netherlands without a Belgian VAT registration falls outside the legal scope. But that distinction is smaller than it appears. A Belgian procurement manager who is internally required to work with Peppol messages gains little from a Dutch supplier continuing to send PDF invoices by email. The extra manual work lands with the Belgian finance team, which will eventually push it back to the supplier. The mandate is Belgian; the consequences are cross-border.
When will the e-invoicing mandate come into effect in the Netherlands?
The Netherlands is lagging behind its neighbours. The government is working on an implementation direction and expects definitive legislation around 2028, with a phased rollout towards 2030 and 2032. The European ViDA directive makes cross-border B2B e-invoicing mandatory from 1 July 2030. That is the hard EU deadline. For businesses that already work structurally with Belgian or other European parties, the practical pressure is already higher than the current state of Dutch legislation suggests. Waiting for Dutch legislation means waiting until the customer puts the problem on your desk.
What changes concretely in the document flow?
The shift to Peppol changes how invoices arrive and go out. Where PDFs by email currently dominate, the share of structured XML messages will grow steadily in the coming years. A Peppol invoice is machine-readable and contains fields that an accounting system can pick up directly. At the same time, the large volume of incoming invoices will continue to arrive as PDFs for the foreseeable future: suppliers from countries without a mandate will keep sending as they always have. Finance teams will therefore not face one new format, but an increasingly large mix of Peppol messages, PDFs, Excel attachments, and scanned receipts. It is precisely during this transition period that maintaining a consistent processing workflow is hardest, and that relying on manual data entry carries the most risk.
Is there value in automating now, before the Dutch mandate?
Waiting for Dutch legislation is understandable, but reality pushes for earlier action. Businesses that already process incoming invoices automatically, regardless of format, will find the move to Peppol processing a smaller step later on. A structured e-invoice is easier for a machine to read than a free-form PDF, but extracting the fields, matching against a purchase order, and delivering into the accounting system or ERP is the same process in both cases. Setting that process up now takes less effort than having to overhaul it all at once in 2028 or 2030. A consistent processing workflow also reduces the risk of errors precisely during the period when the document flow is most mixed. dottle processes incoming invoices regardless of format, from free-form PDF to structured Peppol XML, and delivers them into the system where the work happens. A person approves; dottle handles the reading and data entry.