Preparing for mandatory e-invoicing in the Netherlands after the policy outline letter

Anyone preparing for mandatory e-invoicing in the Netherlands now has a firm framework. In the policy outline letter on electronic invoicing and reporting (Contourenbrief elektronisch factureren en rapporteren) of 11 September 2026, reference 2026-0000288216, State Secretary for Finance Eelco Eerenberg confirms, also on behalf of the Ministers of Economic Affairs and of the Interior, that e-invoicing becomes mandatory for all domestic B2B transactions from 1 July 2030, followed by digital reporting of domestic transactions to the Dutch Tax Administration (Belastingdienst) from 1 July 2031. The Netherlands thereby goes beyond the EU minimum set by ViDA. One choice remains open: the infrastructure for exchanging e-invoices. This article sets out what has been decided, what is still open, and what businesses, public bodies, software vendors, Peppol Serviceproviders and integrators can arrange today.

Reading guide: passages marked What the letter says reflect the content of the letter. Passages marked Analysis and the assessment section are the view of Peppol.nu.

Why this letter matters

Council Directive (EU) 2025/516 (ViDA) requires e-invoicing and per-transaction reporting for cross-border B2B trade from 1 July 2030. Member States may extend these obligations to domestic transactions. Following the EY study shared with the Dutch House of Representatives on 10 March 2026 (Parliamentary Papers II 2025/26, 22112, no. 4290), the Cabinet has now made that choice. For every organisation that sends or receives invoices, the obligation itself is settled; what remains open is implementation and infrastructure.

What has been decided: the decision table in summary

What the letter says. The Cabinet summarises its principles in a table. In essence:

Substantive principles

• One standard: EN 16931 only, including for domestic invoices.
• Invoicing deadline: invoices must be issued within 10 days of the supply of goods or services.
• Near real-time reporting per invoice: invoice data goes to the Tax Administration at the moment of issue, instead of aggregated monthly or quarterly as with today’s EC Sales List.
• Data minimisation: domestic reporting covers a selection of data fields matching the subset used at EU level which, according to the letter, has been approved by the European data protection supervisor.
• Retention period: ten years for reported data, in line with the central VIES system.
• KOR: no domestic e-invoicing obligation for businesses under the small business scheme, although reporting of intra-Community acquisitions may apply.
• Safeguards: access logging, monitoring, need-to-know authorisation, pre-tested risk models, an opinion of the Dutch Data Protection Authority (AP) and a DPIA.
• Digital autonomy: the Tax Administration aims to shape its digital environment as independently as possible, with less reliance on non-European technology vendors.
• Sensitive goods: the directive contains no exemption for, for example, defence and security. The Cabinet is raising this at EU level.

Process and ViDA timeline

1. Parliamentary letter of 26 June 2025: study of policy choices announced.
2. 10 March 2026: EY study sent to Parliament, recommending broad e-invoicing and digital reporting.
3. 11 September 2026: policy outline letter with the Cabinet’s choices.
4. Until October 2026: follow-up study on the digital infrastructure.
5. Autumn 2026: public internet consultation starts.
6. Before the 2027 summer recess: bill submitted to Parliament.
7. Before 1 July 2028: parliamentary procedure completed, two years before entry into force.
8. 1 July 2030: B2B e-invoicing (domestic and intra-Community) and reporting of intra-Community transactions including acquisitions.
9. 1 July 2031: digital reporting of domestic transactions.

In parallel: an administrative burden study by Sira Consulting, an SME test, a business impact assessment, an implementation assessment by the Tax Administration, the AP opinion and a DPIA.

Not yet decided: the infrastructure

What the letter says. EY recommended mandating the Peppol network between businesses; Peppol is already mandatory in the Netherlands for invoicing to central government. The Cabinet states the topic is not yet ready for a decision and is also taking the European Business Wallet (EBW) into account. Until October 2026, five core principles are being worked out: interoperability, the relationship between e-invoicing and digital reporting, secure and reliable data exchange, competition, and safeguarding supervision and enforcement. The letter notes that businesses ask for certainty, while prescribing an infrastructure is also a market intervention.

Analysis. Peppol mandatory B2B is therefore not yet a fact, but it is far from off the table. The letter itself acknowledges the risk of not prescribing anything: e-invoices that are not interoperable between accounting system A and system B.

Assessment: preparing for mandatory e-invoicing in a half-decided framework

Strengths

• A fixed date, with reporting following a year later, leaves room to sort out invoice flows first and reporting second.
• A single standard (EN 16931) without national variants prevents fragmentation.
• No additional micro-threshold and as few new exemptions as possible keep the rules simple.
• Privacy is addressed up front: data minimisation in line with the EU subset, an AP opinion, a DPIA and a retention period shorter than the current 12-year VAT retention period.

Points of attention

• The 10-day invoicing deadline affects processes built on monthly summary invoices or slow manual approval.
• The KOR exemption is narrower than it looks: KOR businesses will still receive e-invoices and may have reporting duties for intra-Community acquisitions.
• The outcomes of the Sira study and SME test could still adjust the principles.

Open questions

• Infrastructure: Peppol, the EBW or a combination has not been decided.
• Architecture of e-invoicing and reporting: will reporting run through the Peppol Serviceprovider (as in Belgium’s 5-corner model, an ambition for 2028) or directly from the business to the Tax Administration? The letter only lists this relationship as a principle to be studied.
• Data fields: the exact fields to be reported have not yet been specified.
• Penalties and transition: the letter says nothing about fines or grace periods, and mentions a test phase only as important.
• B2G alignment: the letter does not address how the existing B2G framework connects.
• EBW role and competition: how a mandate would affect the market for Peppol Serviceproviders and software vendors remains open.

Critical observations (analysis)

