EN 16931 Update Mid-2026: What It Means for Your E-Invoicing Infrastructure
The EU's core e-invoicing standard, EN 16931, is being updated. The revised version is expected mid-2026, and while it might sound like a bureaucratic detail, it has real implications for every software vendor and service provider with Peppol or e-invoicing capabilities built into their platform.
Here's what's changing, who it affects, and most importantly, what you should be doing about it.
Every Peppol invoice in Europe is built on EN 16931
What is EN 16931?
EN 16931 is the European standard that defines the semantic data model for electronic invoices. In plain English: it's the agreed-upon definition of what an e-invoice is:
- what fields it contains
- what they mean
- how they relate to each other
Every Peppol invoice in Europe is built on EN 16931. Every compliant e-invoicing implementation, whether it's a Peppol BIS format, a national format, or a CTC submission references this standard. When EN 16931 changes, the ripple effects go all the way down the stack and have implications.
Invoices that pass today's checks may not pass tomorrow's
What's Changing in the 2026 Update
The revision reflects the EU's shift from public sector e-invoicing mandates to full B2B mandates across member states. Key expected changes include:
- Expanded data model: New fields and business rules to support B2B VAT reporting requirements, to align with EU's ViDA, VAT in the Digital Age initiative
- Updated validation rules: Stricter schematron rules for invoice validation, which means invoices that pass today's checks may not pass tomorrow's
- Better alignment with CTC requirements: Continuous Transaction Control frameworks (real-time tax reporting) require additional data that the current standard doesn't fully accommodate
- Revised country-specific extensions: National adaptations across Belgium, France, Germany, and others will be updated to align with the new core standard
The question is whether it affects you or your customers?
Who Is Affected
If you are a software vendor, ERP provider, or service provider who:
- Generates or processes Peppol invoices for EU customers
- Has built invoice validation logic into your platform
- Offers e-invoicing as a feature of your product
…then this update affects you. The question is whether it affects you directly, or whether your infrastructure provider handles it for you.
The Two Types of Software Vendor
Type A: You built your own Peppol Access Point
You will need to update your validation logic, schematron rules, and invoice generation templates to comply with the updated standard. You'll need to track the draft specifications, run testing against the new rules, and push updates to production before the deadline. You own this.
Type B: You partner with a pre-accredited AP provider
Your provider handles the standard updates. When EN 16931 v2 goes live, your infrastructure is already compliant, because that's what you're paying for. Your job is to make sure your provider has actually done this (ask them).
This is one of the less-discussed but very real costs of the "build your own AP" path: it's not a one-time build. Standards evolve, and every update requires engineering time. Arratech has setup a platform that handles these changes for its customers.
The ViDA Connection
The EN 16931 update doesn't happen in a vacuum. It's part of a broader EU initiative, VAT in the Digital Age (ViDA), that is fundamentally changing how VAT is reported and verified across Europe.
ViDA will require real-time or near-real-time transaction reporting to tax authorities in most EU member states by 2030. This means e-invoicing infrastructure will need to do more than just route invoices between buyers and sellers, it will need to simultaneously report transaction data to tax authority systems.
This is what's known as Continuous Transaction Control (CTC), and it requires a different type of infrastructure: specifically, C5 Aggregation Access Points that can handle both document exchange and tax reporting in a single flow.
Most Peppol Access Points on the market today do not support CTC. This is a gap that will matter, soon.
What You Should Do Before Mid-2026
1. If you're using a third-party AP provider: Ask them directly: "How are you handling the EN 16931 update? When will your infrastructure be compliant?" Any credible provider should have a clear answer.
2. If you built your own AP: Start tracking the draft specification now. The CEN Technical Committee (TC 434) is publishing updates, we recommend you subscribe to their communications. Build your update timeline so you're not scrambling in Q3.
3. Audit your invoice validation logic: Map your current validation rules to the EN 16931 data model. Identify fields or rules that are likely to change, and plan your update path.
4. Start thinking about CTC: If your customers operate in France, Spain, or other ViDA-aligned markets, the next wave of requirements goes beyond EN 16931. CTC capability is quickly becoming a requirement for all those that supply e-invoicing infrastructure.
The Infrastructure Perspective
At Arratech, our platform has been built with CTC capability and readiness in mind and is continuously updated as standards evolve, EN 16931, Peppol specifications, PKI migrations, national extensions, and CTC frameworks. When the EN 16931 update goes live mid-2026, our customers don't need to do anything. Their infrastructure is already compliant.
That's the core value of pre-accredited, managed Peppol infrastructure: regulatory compliance is not your problem.
Arratech provides accredited Peppol Access Point and SMP infrastructure, with built-in support for EN 16931 updates and CTC capabilities. We are ISO22301 and ISO27001 certified, read more about our security and quality in our compliance and trust hub.
GET A DEMO
