Electronic invoice in Netherlands

Mature ecosystem with dual channels via Peppol and Digipoort

Select a country

Overview

The Netherlands has one of Europe's most mature e-invoicing infrastructures and one of its narrowest mandates. Central government suppliers have had to invoice electronically since 2017, and every contracting authority has had to be able to receive EN 16931 invoices since 2019. Beyond that, nothing is compulsory: no domestic B2B mandate, no B2C mandate, no clearance and no invoice-level real-time reporting.

That may be about to change, and the country is at an unusually specific point in the process. A government-commissioned study recommends extending e-invoicing to domestic B2B; the government's response of 10 March 2026 confirmed a political decision was still being prepared; and a public consultation on draft legislation is planned for the fourth quarter of 2026. See The decision still pending.

0106 · 0190 · 9944

KvK, OIN and VAT — at least one of the three must be registered per client

NLCIUS

the national CIUS — receivers must be registered for SI-UBL 2.0 as a minimum

7 years

retention, rising to 10 for immovable property — and in the original form

Timeline

The Dutch B2G milestones are long settled. Everything genuinely uncertain sits in the next eighteen months.

Already in force

1 January 2011

Central government becomes able to receive e-invoices

Central bodies must be able to receive and process e-invoices through the government infrastructure — a capability obligation, well ahead of the European timetable.

1 January 2017

E-invoicing becomes mandatory for central government suppliers

Compulsory under new central government procurement contracts. This is the Dutch supplier-side mandate, and it has not been widened since.

18 April 2019

All contracting authorities must receive EN 16931 invoices

Ministries, municipalities, provinces, water boards and other contracting authorities under the procurement rules. A duty to receive — not a duty on their suppliers to send.

10 March 2026

The government responds on domestic B2B

The response confirms the political decision is still being prepared and that a draft law will go to public consultation in the fourth quarter of 2026.

Still ahead

Q4 2026 — planned

Public consultation on draft legislation

The first moment at which the shape of any Dutch domestic mandate becomes visible in legal text rather than in advice.

1 July 2030

ViDA digital reporting for intra-EU B2B

Structured e-invoices and transaction-level digital reporting for the cross-border transactions in scope. EU law, and the one fixed date here. See ViDA and 2030.

1 January 2035

Alignment of existing national reporting systems

Existing transaction-based reporting systems must be aligned with the ViDA model. This is not a separate deadline for mandatory Dutch domestic B2B e-invoicing.

The decision still pending

The Netherlands has not yet chosen between two paths, and almost every published Dutch roadmap blurs the difference:

The narrow option

Obligation limited to cross-border intra-EU B2B and certain reverse-charge transactions — the minimum ViDA requires, and nothing more.

The broad option

E-invoicing, and possibly digital reporting, extended to domestic B2B transactions as well.

The government-commissioned study recommends the broad model, and sketches a phased scenario: domestic B2B e-invoicing from 1 January 2030, intra-EU e-invoicing and reporting from 1 July 2030, and domestic digital reporting somewhere between January and October 2032.

2030 and 2032 are a consultant's recommendation, not a government schedule. Neither date has been adopted, and roadmaps that present "Netherlands: domestic B2B from 2030" as settled are quoting advice as if it were law. The only date the government itself has committed to is the Q4 2026 consultation.

Six things remain undecided even if the broad option is chosen: the date, which taxpayers are covered, whether small businesses are exempt, whether Peppol becomes compulsory, the reporting architecture, and whether domestic reporting starts at the same time as domestic e-invoicing. That is a lot of unresolved design for a system some suppliers are already being sold against.

Who is in scope

Central government suppliersMust send e-invoices under new central government procurement contracts

All contracting authoritiesMust be able to receive and process EN 16931 invoices

Suppliers to municipalities and provincesNo general obligation. It depends on whether the procurement or contract terms impose one

Domestic B2BNo mandate. Paper, PDF, EDI, Peppol or anything else the parties agree

