ERP and accounting software for the Netherlands - Peppol, Dutch VAT and the road to 2030

There is no Dutch mandate, and we are not going to invent one

Several country pages on this site are organised around a compliance deadline, because in Belgium, Poland and much of the Gulf there genuinely is one. The Netherlands does not have one. No domestic business-to-business e-invoicing mandate is in force, and writing this page as though a Dutch finance director were running out of time would be both untrue and obvious.

What exists is narrower and worth stating precisely. Business-to-government invoicing runs over the Peppol network. In March 2026 the Ministry of Finance presented a design framework for a domestic B2B regime to Parliament, targeting January 2030. That is a stated direction with a long runway attached, not an obligation you are behind on.

So the Dutch argument for changing systems has to be made on its merits, and it can be. The merits are operational: fewer places for the same figure to be keyed, a VAT position that can be explained line by line, cross-border trade handled as data rather than as annotation, and a close that does not consume a week. That is a sufficient reason on its own, and it does not need a deadline propped behind it.

If a vendor tells you the Netherlands is about to mandate B2B e-invoicing, ask them to name the instrument and the commencement date. The honest answer today is that a framework has been presented to Parliament with 2030 in view. Confirm the current position with the Belastingdienst.

• No domestic B2B e-invoicing mandate is in force in the Netherlands.
• B2G invoicing runs over the Peppol network.
• A design framework was presented to Parliament in March 2026, targeting January 2030.
• A framework presented to Parliament is not a commencement date.
• The case for change here is operational, and it stands without a deadline.

What the 2030 framework implies for a decision made today

A long runway changes the shape of a good decision rather than removing the need for one. Systems bought today will still be running in 2030. So the question is not whether to act now on a mandate, but whether the choices you make now leave you well or badly placed when a regime eventually arrives.

The likely shape is legible from what already exists. Dutch public sector invoicing runs over Peppol, and the Netherlands operates inside a European environment where Belgium has already built its live mandate on Peppol. A domestic Dutch regime that ignored that infrastructure would be a surprise. Building toward structured invoice data and network-capable exchange is therefore a low-regret direction, whatever the final rules say.

Low-regret is not the same as urgent. It means that when you replace a system for ordinary reasons, you should prefer one that can already produce a structured invoice and already holds customer identifiers as fields, rather than paying a premium today for a specific format that may not be the one adopted.

It also means resisting the reverse mistake: locking into a narrow point solution built for a rule that does not exist yet. The durable investment is in the data, not the pipe.

• Systems bought now will outlive the current absence of a mandate.
• Peppol already carries Dutch public sector invoicing.
• Belgium built its live mandate on Peppol, next door.
• Invest in structured invoice data, which survives any format decision.
• Avoid paying a premium today for a format that has not been chosen.

Post-audit is not the easy option

It is tempting to read the absence of a mandate as an absence of scrutiny. It is not. In a clearance country such as Poland, the tax authority sees the invoice before the buyer does, and a malformed invoice fails immediately and visibly. In a post-audit country such as the Netherlands, nothing fails at the moment of issue. Problems accumulate silently and surface later.

That has a practical consequence for how you build controls. Where the state does not validate your documents in real time, your own system has to. Sequential numbering that cannot be quietly broken. Credit notes linked to the invoices they correct rather than floating free. VAT treatment stored per line so a return can be traced back to the sales that produced it. Exchange rates recorded on the transaction rather than reconstructed afterwards.

Businesses in clearance countries often have better invoice hygiene than businesses in post-audit countries, not because they are more diligent but because they were forced. A Dutch business has to choose that discipline for itself, and the choice is usually made years before it is tested.

There is a second-order effect worth planning for. A Dutch business selling into Belgium or Poland will have its documents machine-validated abroad even while nothing validates them at home, so the quality bar is effectively set by your most demanding market rather than by your own. Groups usually discover this when a Belgian or Polish customer rejects something that has been accepted domestically for years, and the underlying record turns out to have been wrong in both places.

• No mandate means no external validation at the moment of issue.
• Errors surface at inspection, when the people involved have moved on.
• Enforce unbroken numbering inside your own system.
• Link every credit note to the invoice it corrects.
• Store VAT treatment per line so returns can be traced to source.
• Record the exchange rate applied on the transaction itself.

Where the Netherlands sits among its neighbours

Four nearby European markets currently sit at four different points, and seeing them together makes the Dutch position easier to reason about. Poland runs a clearance model: the invoice goes through KSeF to the tax authority for approval before it reaches the buyer, and the authority assigns the invoice identifier. Belgium runs a network model: structured invoices are exchanged over Peppol between trading partners, mandatory since January 2026.

Spain sits between them in a different way again. Its rules on billing software are phasing in, while its B2B e-invoicing mandate is approved but not yet running. The Netherlands is the fourth point: nothing in force domestically, and a framework aimed at 2030.

