E-Invoicing in the Netherlands 2026: Peppol, ViDA Timeline, Formats and Compliance

Key Takeaways

• Public sector invoicing is already compulsory. Firms supplying the central government have had to send structured e-invoices since 1 January 2017, and every public body has had to be able to receive them since 18 April 2019.
• Business-to-business invoicing remains optional for now, requiring the recipient to agree, though take-up is exceptionally high thanks to Peppol support baked into most Dutch accounting and ERP tools.
• A national B2B requirement is on the drawing board but not in force. A March 2026 advisory study backs a Peppol-driven approach under ViDA, with a draft bill anticipated for consultation toward the end of 2026.
• One date is set in stone. From 1 July 2030, every EU member state must support structured e-invoicing and digital reporting for cross-border B2B trade.
• The national specification is NLCIUS, delivered as Peppol BIS Billing 3.0, written in UBL and conforming to the EN 16931 European norm, moving across the decentralized four-corner Peppol network.

Understanding e-invoicing in the Netherlands

An electronic invoice, in the legal sense, is one whose data is structured so machines can read, check, and post it without human re-keying. That definition rules out the everyday PDF attachment: however neat it looks on screen, the receiving system cannot interpret its contents automatically. This gap is precisely the job that purpose-built e-invoicing software for the Netherlands fills, generating and consuming the structured documents that PDFs and spreadsheets never could.

Few countries got there earlier. The Dutch were among Peppol's original architects, stood up a public-sector invoicing program well before most neighbors, and nurtured the Simplerinvoicing project that later hardened into the national format. That head start explains today's deep bench of certified Access Points and Peppol e-invoicing software, and it is the reason voluntary business adoption climbed so high without anyone being compelled.

Where things stand: enacted versus proposed

The defining feature of the Dutch landscape is the distance between what the law already demands and what policymakers merely intend. As of June 2026, the breakdown looks like this.

• Central government (B2G): In force. Suppliers must send structured e-invoices, mandatory since 1 January 2017.
• Wider public sector (B2G): Receipt is compulsory. All public authorities have had to accept e-invoices since 18 April 2019; whether a supplier must issue them depends on the contract.
• Domestic business trade (B2B): Optional. Allowed where the buyer consents, with no sanction for opting out. A mandate is proposed but unenacted.
• Cross-border EU trade (B2B): Compulsory from 2030. Required under EU ViDA from 1 July 2030, set by directive irrespective of Dutch domestic choices.
• Consumer sales (B2C): Excluded. Falls outside the e-invoicing regime entirely.

The legal and policy backdrop

Three layers shape Dutch e-invoicing: domestic statute, European directive, and an advisory blueprint not yet converted into law.

• The public-sector obligation flows from the law of 20 December 2017, which revised the Public Procurement Law 2012 and brought EU Directive 2014/55/EU into Dutch law. That is the source of the duty to invoice public bodies in structured form.
• The EU ViDA package compels structured e-invoicing and near-instant digital reporting for intra-EU B2B dealings from 1 July 2030. Being an EU obligation, it stands independent of whatever the Netherlands legislates at home.
• The home-grown roadmap emerged on 10 March 2026, when the State Secretary of Finance handed Parliament a report prepared by EY. It urges widening mandatory e-invoicing and digital reporting to cover all domestic B2B activity, with Peppol named as the backbone.

A point worth stressing: that March 2026 document is a recommendation, not a statute. Parliament has adopted no bill. The government has indicated it will declare its chosen path during summer 2026 and circulate draft legislation for feedback by year-end.

The proposal on the table: ViDA-A or ViDA-B

The crux of the Dutch decision is ambition. Brussels sets a baseline, and each country may build higher if it wishes.

• ViDA-A (the floor): Limited to cross-border intra-EU transactions and select reverse-charge supplies. Domestic invoicing largely untouched.
• ViDA-B (the recommendation): All of the above, plus compulsory e-invoicing and digital reporting for every domestic B2B transaction.
• The infrastructure question: A decentralized four-corner Peppol network, turning down both a French-style accredited-provider route and a centralized state platform.

EY's report lands firmly on ViDA-B, with Peppol as the one mandated infrastructure, on the grounds that it brings sharper standardization, smoother interoperability, lower costs over time, and tighter VAT enforcement. Such a move would put the Netherlands in step with Belgium, France, Germany, Italy, and Ireland, all of which pushed beyond the EU floor. The study also argues against a clearance system, meaning the tax authority would neither pre-approve nor gatekeep invoices before they change hands. Reporting would instead happen alongside the transaction, a continuous-control approach minus the clearance step.

The expected sequence of dates

Only two points on the Dutch calendar are guaranteed by EU law: the public-sector deadlines, long since passed, and the 1 July 2030 ViDA cross-border requirement. Everything domestic that follows hinges on legislation still to be written, so read the post-2026 entries as a projected path rather than fixed appointments.