B2CNo mandate. In most consumer sales a full VAT invoice is not required at all, subject to exceptions

The distinction to hold on to for sub-central government: a municipality must be able to receive a structured invoice, but it is not obliged to require one from every supplier. Whether you must send an e-invoice to a Dutch municipality is a question about your contract, not about Dutch law.

B2G and the channels

Peppol is officially the preferred channel, but it is not the only permitted one. Central government supports three routes, and knowing which a particular buyer uses saves a rejected invoice.

PeppolThe recommended channel, and the one that scales. All public organisations are connected directly or indirectly

DigipoortThe government gateway operated by Logius — a direct technical connection, used by high-volume suppliers

Supplier portalManual web entry, for low-volume suppliers without a system

A PDF attached to an email is none of these. Central government bodies state plainly that a PDF or email invoice is not an e-invoice and will be returned to the sender — which in practice means the payment clock has not started and nobody has told you.

B2B and B2C

Domestic B2B is unregulated as to format. A structured e-invoice is not required, the parties may use paper, PDF, EDI, Peppol or another agreed method, and there are no continuous transaction control or real-time reporting requirements. What is required for a digital invoice is the buyer's agreement, plus authenticity of origin, integrity of content and legibility across the retention period.

Intra-EU B2B before 2030

No Dutch structured-invoice mandate. Ordinary VAT invoicing rules apply, including the additional content for intra-Community supplies, both VAT identification numbers, reverse charge references and the associated VAT and ICP reporting. The invoice may be paper or digital, with the recipient's agreement still needed for the digital form.

Exports outside the EU

Exporting to a third country does not bring a transaction into the intra-EU ViDA reporting regime. ViDA creates no European requirement to send a structured e-invoice to a buyer in, say, the United States, the United Kingdom, Switzerland or the UAE. What does apply is Dutch export evidence and zero-rating rules, the buyer's country requirements, the contract, and any VAT or GST registration the supplier has in the destination country.

B2C

No obligation to issue structured e-invoices to consumers, and in most sales to private individuals a Dutch seller need not issue a full VAT invoice at all. The ViDA changes on OSS, IOSS, platforms and single VAT registration are separate tax mechanisms — they do not turn a consumer receipt into a mandatory Peppol document.

The model

There is no continuous transaction control system for commercial invoices in the Netherlands today.

No obligation to transmit every invoice to the Belastingdienst

No clearance requiring prior tax authority approval

No mandatory invoice-level real-time reporting

The tax authority is not a participant in the current exchange chain

Peppol runs as the standard decentralised four-corner model: sender, sender's Access Point, receiver's Access Point, receiver. For invoices to public bodies, Peppol can interoperate with Digipoort — but that is routing and technical processing, not tax clearance. Current digital tax reporting works through returns filed via software, tax intermediaries or the Mijn Belastingdienst Zakelijk portal, which is nothing like per-transaction transmission.

The government study is explicit that ViDA reporting is not clearance, and concludes that a classic model in which an invoice must first be authorised by a state portal does not fit the future European design. Exchange can stay decentralised while tax reporting runs as a separate parallel flow. Calling the future Dutch system "five-corner-like" is fair shorthand; calling the Belastingdienst a gatekeeper for every invoice is not.

Formats and PDF

The Dutch national Core Invoice Usage Specification is NLCIUS. It sets UBL 2.1 as the preferred syntax, treats UN/CEFACT XML CII D16B as permitted but not recommended, and adds national rules on how EN 16931 elements are used.

SI-UBL 2.0 / NLCIUSThe domestic profile. Dutch Access Points must register invoice receivers for at least this document type

Peppol BIS Billing 3.0Common for international exchange, and usable domestically too. Also UBL 2.1 syntax

UBL-OHNLGovernment procurement messages through Digipoort

SETU XMLTemporary staffing and HR processes