• Reporting benefits are indirect. The Cabinet acknowledges that businesses will feel the benefits less directly. The case rests on fraud prevention and a more level playing field; concrete burden reduction comes only “in due course”.
• Evidence from abroad is thin. The fall in the VAT gap in Italy and Hungary is cited, but the letter itself says these countries may not be representative and that the effect is hard to isolate.
• A tight window. If the law passes in mid-2028 and the infrastructure is only detailed afterwards, two years remain for building, testing and migrating across every invoicing business.
• EN 16931 is a semantic model. It says nothing yet about syntax (UBL or CII), a national CIUS or transport. Those choices define the actual build for software.
• Certainty versus market disruption. Postponing the infrastructure decision holds back investment decisions by vendors and large enterprises. Waiting costs build time; choosing now carries a limited selection risk.

What this means in practice: a guide per audience

Analysis. Because EN 16931 is fixed and Peppol supports that standard today, most of the steps below do not depend on the infrastructure choice.

Business owners and finance managers (including SMEs and KOR)

What you need to have in place before the end of 2027:

• Map your outgoing and incoming invoice flows: volumes, customers, countries, systems.
• Ask your accounting or ERP vendor in writing for its roadmap on EN 16931, near real-time reporting and the 10-day deadline.
• Test your invoicing process against the 10-day deadline (summary invoices, approval rounds).
• Clean up master data: VAT numbers, Chamber of Commerce numbers and addresses of customers and suppliers.
• If you trade with Belgium or France, start now: obligations already apply there.
• KOR businesses: prepare to receive e-invoices and check whether you make intra-Community acquisitions.

What you need before 1 July 2029: a working solution that sends and receives EN 16931 invoices, tested with your main trading partners. Reporting of intra-Community transactions follows from 1 July 2030 and domestic reporting from 1 July 2031.

(Public) organisations as recipients and buyers

• Central government: B2G via Peppol already exists. Check that your receiving side can handle growing volumes.
• Municipalities, provinces and water boards: as contracting authorities you must already be able to receive EN 16931 invoices. Make receipt via Peppol the default and include it in your purchasing terms.
• Where you invoice businesses yourself (for example VAT-taxed leasing), you may fall under the B2B obligation as a taxable person. Have this reviewed legally before 2028.
• Align internal approval processes with the 10-day deadline.

Software vendors (ERP and accounting)

• Before the end of 2026: follow the internet consultation and provide input on data fields, architecture and transition.
• Before the end of 2027: support EN 16931 natively in both syntaxes (UBL and CII), including validation before sending.
• Build a reporting module that can derive a per-invoice dataset, so you are ready for reporting via a serviceprovider or directly.
• Adapt invoicing logic to the 10-day deadline and alert users when it is exceeded.
• Decide whether to become a Peppol Serviceprovider yourself or work with a partner.

Peppol Serviceproviders

• Prepare capacity for the step from B2G to full B2B volumes.
• Develop scenarios for a 5-corner role: forwarding a reporting dataset to the Tax Administration, following the Belgian example.
• Follow developments around the EBW and the competition assessment, and engage as a stakeholder in the consultation and with the Netherlands Peppol Authority (NPA).
• Make onboarding easy for SMEs and KOR businesses.

Integrators

• Map each client’s landscape: which systems invoice, which receive, where manual steps remain.
• Design for decoupling: a mapping layer to EN 16931 separate from transport, so a later infrastructure choice does not require a rebuild.
• Plan test windows in 2029 with clients and their trading partners.
• Build logging and error handling for near real-time reporting into the architecture.

Frequently asked questions

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

Under the Cabinet’s proposal, from 1 July 2030 for domestic and intra-Community B2B transactions. Digital reporting of domestic transactions follows from 1 July 2031.

Is Peppol mandatory for B2B?

Not yet decided. EY recommended mandating Peppol; the Cabinet is studying the infrastructure until October 2026 and is also considering the European Business Wallet.

Which standard must an e-invoice follow?

Only the European standard EN 16931, referenced in Implementing Decision (EU) 2017/1870. No additional national standards will be introduced.

Does the obligation apply to businesses under the small business scheme (KOR)?

KOR businesses have no domestic e-invoicing obligation. A reporting obligation for intra-Community acquisitions may still apply.

What must be reported to the Dutch Tax Administration?

A limited selection of invoice data per invoice, near real-time. The exact fields follow the EU subset and will be specified in the bill.

Sources

1. State Secretary for Finance, Contourenbrief elektronisch factureren en rapporteren (policy outline letter), 11 September 2026, reference 2026-0000288216 (not yet available online on rijksoverheid.nl or tweedekamer.nl at the time of publication).
2. Parliamentary letter on implementing the VAT in the Digital Age directive, 26 June 2025 (Dutch)
3. Cabinet response to the EY report on ViDA e-invoicing and digital reporting, 10 March 2026, Parliamentary Papers II 2025/26, 22112, no. 4290 (Dutch)
4. Council Directive (EU) 2025/516 of 11 March 2025 (VAT in the Digital Age)
5. Commission Implementing Decision (EU) 2017/1870 of 16 October 2017 (EN 16931)
6. OECD (2022), Tax Administration 3.0 and Electronic Invoicing: Initial Findings

Further reading on Peppol.now

• Review of the EY report ViDA e-invoicing Netherlands
• Netherlands ViDA e-invoicing: what businesses need to know before 2030
• News: Dutch cabinet confirms mandatory e-invoicing Netherlands 2030

The infrastructure choice will only follow after October 2026, but the standard, the data and the deadlines are set. If you start preparing for mandatory e-invoicing as a project now, choose a solution that already supports EN 16931 today. In the Peppol.now comparison tool you can filter Peppol Serviceproviders and software packages by your situation.