For a Dutch group with operations across these countries, that divergence is the actual design constraint. The same customer order has to produce a clearance submission in Poland, a Peppol document in Belgium, a compliant billing record in Spain and an ordinary invoice at home. Systems that assume one European behaviour break at exactly this point.

Skyline Nexus keeps country behaviour as configuration on the entity rather than as a global setting, so that one chart of accounts and one customer master can sit behind four different invoicing outcomes. What it will not do is decide for you which regime a given transaction falls under.

• Poland: clearance through KSeF before the invoice reaches the buyer.
• Belgium: mandatory structured exchange over Peppol since January 2026.
• Spain: billing-software rules phasing in, B2B mandate approved and pending.
• Netherlands: no domestic mandate in force, framework targeting 2030.
• Design for divergence; it is the stable assumption in Europe today.

Dutch VAT and the two rates that matter

The Netherlands applies a standard VAT rate of 21 percent and a reduced rate of 9 percent, in euro. For a business with a mixed catalogue, the reduced rate is where errors live. Classification is a product data problem, and it is solved at the item level or not at all.

When the rate is a property of the item rather than something a salesperson picks at the counter, the same product is taxed the same way in every channel, and a mistake is corrected once. When it is picked at the point of sale, you get a distribution of answers and no way to tell which invoices were wrong without reading them.

Intra-EU trade adds the second layer. Supplies to VAT-registered customers in other member states, reverse charge on many business-to-business services, and the customer VAT identification number all belong on the document as fields. Validate the number rather than trusting it, and store the validation with the transaction so it can be produced later.

• Standard rate 21 percent, reduced rate 9 percent, in euro.
• Set the rate as a property of the item, not a choice at the counter.
• Capture and validate customer VAT identification numbers on intra-EU supplies.
• Treat reverse charge as a stored treatment with the right document wording.
• Keep the rounding basis consistent across channels.

Trade, logistics and the invoices they generate

The Netherlands earns a disproportionate share of its activity from moving and handling goods that belong to companies elsewhere, and that shapes what a Dutch system has to hold. Freight and handling charges on the same document as goods. Shipments that cross a period end. Costs incurred in one currency and billed in another. Customers who are intermediaries rather than end buyers.

Each of those is a place where a general-purpose accounting package quietly loses information. Charges get flattened into a single line and the VAT treatment of the freight component is lost. A shipment in transit at month end gets recognised in the wrong period because nobody recorded the delivery event. A foreign currency cost is translated at a rate nobody wrote down.

The fix is unglamorous: capture the events as they happen, in the system that will later have to explain them. Delivery separate from invoicing. Landed cost attached to the goods rather than posted as an expense. Original currency and applied rate stored on every foreign transaction. None of this is a Dutch legal requirement. All of it is why Dutch closes take longer than they should.

Skyline Nexus holds these as distinct records rather than as annotations: delivery separate from invoice, landed cost attached to the item, original currency and applied rate stored on the posting, and bill-to and ship-to as separate parties on the same document. That is a description of what the system keeps, not a claim about any Dutch obligation, because on this point there is no obligation to claim.

• Keep freight and handling as their own lines with their own VAT treatment.
• Record delivery as an event distinct from invoicing, for period cut-off.
• Attach landed cost to the goods rather than burying it in expenses.
• Store original currency and the applied rate on every foreign transaction.
• Model intermediaries properly; bill-to and ship-to are not the same party.

IFRS as adopted by the EU, and local GAAP underneath

Listed companies in the European Union report consolidated accounts under IFRS as adopted by the EU. Individual entities commonly prepare their statutory accounts under local generally accepted accounting principles. A Dutch entity inside an international group therefore usually serves two presentations from one set of underlying transactions.

This is one of the clearest structural differences between operating in Europe and operating in the Gulf, and it is worth naming rather than glossing. It affects consolidation, not the invoice, but it decides how much detail the invoice has to leave behind. Presentations differ; the transaction record has to be rich enough to support both.

Practically, that argues for keeping entity, branch, cost centre and project as dimensions on the posting rather than deriving them at report time, and for keeping subledgers reconciled to their control accounts so that the statutory close and the group package start from the same numbers. Which framework applies to you is a determination for your auditor.

• EU listed companies: IFRS as adopted by the EU for consolidated accounts.
• Individual entities: commonly local GAAP for statutory accounts.
• One transaction record must support both presentations.
• Carry entity and branch as posting dimensions.
• The framework determination belongs to your auditor.

What to build toward without a deadline

Absent a mandate, the useful discipline is to ask which improvements would still be worth making if no regime ever arrived. Nearly all of the durable ones are about data quality, and none of them depend on a format decision.