NLCIUS extensionsSector-specific additions such as the G-account extension

Where the PDF sits

Distinguish a digital invoice from a structured one. In domestic B2B a PDF is a perfectly lawful digital invoice, provided the buyer agrees to receive digital invoices and authenticity, integrity and legibility are ensured throughout the retention period.

In B2G it is not: a PDF file, or a PDF in an email, is not a structured e-invoice and will be returned. And from 1 July 2030 an ordinary PDF without a structured data set will not meet the ViDA requirements for the transactions in scope. For transactions outside the reporting requirements, national law could still permit hybrid formats — but the Netherlands has not decided that either.

Identifiers

The Netherlands has more identifier schemes in play than most countries, and the national requirements say something specific about which ones count.

0106NL:KVK — Chamber of Commerce number, eight digits. The most common identifier for an ordinary Dutch company

0190NL:OIN — Organisation Identification Number for public bodies, twenty digits. Central government, municipalities and provinces must be registered on this at minimum

9944NL:VAT — the Dutch VAT identification number

0217KvK establishment number for an individual branch, twelve digits

0088GLN, and an IBAN-based scheme in exceptional cases

Under the Dutch national requirements a service provider must register a client on at least one of KvK (0106), OIN (0190) or VAT (9944). Only where none of those is objectively available may another supported identifier such as GLN or IBAN be used. So "we address everyone by VAT number" is permitted, but it is the least universal of the three — the KvK number is what an ordinary Dutch business actually has.

Peppol and the NPa

The Netherlands Peppol Authority (NPa) acts on behalf of the Ministry of the Interior and Kingdom Relations (Ministerie van Binnenlandse Zaken en Koninkrijksrelaties, BZK). It governs the national part of the Peppol trust framework, the quality and reliability of the network, the national requirements for service providers, supervision of those providers, national formats and rules, and monitoring of Access Point availability. The Netherlands Authority for Digital Infrastructure (Rijksinspectie Digitale Infrastructuur, RDI) is also involved in enforcement.

Peppol is the strategic and preferred network, and every public organisation is reachable on it. But the NPa states that no decision has been taken to make Peppol the compulsory channel for the whole Dutch market. Digipoort, the government portal and, in some cases, XML by email remain in use for B2G.

Requirements for providers

The Dutch national requirements state Service Provider Accreditation: No — there is no separate Dutch licence comparable to the Slovak digitálny poštár. That absence is easy to misread. There is no accreditation, but there are Dutch national requirements, and they are more detailed than most.

Serving Dutch clients from abroad

A provider established in another EU country can onboard Dutch clients directly, provided it is an OpenPeppol member, holds a valid agreement with its home Peppol Authority (or with OpenPeppol where that country has none), complies with the Dutch national requirements, and supplies the NPa with the documents and technical information it asks for. The NPa is explicit that a foreign provider does not sign a separate principal Service Provider Agreement with it merely because it serves Dutch clients — the agreement stays with the authority of the country where the provider is established.

No Dutch legal entity, branch or permanent establishment required

No local tax representative solely for Peppol purposes, no local official mailbox, no local director or owner

No requirement for a Dutch-located server

What is actually required

Information securityAn ISO/IEC 27001 certificate covering the Peppol services, or — as an interim equivalent — a Third Party Memorandum from an independent registered IT auditor. OpenPeppol's global deadline for mandatory ISO/IEC 27001 accreditation is 1 October 2027

End User IdentificationIdentify the end user before connecting, verify that its identifiers are valid and active, re-assess at least annually, and provide the NPa with a description of the process

TechnicalProvide an endpoint URL for service-level monitoring, maintain the required availability, support AS4, validate Peppol PKI certificates correctly, support large file transfers in testing, and meet the applicable OpenPeppol reporting mechanism

Formats and SMPRegister invoice receivers for NLCIUS / SI-UBL 2.0. No dummy or test Peppol IDs in production, and every Peppol ID must correspond to a real, active end user