• 1 January 2017: Public sector goes live. Central government suppliers must issue structured e-invoices through Peppol or Digipoort.
• 18 April 2019: Mandate widens. Municipalities, provinces, and water boards must be capable of receiving structured e-invoices.
• 10 March 2026: Report reaches Parliament. EY's study recommends a Peppol-based domestic B2B mandate in line with ViDA.
• Summer 2026: Cabinet declares its position. The government is due to settle on ViDA-A or ViDA-B.
• Late 2026: Draft law opens for consultation. Stakeholders are expected to be invited to comment on the proposed framework.
• Mid-2028: Legislation completed (projected). A roughly two-year run-up would then allow businesses to adapt their systems.
• 1 July 2030: ViDA cross-border rule bites (firm). Structured e-invoicing and digital reporting for intra-EU B2B become mandatory EU-wide.
• 2032 onward (proposed): Domestic reporting layer. Near-instant reporting on domestic trade is floated for a later stage, still tentative.

The Dutch architecture: a decentralized four-corner network

Where Spain leans on a hybrid setup and Italy routes everything through a central clearing platform, the Netherlands runs on the decentralized four-corner Peppol model. Invoices travel straight from one trading partner to another by way of their respective Access Points, with no state platform interposed in every exchange. The proposed mandate would preserve that design and bolt on a reporting channel feeding the tax authority, which some describe as stretching the four-corner model toward a five-corner one for reporting. Well-built Peppol e-invoicing software in the Netherlands manages this routing and validation in the background.

The exchange unfolds like this:

• The supplier's accounting or ERP system produces a structured invoice in Peppol BIS Billing 3.0, the Dutch NLCIUS profile.
• The supplier's Access Point checks the document against the EN 16931 and NLCIUS rule sets.
• That Access Point dispatches the invoice across the four-corner Peppol network to the recipient's Access Point.
• Addressing relies on an identifier: the Organization Identification Number (OIN) for public-sector recipients, and the KVK Chamber of Commerce number or Dutch VAT identification number for business recipients.
• Under the planned regime, the very same data flow would spin off a digital report to the tax authority, folding invoicing and reporting into a single step.

Who runs the system

A handful of public organizations keep the Dutch framework turning, and knowing their roles is useful.

• The Netherlands Peppol Authority (NPa), once known as SimplerInvoicing, oversees the Peppol network at the national level. It became a public body in 2020 and reports to the Ministry of the Interior. The NPa polices Dutch Peppol providers closely, layering extra demands such as ISO 27001 certification, End User Identification, and uptime guarantees on top of the standard OpenPeppol rules.
• Logius, the government's digital services agency, runs the central-government plumbing, Digipoort included.
• Digipoort serves as the state's secure gateway for inbound electronic documents, best suited to high-volume senders with a direct technical hookup.
• The Government Supplier Portal lets occasional, low-volume suppliers key in invoices by hand without buying software.

Formats and standards explained

Dutch e-invoices align with the EN 16931 European semantic model. Because the surrounding vocabulary trips people up, here is how the pieces connect.

• EN 16931: The European semantic standard underpinning every Dutch structured invoice.
• NLCIUS: The Netherlands Core Invoice Usage Specification, the country's tailored cut of EN 16931.
• Peppol BIS Billing 3.0: The billing profile carried on the Peppol network, in UBL syntax, and the format of choice across the Netherlands.
• SI-UBL 2.0: The earlier Dutch UBL profile, now folded into and replaced by Peppol BIS Billing 3.0. The older SI-UBL 1.x releases are no longer valid.
• Digipoort: A government transport channel, not a file format. It dictates how an invoice arrives, not what sits inside it.

On addressing: public-sector invoices use the OIN, whereas business-to-business Peppol exchanges use the KVK number or the Dutch VAT identification number. The Netherlands imposes no signature requirement; systems must safeguard authenticity and integrity, but no qualified electronic signature is obligatory.

Record-keeping obligations

Ordinary Dutch VAT bookkeeping rules govern e-invoice retention. The general rule is seven years, rising to ten years for invoices tied to immovable property. Keep records in their native structured form so their authenticity and integrity stay provable across the whole retention window. Capable e-invoicing software for the Netherlands automates that storage and keeps everything inspection-ready.

The penalty picture

With B2B invoicing still voluntary, there is no fine for sitting it out on the private side. In the public sector, an invoice that fails the rules can be bounced by the receiving body under procurement terms, which simply holds up payment. Broader Dutch tax and invoicing duties carry their own administrative penalties, and overdue VAT draws a surcharge. A purpose-built B2B penalty regime will surface only once the planned mandate becomes law, with specifics to be spelled out then.

The case for acting before the law lands

Waiting for final legislation feels prudent, yet several pressures tilt the balance toward early adoption, and toward picking the right e-invoicing software in the Netherlands now.

