Dutch e-invoicing: what is actually required?
The short answer is that no Dutch law requires B2B e-invoicing. What pushes you anyway sits elsewhere — with the public sector, across the border, and in European law that is already adopted.
Your dates
Two questions. Nothing is sent anywhere — the answer is computed in your browser.
What applies to you
Is a business reachable on Peppol?
A real lookup in the Peppol Directory — yours, a customer's, a supplier's. Enter an eight-digit Dutch Chamber of Commerce (KvK) number.
Nothing here requires you to be listed. The lookup is useful all the same: it tells you whether a customer or a supplier can already receive a structured invoice — and whether you can.
Two reservations, stated here rather than in the small print. The directory is not exhaustive: only participants who registered appear in it. And this lookup queries the KvK number (scheme 0106); a business registered under its VAT number instead will not surface. An absence is a signal, never a proof.
There is no Dutch B2B obligation — and that is the state of play
No statute, no bill before parliament. The government's business portal still describes a PDF by e-mail as normal practice, and states that the customer is not obliged to accept an e-invoice. A process is under way — the cabinet announced a public consultation for the fourth quarter of 2026. A consultation is not a law, and we draw no date from it.
What pushes you anyway: your customers across the border
Belgium has mandated B2B since 1 January 2026; Germany has mandated receiving since 1 January 2025 and issuing from 2027. A Belgian or German customer will ask for Peppol whatever Dutch law says. The obligation then comes not from the legislator but from your ledger.
Three routes to government, your choice
Peppol (directly or through a provider), a direct Digipoort connection for high volumes, or the supplier portal for manual entry. There is no state-accredited platform as in France, and no tax clearance. The formats are NLCIUS and Peppol BIS.
One obligation, five different laws
E-invoicing is being mandated country by country, and the gaps are wider than most groups expect. It is tempting to treat it as one project — pick a network, switch it on everywhere — and that is the assumption that produces rejected invoices in one country while another has not yet asked for anything. The four things that actually differ are the channel, the format, the date, and who is caught by it.
The clearest illustration is that two neighbouring countries can require opposite things. Belgium mandates a network: since January 2026 a domestic B2B invoice travels over Peppol, and the royal decree says so in its own text. Germany mandates a form and no network at all: since January 2025 every business must be able to receive a structured invoice, but the finance ministry is explicit that it may arrive by e-mail. France mandates neither in that sense — it built a state directory and a register of approved platforms, and an invoice must pass through one of them.
Peppol, and why it is not the whole story
Peppol is a shared addressing and transport network for business documents. Rather than each company agreeing a format with each customer, every participant registers an address and exchanges structured invoices through certified access points. An invoice sent over Peppol arrives as data your accounting system can read, not as a PDF someone has to re-type.
Being 'on Peppol' means two things: your identifier resolves to a registered address, and your software can produce and receive the structured format. Many companies discover they have the first without the second, because an integrator registered them during a pilot and nothing was connected afterwards.
What changes from country to country is what that registration is worth. In Belgium it is how you comply. In the Netherlands it is voluntary — nothing in Dutch law requires it, and a Dutch business typically joins because a Belgian or German customer asks. In Germany it is one delivery option among several and carries no legal weight of its own. And in France an entry in the state directory is not something you create yourself: your approved platform declares you, which is precisely why an absent entry is worth checking.
What this means inside Odoo
Odoo acts as a Peppol access point, and it is registered on the French tax authority's list of approved platforms — since 15 April 2026, on the official list published on 19 August 2026, the same list the French tool on this site searches. That covers the two mechanisms that need an intermediary; the German requirement, being a format rather than a channel, is a question of what your invoices contain rather than how they travel.
The work is rarely the connection itself — it is the data behind it: customer records without valid VAT or registration numbers, product lines without the tax mapping the format requires, and journals that were never set up to keep structured invoices for the statutory retention period. A missing tax mapping does not produce a visible error on your side; it produces an invoice rejected at the network level that never reaches your customer.
Our usual sequence is to clean the partner and tax data first, register the addresses second, and only then switch the outbound flow. Doing it in the other order produces a queue no one can unblock at month end — and it tends to surface in the week the obligation starts, which is the worst possible week to discover it.
Not for business-to-business. There is no statute and no bill before parliament. The government's own business portal still describes a PDF by e-mail as normal practice and states that your customer is not obliged to accept an e-invoice. Invoicing central government is the exception: that has been mandatory since 1 January 2017.
For cross-border trade it is real, and it is not a Dutch plan but adopted European law: Directive (EU) 2025/516 makes digital reporting and structured e-invoicing mandatory for intra-EU B2B from 1 July 2030. For purely domestic invoices there is only an announced public consultation. A consultation is not a law, and we draw no date from it.
Contractually yes, legally no. Belgium has mandated B2B since 1 January 2026 and Germany has mandated receiving since 2025 — your customer carries an obligation of their own and will pass it on. The pressure then comes not from the legislator but from your ledger, which in practice moves faster.