Client migrationOn a client moving away, the previous provider must assist the transfer or remove the SMP registration within three working days

Holding ISO 27001 does not exclude further checks by the NPa or the RDI, because part of the national conditions is not covered by the certificate itself. The Netherlands is, in short, a market with no licence and real supervision — which is a more demanding combination than it first sounds.

Two operational habits worth building

The NPa publishes validation artefacts for SI-UBL 2 (NLCIUS) and Peppol BIS 3 on a roughly six-monthly cycle — a May and a November release — so keeping validation current is a scheduled task rather than a one-off implementation. And in February 2026 the NPa flagged that existing Peppol PKI certificates become invalid following a platform change at OpenPeppol and must be replaced. Certificate lifecycle is not something to discover on the day a send starts failing.

ViDA and 2030

From 1 July 2030, the intra-EU transactions in scope require a structured e-invoice conforming to the European standard, with invoice-level digital reporting. On the current reading of the rules:

—The e-invoice must be issued within ten days of the taxable event

—The supplier reports at the moment the invoice is issued, or when it should have been issued

—The buyer reports the corresponding data within five days — unless the member state uses the applicable opt-out for intra-Community acquisitions

—The five-day rule also applies to self-billing

—Data goes to the tax administration of the state whose VAT identification number is used, and is exchanged between states through a modernised VIES

—The buyer loses the right to demand paper or a PDF instead of an e-invoice

Scope matters more than people assume: ViDA reaches intra-Community supplies, intra-Community acquisitions and certain reverse-charge B2B transactions under Articles 194–197 of the VAT Directive. Not every international transaction is automatically in the reporting regime — you have to establish the VAT treatment and the specific ViDA provision before concluding that it is.

Consequences and VAT deduction

No single fixed administrative penalty was identified for a supplier sending a PDF instead of a structured B2G e-invoice. The consequences today are practical: the invoice is returned or rejected, it is not taken into processing, payment is delayed until a correct document arrives, and there may be consequences under the procurement contract. The Ministry of Justice and Security, for example, states directly that a PDF or email is not an e-invoice and will be returned.

For municipal buyers the consequences depend on the contract, since they may — but need not — impose an e-invoicing requirement on suppliers.

Future ViDA sanctions

Dutch penalties for breaching the 2030 requirements do not yet exist, because the national implementing legislation has not been adopted. They will presumably attach to failing to issue a required e-invoice, issuing it late, reporting late, incomplete or inaccurate data and format breaches — but the amounts, exemptions, any grace period and the correction procedure all have to come from Dutch law. General penalties for incorrect VAT returns already exist; they are not e-invoicing penalties.

VAT deduction

Currently a structured Peppol e-invoice is not the only admissible document for deducting VAT. The Belastingdienst accepts paper and digital invoices; for a digital document what matters is the recipient's agreement, authenticity of origin, integrity and legibility. Input VAT is normally deducted on the basis of the invoice received and only once it has been received, though the rules allow special and simplified documents in defined cases such as certain fuel receipts.

ViDA does give member states scope to link deduction to receipt of a correct e-invoice, and the government study notes that legal possibility. The Netherlands has not decided to use it. So it cannot be asserted that from 2030 the e-invoice necessarily becomes the only basis for domestic VAT deduction.

Archiving

Invoices sent and received must be retained for seven years, extending to ten years for data on immovable property and rights to immovable property.

Invoices must be kept in the form in which they were sent or received. A digital invoice should not be printed and filed as paper — it is retained digitally

Paper invoices may be scanned for digital storage, provided the reproduction is accurate and complete and the authenticity features are saved too

Where the invoice was structured, keep the XML — the rendered visualisation is not the invoice, and printing it is exactly the failure the rule is aimed at

This is one of the cleaner archiving regimes in Europe to comply with and one of the easiest to breach by habit. The most common failure is not a missing record but the wrong form of one: a PDF print of an XML that was never kept.

