In the Netherlands, e-invoicing is mandatory today for suppliers to the Dutch central government, and other public authorities can require it through procurement or contract terms. Ordinary B2B invoicing is not yet mandatory. That is set to change. On 11 September 2026 the Dutch cabinet decided to introduce e-invoicing and digital reporting for businesses: e-invoices become mandatory for domestic and intra-EU B2B transactions from 1 July 2030, digital reporting of domestic invoices to the Belastingdienst follows from 1 July 2031, and small businesses in the KOR scheme are exempt from the domestic obligation. The plan is not yet law, and the bill is due in parliament before summer 2027. Depending on the recipient and route, the main Dutch terms readers will encounter today are NLCIUS, SI-UBL 2.0, Peppol BIS Billing 3.0, and Digipoort, with the European standard EN 16931 as the single standard for the 2030 obligation.
The first distinction for Dutch compliance is between a structured e-invoice and a PDF invoice. A structured e-invoice contains invoice data in a machine-readable standard that can be validated and routed automatically. A PDF attached to an email may be digital, but it is still a document that a person or downstream system has to read and interpret. That difference matters because Dutch mandate discussions are about structured exchange, not about whether an invoice was sent electronically in a loose sense.
Until 2030, the Dutch position is narrower than headlines about the cabinet's decision suggest. Central-government suppliers need to comply now. Other public-sector bodies may impose structured e-invoicing through their own procurement terms. In B2B trade, the question until the obligation starts is whether the recipient agrees to receive an e-invoice and which format that recipient expects. B2C is simpler: there is no Dutch e-invoicing mandate for invoices to consumers, and the 2030 plan covers business-to-business transactions only.
As Business.gov.nl's Dutch invoice requirements guide explains, in the Netherlands customers must agree to accept an e-invoice, and accepting e-invoices is not mandatory unless the work is for the Dutch central government. That remains the practical baseline for finance teams until the 2030 obligation applies: start by identifying whether the invoice is going to central government, another public body with contract-specific rules, or an ordinary business counterparty.
The Dutch Timeline Is Easier to Read When You Separate 2017, 2019, 2030, and 2031
Many summaries of Dutch e-invoicing compress several dates into one story, which makes the rules look broader or more settled than they are. The cleaner way to read the Netherlands is to separate the date that made e-invoicing operationally mandatory for central-government suppliers, the later EU public-procurement backdrop, and the two planned dates that bring business-to-business trade in.
1 January 2017 is the practical starting point for mandatory Dutch B2G e-invoicing. If a supplier invoices the Dutch central government, the expectation is no longer a PDF-by-email workflow. The invoice needs to meet the relevant structured route and format requirements for that public-sector relationship.
18 April 2019 matters mainly because public authorities across the EU framework had to be able to receive and process compliant electronic invoices. It should not be read as proof that every Dutch public-sector transaction suddenly followed one identical supplier mandate from that date onward. In practice, readers still need to distinguish central government from other authorities and then confirm the specific procurement terms attached to the invoice flow.
1 July 2030 is when ViDA, the EU's VAT in the Digital Age package, requires e-invoices and per-transaction digital reporting for cross-border B2B trade within the EU, with invoices for that trade issued within 10 days of the supply. The cabinet's September 2026 decision extends the e-invoicing obligation to domestic B2B invoices from the same date, and requires reporting of intra-Community acquisitions from then as well.
1 July 2031 is the planned start of digital reporting for domestic B2B transactions. Businesses will report a selection of data fields from the domestic e-invoices they send to the Belastingdienst, limited to the subset of fields used at EU level.
Neither domestic date is law yet. The cabinet intends to put a draft bill out for internet consultation in autumn 2026, submit it to the House of Representatives before the 2027 summer recess, and complete the parliamentary process before 1 July 2028, two years before the obligation starts. Groups operating across Benelux often compare Dutch planning with Belgium e-invoicing requirements, where a domestic B2B mandate has applied since 1 January 2026 and the Dutch equivalent is still waiting for its law.
Which Dutch Rules Apply to B2G, B2B, and B2C Transactions
The fastest way to classify a Dutch invoice flow is to ask who the recipient is. The legal and operational answer changes much more by transaction type than by the fact that the invoice is electronic.
| Transaction type | Current Dutch position | From 1 July 2030 (planned) | Practical takeaway |
|---|---|---|---|
| B2G | Central-government suppliers must send e-invoices now. Other public authorities may require them through procurement terms or contract conditions. | Unchanged by the 2030 plan. | Confirm the exact recipient requirement before issuing the invoice. |
| B2B | Structured e-invoicing is voluntary until the 2030 obligation and usually depends on recipient agreement. | Mandatory for domestic and intra-EU invoices in the EN 16931 standard. KOR businesses are exempt from the domestic obligation. | Ask what format and channel the customer accepts now, and plan for EN 16931 invoicing by 2030. |
| B2C | No e-invoicing mandate for invoices to consumers. | No obligation. The plan covers B2B only. | Ordinary invoicing and tax compliance rules still matter, but the structured e-invoicing pressure is far lower. |
For overseas suppliers, the most important point is that Dutch public-sector exposure changes the analysis immediately. A foreign company billing a Dutch ministry or central-government entity should not assume that a normal PDF workflow is acceptable just because domestic Dutch B2B trade is voluntary until 2030. Public-sector recipient requirements override that assumption.
For Dutch businesses selling to other businesses, recipient agreement remains central until 1 July 2030. A buyer may prefer or require a structured format for efficiency, but no nationwide rule yet says every domestic B2B invoice must move that way. Businesses using the KOR small business VAT scheme, for turnover of up to EUR 20,000 a year, will have no domestic e-invoicing obligation under the plan, although digital reporting of intra-Community acquisitions can still apply to them. Sole traders and small businesses still need to meet the underlying invoicing rules even when structured exchange is not mandatory in every case. If the question is about what the invoice itself must contain, rather than which exchange format to use, the baseline rules are covered separately in our guide to Dutch freelancer invoice requirements.
How NLCIUS, SI-UBL 2.0, Peppol BIS Billing 3.0, and Digipoort Fit Together
Dutch e-invoicing terminology becomes much easier to handle once each label is assigned a job. The confusion in many country guides comes from treating standards, implementation profiles, and transmission channels as if they were interchangeable.
- NLCIUS is the Dutch Core Invoice Usage Specification layered onto the European EN 16931 model. It adapts the European invoice standard to Dutch government-oriented requirements.
- SI-UBL 2.0 is the Dutch implementation profile used domestically. In practice, it is the local UBL expression many finance teams and software providers encounter when they work with Dutch structured invoicing.
- Peppol BIS Billing 3.0 is the billing standard used on the Peppol network. It matters when invoices move through Peppol, especially in cross-border or network-based exchange scenarios.
- Digipoort is a government submission channel. It tells you how the invoice is delivered into a public-sector route, not by itself which document syntax sits inside the file.
The practical relationship is this: NLCIUS describes the Dutch requirements layered onto the European model, SI-UBL 2.0 expresses the Dutch implementation domestically, Peppol BIS Billing 3.0 governs invoices sent across the Peppol network, and Digipoort is one of the channels through which a compliant invoice may need to travel. A supplier does not always need to master every acronym separately, but the finance team does need to confirm which standard and route the recipient actually expects before going live.
The 2030 plan settles the standard for B2B but not the network. The cabinet chose the EU norm, EN 16931, as the only standard for domestic transactions, with no other standards alongside it. Which infrastructure will carry those invoices is still open. EY's study for the government advised prescribing Peppol between businesses, the network central-government suppliers already use, while the cabinet also wants to weigh the European Business Wallet now in development, and its September 2026 letter to parliament describes the infrastructure question as not yet ready for a decision.
What Finance Teams Need to Do in Practice, From Access Points to Mixed PDF Workflows
Once the recipient type is clear, Dutch compliance becomes a workflow design problem. The sender or AP team needs to confirm the required route, map the expected format, and test the invoice before treating the setup as production-ready.
- Confirm whether the recipient expects Digipoort, Peppol, or another contract-defined route.
- Check which identifier the recipient uses and whether a Peppol access point is needed to reach it.
- Validate the document format expected by that route, rather than assuming every electronic invoice can be reused unchanged.
- Test the exchange before production so rejection rules surface in a controlled setting instead of during live billing.
This is why Peppol can matter even when it is not described as universally mandatory across all Dutch invoicing. A company may not face a blanket national Peppol obligation, but it can still need Peppol in practice because a government body, trading partner, or service provider has standardized on that network for invoice delivery.
Preparing for 2030 is mostly a software question. Check that your invoicing and accounting software can issue and receive EN 16931 invoices, and treat the choice of network as open until the government decides it. Teams with cross-border EU sales also need billing that can issue those invoices within ViDA's 10-day window.
The other real-world challenge is mixed intake. Many finance teams have one queue receiving PDFs by email, another handling structured invoices from trading partners, and a growing need to keep both streams auditable. That usually means separating document capture from structured message handling inside broader invoice processing workflows, rather than pretending one rule covers every inbound invoice.
Where suppliers still email attachments, teams often need a parallel process to convert PDF invoices into structured e-invoices or extract their data for downstream systems. That is a different operational problem from receiving native Peppol or Dutch public-sector e-invoices, and treating those two paths separately makes Dutch compliance much easier to manage. Under the plan, PDF invoices between Dutch businesses stop being the norm from 1 July 2030, so for domestic suppliers the PDF stream is a transition problem with an end date, although invoices from KOR suppliers and from outside the EU may still arrive as PDFs.
A Short Checklist for Dutch and Cross-Border Compliance Teams
Use the Dutch rules in this order:
- Identify whether the invoice flow is B2G, B2B, or B2C before choosing a format or channel.
- Confirm the recipient's actual requirement, especially for Dutch central government bodies and other public authorities working through procurement terms.
- Match the invoice to the correct standard and route, whether that means a Dutch implementation profile, a Peppol exchange path, or a government submission channel.
- Test with the recipient or access point before production use so identifier, validation, and formatting issues are caught early.
- Plan for e-invoicing on domestic and intra-EU B2B invoices from 1 July 2030 and domestic digital reporting from 1 July 2031, alongside today's B2G rules.
- Track the internet consultation, the bill, and the network decision, because dates and details can still change before the law passes.