• Your counterparties have already shifted. Belgium switched on mandatory B2B e-invoicing on 1 January 2026, with Germany and France advancing their own timetables. A Belgian or German buyer running a Peppol-wired payables process increasingly treats incoming PDFs as friction, or simply cannot process them.
• The cross-border clock is fixed. Trade with businesses elsewhere in the EU and the 1 July 2030 ViDA date reaches you no matter what the Netherlands settles on at home.
• Late movers will hit a bottleneck. Anyone holding off until 2029 will be jostling with every other in-scope firm for scarce Access Point and advisory capacity.
• The economics work regardless. Cross-country evidence points to per-invoice savings of well above half, quicker settlement, fewer mistakes, and cleaner data, benefits that need no mandate to justify them.

A workable readiness checklist:

1. Switch on Peppol BIS 3.0 and the NLCIUS profile now if your ERP or accounting platform already supports it, as many Dutch systems do out of the box.
2. Sign with an NPa-supervised Peppol Access Point, or check that your current provider holds that accreditation.
3. Review how your invoice fields map to the NLCIUS rules, and test sample documents against EN 16931.
4. Set up your inbound process so arriving Peppol invoices are posted, matched to purchase orders, and archived automatically.
5. Clean your master data, covering VAT numbers, KVK numbers, buyer references, and payment terms.
6. Provision for the seven-year, or ten-year for property, archiving rule.
7. Watch the summer 2026 cabinet decision and the late-2026 draft bill, and reassess your scope as the rules solidify.

The Netherlands within the European frame

The Dutch strategy is intentionally in tune with Europe's wider trajectory. By backing Peppol and EN 16931 rather than inventing a one-off national system, the country sets up its businesses to satisfy both a future domestic mandate and the EU-wide ViDA rules through one shared pipe. For firms trading across the continent, that coherence pays off: what you spend on e-invoicing software for the Netherlands extends naturally to Belgium, Germany, and the broader EU regime now forming.

Stay ahead of the Dutch mandate with SMARTeIS

Built on Peppol and EN 16931, SMARTeIS by Skill Quotient gives Dutch businesses a single, dependable home for compliant invoicing. The platform generates NLCIUS and Peppol BIS 3.0 invoices, routes them through certified Access Points, automates the processing of inbound documents, and connects directly to ERPs like SAP, Sage, Dynamics, and Exact. Get compliant well before the rules require it, and meet the EU ViDA deadline without a second system.

Request your personalized demo!

Frequently asked questions

Is e-invoicing compulsory in the Netherlands today?

In part. It is required for central-government suppliers, live since 2017, and every public body has had to be able to receive structured e-invoices since April 2019. For general business trade it stays voluntary and depends on the buyer agreeing. Consumer sales sit outside the rules.

When does B2B e-invoicing become mandatory in the Netherlands?

No domestic B2B mandate is law yet. A March 2026 advisory report recommends one under ViDA, with a draft bill expected for consultation by late 2026 and a path pointing toward 2030. The single firm date is the EU ViDA cross-border obligation of 1 July 2030, which lands regardless of the domestic outcome.

How do NLCIUS, SI-UBL, and Peppol BIS 3.0 relate?

NLCIUS is the Dutch tailoring of the EN 16931 European standard. Peppol BIS Billing 3.0 is the billing profile used on the Peppol network, written in UBL, and the dominant Dutch format. SI-UBL 2.0 is the older Dutch UBL profile, now merged into and replaced by Peppol BIS 3.0; the earlier SI-UBL 1.x versions are no longer accepted.

Does a PDF count as an electronic invoice in the Netherlands?

No. A PDF, even one emailed across, is not a structured electronic invoice, since its contents cannot be validated and posted automatically. A compliant e-invoice uses a structured format such as Peppol BIS 3.0 in UBL, sent over the Peppol network.

Will the Netherlands adopt a central platform like some countries?

The advisory report advises against both a clearance model and a central state platform. It favors the decentralized four-corner Peppol network with a separate reporting channel to the tax authority. The final shape rests on legislation due from late 2026.

Must small firms and the self-employed take part?

For the proposed domestic mandate, the advisory report has earmarked mainly-B2C businesses and certain VAT-exempt activities as possible exemptions, with the final scope to be fixed in consultation. For cross-border intra-EU trade, the 1 July 2030 ViDA duty is expected to apply with no carve-outs.

What is the archiving period for e-invoices?

Standard Dutch VAT bookkeeping rules apply: seven years for most invoices, ten years for those concerning immovable property. Records should be retained in their original structured form.

Is there a penalty for not adopting e-invoicing?

Not on the B2B side today, given its voluntary status. In the public sector, a non-compliant invoice can be refused by the receiving entity, which delays payment. A dedicated B2B penalty regime arrives only once the planned mandate is enacted.