How we help

The Netherlands needs no licence but does have real national requirements — and a decision arriving in the next few months:

NLCIUS / SI-UBL 2.0 support with correct SMP registration, alongside Peppol BIS Billing 3.0 for international traffic

Addressing on 0106, 0190 and 9944, with OIN used for public bodies rather than guessed

Delivery to central government through Peppol, and awareness of the Digipoort and portal alternatives where a buyer expects them

End User Identification run as a documented, annually re-assessed process rather than a one-off onboarding check

Clean SMP hygiene — real active participants only, and prompt handling when a client migrates

Archiving that keeps the original XML in its original form, not a printed rendition

Preparation for the intra-EU ViDA requirements, including the ten-day issuance rule and the reporting timing

Connection by API, SFTP and CSV, with ERP and IDoc source data

Frequently asked questions

Is e-invoicing mandatory in the Netherlands?

Only towards central government, where it is compulsory under new procurement contracts since 1 January 2017. All contracting authorities have had to be able to receive EN 16931 invoices since 18 April 2019, but that is a duty to receive rather than a duty on suppliers to send. There is no domestic B2B mandate and no B2C mandate.

Is a Dutch B2B mandate coming in 2030?

Not decided. A government-commissioned study recommends extending e-invoicing to domestic B2B, sketching domestic e-invoicing from 1 January 2030 and domestic digital reporting between January and October 2032 — but those are the consultant's recommendations, not adopted policy. The government's response of 10 March 2026 confirmed the political decision was still being prepared, with a draft law going to public consultation in Q4 2026. The date, the taxpayers covered, small-business exemptions, whether Peppol becomes compulsory and the reporting architecture are all still open.

Do I have to send an e-invoice to a Dutch municipality?

Not by general law. Municipalities, provinces and water boards must be able to receive EN 16931 invoices, but they are not obliged to require them from every supplier. Whether you must send one depends on the procurement or contract terms — so read those rather than assuming either way. For central government under a new contract, the answer is yes.

Can I send a PDF invoice?

In domestic B2B, yes — a PDF is a lawful digital invoice where the buyer agrees to receive digital invoices and authenticity of origin, integrity of content and legibility are ensured for the retention period. In B2G, no: a PDF file or a PDF in an email is not a structured e-invoice and central government bodies state it will be returned to the sender. From 1 July 2030 a plain PDF will not meet the ViDA requirements for the transactions in scope.

Which identifier should I register for a Dutch client?

At least one of KvK (0106), OIN (0190) or VAT (9944) — the Dutch national requirements say so explicitly. Only where none of the three is objectively available may another supported identifier such as GLN (0088) or an IBAN scheme be used. Central government bodies, municipalities and provinces must be registered on OIN 0190 at minimum. For an ordinary Dutch company the KvK number is the most common choice; the establishment number 0217 identifies a specific branch.

Does a foreign Access Point need Dutch accreditation?

No — the Dutch national requirements state "Service Provider Accreditation: No", and there is no local entity, branch, tax representative, mailbox, local director or Dutch server requirement. But the national requirements themselves still apply. A provider established elsewhere keeps its agreement with its home Peppol Authority (or with OpenPeppol where there is none), complies with the Dutch requirements, and supplies the NPa with the documents and technical information it requests. No separate principal agreement is signed with the NPa just because you serve Dutch clients.

What do the Dutch national requirements actually demand?

Information security through ISO/IEC 27001 covering the Peppol services, or an interim Third Party Memorandum from an independent registered IT auditor — with OpenPeppol's global deadline for mandatory ISO/IEC 27001 accreditation set at 1 October 2027. End User Identification before connecting, with verification that identifiers are valid and active, annual re-assessment and a process description given to the NPa. Technically: an endpoint URL for monitoring, required availability, AS4, correct Peppol PKI validation and large-file support. Receivers registered for NLCIUS / SI-UBL 2.0, no dummy or test IDs in production, and on client migration the previous provider assists or removes the SMP registration within three working days.

