EN 16931 is getting an update. Here's what changes and what it means for your product.
The EN 16931-1 standard, the backbone of structured e-invoicing across Europe, is due for a significant update in mid-2026. If you're building or maintaining a product that handles invoicing, this is worth understanding now rather than later.
Not familiar with EN 16931 yet? Start with the basics: What is EN 16931? The European e-invoicing standard explained.
When EN 16931 was first developed, the primary use case was B2G invoicing. Governments needed a common standard so that public buyers across Europe could receive and process structured invoices from suppliers, regardless of which country they were in or which software the supplier was using. That worked. B2G e-invoicing is now mandatory across the EU, and adoption in markets like Finland, Sweden, and Norway has been high for years.
But the regulatory scope is expanding. The EU's ViDA (VAT in the Digital Age) initiative is pushing e-invoicing into B2B territory across the bloc, and several countries have moved ahead with their own national B2B mandates already. Belgium's went live in January 2026. France, Germany, and others are following.
B2B e-invoicing introduces requirements that the original B2G-oriented standard wasn't fully designed to handle. More document types, more complex transaction flows, differences in how VAT needs to be reported and validated. The EN 16931-1 update is the standard catching up with the direction the market is already moving.
The details of the update are still being finalised, but the direction is clear: the updated standard will be better suited to the realities of B2B invoicing at scale. That means adjustments to the semantic data model, likely expanded support for additional data fields or document types, and alignment with what ViDA will require when it takes full effect.
This will flow downstream. When EN 16931 changes, the syntax bindings (UBL 2.1, UN/CEFACT CII) and the Peppol specifications built on top of it will need to follow. Implementation timelines for those downstream changes haven't been published yet, but mid-2026 for the core standard gives a rough sense of the sequencing.
For software vendors, the practical implication depends on your current setup.
If you're integrated with a provider that owns the compliance layer, the update is largely their problem to solve, not yours. Format changes, schema updates, new validation rules: a good e-invoicing partner handles this without requiring you to reopen the integration.
If you've built e-invoicing in-house or rely on a provider that pushes compliance changes back to you, this update adds to your maintenance queue. And it won't be the last one. ViDA's full rollout runs to 2030, and the standard will continue to evolve as more countries implement B2B mandates and real-time reporting requirements come online.
The pattern here matters: e-invoicing compliance is not a one-time implementation, but an ongoing commitment. The EN 16931 update is a useful reminder of that, regardless of your current setup.
The mid-2026 timeline for the standard update means downstream specification changes and implementation guidance will likely land in H2 2026 or into 2027. If your product is already live with e-invoicing, you have time to assess the impact, but that assessment is worth starting now. If you're planning a new integration, factor in that the specification landscape is shifting.
Either way, understanding the regulatory direction is part of building a product that stays compliant without constant firefighting.
The EN 16931 update is one piece of a broader shift in how e-invoicing works across Europe. For a market-by-market breakdown of mandates, formats, and what's coming, visit our e-invoicing in Europe overview.