Peppol in the Netherlands: what Shopify merchants need to know
Last updated 26 August 2026 · dates and requirements checked against primary sources on 26 August 2026
The Netherlands is one of the quieter e-invoicing stories in Europe, and one of the most instructive. There is no Dutch B2B mandate — no 2027 deadline of the sort Germany has legislated. Yet Dutch businesses have been sending structured e-invoices over Peppol for years, because the government required it and the market followed. If you sell B2B from Shopify to Dutch companies, the pressure to send a real e-invoice will come from your buyers, not from a law.
The short version
Where the obligation actually sits
The Dutch rules start with public procurement. Since 1 January 2017, businesses supplying Dutch central government have had to send structured e-invoices rather than PDFs, and the wider public sector was brought into line under the EU directive on e-invoicing in public procurement (2014/55/EU), which obliged public bodies across the EU to receive EN 16931-compliant invoices.
For everything else — one company invoicing another — Dutch law leaves it to the parties. An e-invoice is permitted and encouraged; a PDF is still legally acceptable, provided the invoice content meets normal Dutch VAT requirements. That is the key difference from Germany, and the reason the Netherlands is often misdescribed as "already mandatory".
Why Dutch buyers ask for Peppol anyway
The Netherlands was an early and enthusiastic Peppol adopter, with its own Peppol authority overseeing the network domestically. That has three practical consequences for a merchant:
- Your buyer is probably already on it. Companies that supply government had to get onto structured invoicing years ago, and kept using it for their commercial invoices too.
- Their accounting software expects it. Dutch bookkeeping packages read Peppol invoices directly into the ledger — no typing, no scanning. A PDF from your store creates manual work for them.
- It is asked for at onboarding. "Can you invoice via Peppol?" turns up in supplier forms well before any legal deadline would have forced it.
So the Dutch market rewards capability rather than punishing its absence. That is a softer pressure than a mandate, but it shows up in the same place: whether you win the B2B account.
The formats: EN 16931, NLCIUS and Peppol BIS
A Dutch e-invoice is a structured UBL document built on the European standard EN 16931. Two profiles matter:
| Name | What it is | When you meet it |
|---|---|---|
| NLCIUS | The Dutch national specification of EN 16931 — a "CIUS" that pins down how Dutch-specific fields are used. | Domestic Dutch invoicing, and anything going to Dutch public bodies. |
| Peppol BIS Billing 3.0 | The pan-European Peppol profile of the same EN 16931 standard. | The profile that actually travels the Peppol network, at home and cross-border. |
They are compatible relatives, not rivals — both are EN 16931 underneath. If your invoices are generated against EN 16931 correctly, you are in the right territory for the Netherlands, Germany, and the rest of the EU wave behind them.
Dutch Peppol IDs: KvK, VAT and OIN
You cannot send a Peppol invoice to a company name. You need its participant identifier — a scheme code plus a number — and it has to be registered on the network to receive. In the Netherlands you will run into three:
| Scheme | Identifier | Used by |
|---|---|---|
| 0106 | KvK number (Chamber of Commerce registration) | Dutch companies — the most common business identifier. |
| 9944 | Dutch VAT number (NL…B..) | Businesses identified by VAT, and the natural fit for cross-border B2B. |
| 0190 | OIN (Organisatie Identificatie Nummer) | Dutch government bodies and public organisations. |
Practically: capture the buyer's KvK number and VAT number at checkout for Dutch B2B orders. Those two fields are what let you address them on the network, and the VAT number is what you need for the tax treatment anyway.
What this means for a Shopify store
Shopify sells beautifully and invoices thinly. Its order confirmation is not an e-invoice: it cannot produce NLCIUS or Peppol BIS UBL, it has no concept of a Peppol ID, and it cannot transmit anything over a certified Access Point. To serve Dutch B2B buyers properly you need a layer that:
- collects company name, KvK and VAT number on B2B orders,
- turns the order into EN 16931-valid UBL, with the VAT worked out correctly,
- sends it over a certified Peppol Access Point, and
- keeps the signed receipt the receiving Access Point returns on handover.
The Dutch VAT details that break invoices
A Peppol invoice is validated on arrival, so arithmetic that "looks fine" on a PDF gets rejected here. Three things catch Dutch stores out. First, the standard Dutch VAT rate is 21%, with a reduced 9% rate for goods like food and books — a store mixing both must get the split right per line, not per order. Second, whether your Shopify prices include or exclude tax changes how net and VAT are derived, and rounding at the wrong step leaves you a cent out — enough to fail validation. Third, selling to a VAT-registered business in another EU country is usually reverse charge: 0% VAT, the buyer's VAT number validated against VIES, and the correct legal note on the invoice. Getting onto the network is the easy half; the numbers have to be right.
What's coming, and why it matters here
No Dutch B2B mandate is in force, but one is now being prepared. On 10 March 2026 the State Secretary for Finance sent Parliament an analysis of the options, and the cabinet reply pointed at the broadest of them: compulsory e-invoicing for all domestic Dutch B2B transactions, carried over Peppol rather than a central clearance platform, phased in between 2030 and 2032. A definitive cabinet position was expected in the summer of 2026 and a draft bill is due to go out for internet consultation in the fourth quarter of 2026, with the law itself not expected to be settled until around mid-2028. None of that is law yet, so treat 2030 as the direction of travel rather than a date to diary. Under ViDA, structured e-invoicing and digital reporting for intra-EU cross-border B2B arrives at EU level from 1 July 2030 in any case, and member states are free to mandate domestically before then. Meanwhile Germany's mandate phases in across 2027–2028. If you sell to both Dutch and German businesses — a very ordinary combination — the German deadline is what forces your hand, and the Dutch market is where the capability immediately pays for itself.
The Netherlands has no B2B mandate, and several of its neighbours now do. The EU e-invoicing mandate table shows which ones, from when, and what each runs on.
Frequently asked questions
Is e-invoicing mandatory in the Netherlands?
Only towards the government. Suppliers to Dutch central government have had to send structured e-invoices since 1 January 2017, and the wider public sector followed under EU directive 2014/55/EU. B2B invoicing is not mandated today: there is no Dutch equivalent of Germany's 2027 to 2028 obligation. One is in preparation, aimed at all domestic B2B invoicing over Peppol between 2030 and 2032, with a draft bill due for consultation late in 2026.
What is NLCIUS?
The Dutch national specification of the European standard EN 16931 — a Core Invoice Usage Specification that pins down how Dutch-specific details are filled in. A Dutch e-invoice is normally UBL following NLCIUS or the Peppol BIS Billing 3.0 profile.
What is a Dutch Peppol ID?
A scheme plus a number that addresses a business on the network. Dutch companies are commonly identified by KvK number (scheme 0106) or VAT number (scheme 9944); government bodies use an OIN (scheme 0190). The identifier must be registered to receive before you can invoice it.
Do I have to send Peppol invoices to Dutch B2B customers?
Not by law. But the Netherlands is a mature Peppol market and many buyers — especially larger ones and anyone who also supplies government — expect it. In practice it is a commercial requirement well before it is a legal one.
Can Shopify send a Dutch e-invoice on its own?
No. Shopify's order confirmation isn't a structured e-invoice: no NLCIUS/EN 16931 UBL, no Peppol ID handling, no Access Point connection. That layer is added with an app or service.
How does this compare with Germany's 2027 mandate?
Opposite ends of the same road. Germany is legislating compulsory B2B e-invoicing phasing in from 2027 to 2028; the Netherlands has no B2B mandate but very high voluntary adoption. Selling into both takes the same capability either way.
This guide is general information for Shopify merchants, not legal or tax advice. Rules, mandates and thresholds vary by country and change over time — confirm your obligations with a qualified tax adviser.
E-invoices from your Shopify B2B orders
Zeppol turns every B2B order into an EN 16931 document, checks it against the EU and the German rules, and sends it over Peppol or by email. Join the list and I'll be in touch before the deadline.