Does the Netherlands have clearance or real-time reporting?

Neither. There is no obligation to transmit every invoice to the Belastingdienst, no prior approval, no invoice-level real-time reporting, and the tax authority is not part of the exchange chain. Peppol runs as a standard four-corner model, and where it interoperates with Digipoort for public sector invoices that is routing and technical processing, not tax clearance. Current digital tax reporting is return-based, filed via software, intermediaries or the Mijn Belastingdienst Zakelijk portal.

What changes for cross-border invoicing in 2030?

For the intra-EU transactions in scope: a structured e-invoice conforming to the European standard, issued within ten days of the taxable event, with the supplier reporting at issuance and the buyer within five days unless the member state uses the opt-out for intra-Community acquisitions. Self-billing follows the five-day rule. Data goes to the tax administration of the state whose VAT number is used and is exchanged through a modernised VIES, and the buyer loses the right to demand paper or PDF instead. Scope covers intra-Community supplies and acquisitions and certain reverse-charge transactions under Articles 194–197 — not every international transaction.

How long must invoices be kept, and in what form?

Seven years, extending to ten years for data on immovable property and rights to immovable property. Crucially, invoices must be retained in the form in which they were sent or received — a digital invoice is stored digitally, not printed. Paper invoices may be scanned for digital storage provided the reproduction is accurate and complete and the authenticity features are saved as well. Where the invoice was structured, keep the XML rather than a rendered copy.

Summary

The Netherlands runs excellent infrastructure under a modest mandate. Central government suppliers must invoice electronically, every contracting authority must be able to receive, and nothing else is compulsory — no domestic B2B or B2C obligation, no clearance, no real-time reporting. Peppol is the preferred network without being the only permitted one.

Technically the country is specific rather than difficult: NLCIUS with SI-UBL 2.0 as the registration minimum, UBL 2.1 preferred over CII, three identifier schemes of which at least one must be used, and detailed national requirements on security, end user identification, SMP hygiene and client migration — enforced without an accreditation regime.

The genuinely open question is whether the Netherlands takes the narrow ViDA route or extends the obligation to domestic B2B. The advice says extend; the government has not said. The first honest answer arrives with the Q4 2026 consultation — and anything published before then that gives a Dutch domestic date is quoting a recommendation, not a law.

Resources

Netherlands Peppol Authority (NPa) The national requirements for service providers, the format rules and the position on whether Peppol becomes compulsory NPa — technical specifications Where the SI-UBL 2 (NLCIUS) and Peppol BIS 3 validation artefacts are published, twice a year NPa — registering as a service provider The procedure, and the documents the NPa expects from a provider serving Dutch end users Logius — e-invoicing to the government The three B2G channels — Peppol, Digipoort and the supplier portal — and the historical B2G milestones Belastingdienst — retaining your invoices The seven-year rule, the ten-year exception, and the requirement to keep invoices in their original form Belastingdienst — how long to keep your administration Seven or ten years, and what falls into each category European Commission — eInvoicing in the Netherlands The country profile: transposition, NLCIUS, the Peppol-based approach and the absence of real-time reporting Peppol BIS Billing 3.0 The international profile used alongside the Dutch NLCIUS / SI-UBL 2.0 Peppol Electronic Address Scheme code list Where 0106, 0190, 0217 and 9944 sit, alongside every other scheme you may need European Commission — VAT in the Digital Age (ViDA) The 1 July 2030 requirements, the ten-day issuance rule and the scope that decides which transactions are caught Peppol Directory Confirm a Dutch participant is reachable, and on which of the identifier schemes

Need support with e-invoicing compliance?

As a certified Peppol Access Point we provide solutions for sending and receiving electronic invoices securely across Europe — including format conversion, validation and integration with national systems.

Start your free trial