Many Dutch organizations are still running an older version of Microsoft Dynamics NAV or an outdated Business Central environment. This is often because the system still works, contains customizations, or because an upgrade keeps getting postponed.
Still, the playing field is changing rapidly. Two developments make it clear that the time to modernize is drawing nearer: the rise of Peppol and stricter requirements regarding security and software support.
1. Peppol is coming. Belgium and Germany are already leading the way.
Electronic invoicing is increasingly becoming the norm in Europe. Since January 1, 2026, Belgium has made B2B e-invoicing via Peppol mandatory for businesses subject to VAT. Germany is also phasing in mandatory requirements for electronic invoices.
The Netherlands isn’t there yet, but the direction is clear. In 2026, the Ministry of Finance published an evaluation recommending a Peppol-based model for future B2B e-invoicing. Although there is no definitive requirement yet, work is already underway on the next steps toward legislation.
For organizations, this means that the electronic exchange of invoices is increasingly becoming a prerequisite for doing business efficiently with customers, suppliers, and government agencies.
Companies that still use older versions of NAV often run into limitations in this regard:
- No standard support for modern e-invoicing processes
- Additional customization to meet new requirements
- Higher maintenance costs
- Greater reliance on external solutions
Upgrading to a modern Business Central environment in a timely manner creates a much better foundation for meeting future Peppol requirements and other digital developments.
2. Security is becoming increasingly important
The second reason is perhaps even more important: security.
Cyberattacks are becoming increasingly sophisticated, and organizations are facing stricter requirements from customers, auditors, insurers, and regulators. At the same time, Microsoft Business Central continues to evolve with new security enhancements, updates, and fixes.
However, there is an important point to note regarding older versions: Microsoft only provides support for versions that fall within the official support cycle. Once a version reaches end-of-life, it will no longer receive new security updates.
This means that organizations that continue to use the same version for years are taking on an increasing amount of risk:
- Known vulnerabilities are no longer fixed
- Integrations with modern applications are becoming more challenging
- Compliance risks are on the rise
- Reliance on Outdated Custom Solutions Is Growing
- Upgrades eventually become more complex and more expensive
Whereas an upgrade used to be viewed primarily as an IT project, it is now increasingly seen as a business risk that warrants attention from senior management, finance, and operations.
Putting it off usually doesn't make the step any smaller
A common argument is that an upgrade “will come later.” In practice, however, we see exactly the opposite. The longer an organization waits, the greater the gap becomes between its current situation and the modern Business Central environment.
As a result, costs, risks, and implementation complexity often increase as well.
Organizations that start creating a roadmap now are paving the way for a controlled modernization process. Not because the system no longer works today, but because future requirements in the areas of e-invoicing, security, and integrations are making this increasingly necessary.
