For a good while, the e-invoicing community has anticipated a revision of the EN 16931-1 standard that would move beyond its original B2G (Business-to-Government) focus. Developed initially under Directive 2014/55/EU, the 2017 version of the norm lacked some more granular data structures required for the complex B2B scenarios and real-time reporting now being mandated by EU Member States.
With the European Committee for Standardization (CEN) TC 434 finalizing the revision, end users, service providers and software vendors alike are set to receive technical clarity needed to align with the “VAT in the Digital Age” (ViDA) initiative and domestic mandates like Germany’s mandatory B2B e-invoicing. Originally hoped for in 2025, the update slipped into early 2026 at the last minute, choosing higher quality in a long-term foundation over a few weeks on our calendars.
Highlights of the technical revision
The updated semantic model focuses on three critical pillars designed to harmonize commercial reality with tax transparency:
- Closing Legacy Design Gaps: The revision addresses long-standing technical friction points, for instance regarding certain tax category combinations or a “goods/services” indicator on item level. These corrections eliminate ambiguities that previously caused validation gaps or led to validation errors when mapping tax situations to the European Norm.
- Expanded B2B Functionality: To reflect the growing scope of B2B mandates, the standard adds more support for complex business flows that may previously have required extensions. This includes improved handling of multiple purchase orders or delivery notes within a single invoice, multiple buyer references and business identifiers for buyers.
- ViDA-Aligned Data Elements: In direct response to the upcoming Digital Reporting Requirements (DRR), new elements have been introduced. These include clearer bank account information as well as more robust structures for cash discounts and multiple payment terms and late payment penalties, ensuring that the invoice contains all the data points required by tax authorities for automated VAT reporting.
Impact, migration, and the road ahead
The most significant takeaway is that the 2026 revision is not backward compatible. The introduction of new business terms, modified validation rules, and updated syntax bindings for UBL and UN/CEFACT CII means that existing “version 3” implementations cannot simply absorb the new traffic. Migration planning is required now, especially for service providers performing format conversions, as the underlying XML structures will shift significantly.
Furthermore, several key follow-up activities are already in motion to operationalize this update:
- Peppol BIS 4.0: OpenPeppol has initiated a workgroup, merging the adoption of the EN 16931 update together with a general shift to a “PINT”-like (Peppol INTernational) methodology. This convergence will result in Peppol BIS 4, creating a unified global standard that accommodates both European and international tax requirements.
- XRechnung 4.0: In Germany, the KoSIT (Coordination Office for IT Standards) is planning a major version 4.0 release of XRechnung. This version will align the national CIUS with the new semantic model, serving as the technical backbone for the German B2B mandate.
- Other updates: Similarly, adoption of the EN 16931 update is planned e.g. in the France aligning the French CTC extensions to absorb the new capabilities.
The formal publication process is expected to conclude in mid-2026:
- Formal vote in CEN TC 434 on the core semantic model unanimously approved the update in late January 2026.
- This triggered the publication process through the national standardization bodies, to be completed within 6 months.
- Syntax bindings to UBL 2.5 and CII D25A internally available and TS draft accepted, to be formally voted on in July 2026.
For the service providers arena, the shift marks the beginning of yet another phase in the accelerating landscape of e-invoicing mandates, particularly in Europe.
Consistent adoption of this EN 16931 update with its extended scope should help to reduce the need for national or industry-specific variations based on the larger reach of invoicing functionality covered.