Customer master data with validated VAT identification numbers and settled legal names. One invoice numbering scheme rather than one per channel. Item-level tax classification. Credit notes linked to their originals. Exchange rates stored on the transaction. Delivery recorded separately from invoicing. Every one of those pays for itself in a faster close, and every one of them is also a prerequisite for any structured invoicing regime the Netherlands might eventually adopt.

That is the honest version of preparing for 2030: do the things that are worth doing anyway, and let the format follow when it is known. A business that has done this can add a network connector in weeks. A business that has not will still be cleaning customer records when the rules are published.

There is also a sequencing benefit specific to Dutch groups with operations elsewhere in Europe. The master data work is the same data whether it feeds a Belgian Peppol document, a Polish clearance submission or a Dutch PDF. Doing it once, at home, where nothing is failing yet and there is no deadline pressure, is considerably cheaper than doing it in a foreign subsidiary during a live implementation with rejections accumulating.

• Clean and validate customer tax identifiers now.
• Consolidate invoice issuance and numbering.
• Classify tax treatment at item level.
• Link corrections to originals as recorded events.
• Store currency and rate with every foreign transaction.
• Leave format and transmission until the rules exist; that part is fast.

Questions worth asking a supplier about the Netherlands

The most useful test of a supplier in a market with no mandate is whether they will say so. Ask directly whether Dutch B2B e-invoicing is mandatory. An answer that hedges toward yes tells you what their sales process is optimised for.

After that, the questions are operational. Can the system produce a structured invoice today for public sector customers? Does it hold customer VAT identification numbers as validated fields? Does it store the applied exchange rate on the transaction? Can a VAT return figure be traced to the individual invoices behind it? Can freight be invoiced with its own tax treatment on the same document as goods?

Then the group question: what does the same system do differently in Belgium, Poland and Spain? For a Dutch parent with European subsidiaries that is the difference between one implementation and four.

• Is B2B e-invoicing mandatory in the Netherlands? Listen to the answer.
• Can you issue structured invoices to public bodies over Peppol today?
• Are customer VAT identification numbers held and validated as fields?
• Is the applied exchange rate stored on the transaction?
• Can each VAT return figure be traced to the invoices behind it?
• How does the system behave differently in Belgium, Poland and Spain?

Confirm the position with the Belastingdienst

Everything on this page reflects the position as confirmed on 7 September 2026: no domestic B2B e-invoicing mandate in force, public sector invoicing over Peppol, and a design framework presented to Parliament in March 2026 targeting January 2030.

Positions like this change through legislative process rather than overnight, but they do change, and a web page is not a source of law. The Belastingdienst is the authority for Dutch tax administration, and it is where the current position should be confirmed before you commit budget or sign a contract on the strength of a timeline.

A software supplier can honestly tell you what its system records, produces and prevents. It cannot tell you that you are compliant, and it should not try. Skyline Nexus is offered on that basis: capability described plainly, with the compliance conclusion left to your adviser.

• Authority: Belastingdienst.
• Position stated as confirmed on 7 September 2026.
• No domestic B2B mandate in force; framework targeting January 2030.
• Confirm the current position before budgeting, because a page is not a source of law.
• No software certifies you as compliant, in the Netherlands or anywhere else.

Common questions

Is e-invoicing mandatory in the Netherlands?

Not for business-to-business transactions. No domestic B2B e-invoicing mandate is in force. Business-to-government invoicing runs over the Peppol network, and in March 2026 the Ministry of Finance presented a design framework for a domestic B2B regime to Parliament targeting January 2030. Confirm the current position with the Belastingdienst.

What is happening in 2030?

A design framework for a domestic business-to-business e-invoicing regime was presented to Parliament by the Ministry of Finance in March 2026, targeting January 2030. That is a stated direction of travel with a long runway, not a commencement date, and the details would be settled through the legislative process.

What are the Dutch VAT rates?

The standard rate is 21 percent and there is a reduced rate of 9 percent, charged in euro. For a mixed catalogue the reduced rate is where most errors occur, which is why tax classification is better set as a property of the item than chosen at the point of sale.

If there is no mandate, why change accounting systems?

Because the Dutch case is operational rather than regulatory. Without a clearance system validating documents at the moment of issue, your own records carry the burden of proof at inspection. Unbroken numbering, credit notes linked to originals, VAT treatment stored per line and exchange rates recorded on the transaction are all worth having regardless of what any future regime requires.

How does the Netherlands compare with Belgium and Poland?

They sit at three different points. Poland clears invoices through KSeF, where the tax authority approves the invoice before it reaches the buyer. Belgium requires structured invoices exchanged over the Peppol network, mandatory since January 2026. The Netherlands has no domestic B2B mandate in force at all. A group operating across them needs per-country behaviour rather than one European setting.

Rates, regimes and deadlines in this summary change, and many countries are actively legislating on e-invoicing. This is general information, not tax or legal advice — confirm the current position with the authority named above or with your tax adviser before you rely on it.