EN 16931 E-Invoicing Standard: Requirements, Formats and EU Compliance

• EN 16931 is the EU's semantic data model for electronic invoices, and it now has two live versions in circulation: the original 2017 baseline and the newly revised EN 16931-1:2026.
• XRechnung and ZUGFeRD are the two formats Germany recognizes as EN 16931 compliant, and Peppol BIS Billing networks run on the same standard.
• Germany's B2B e-invoicing mandate is phased: receiving is mandatory now, issuing becomes mandatory in 2027 for larger businesses, and the transitional rules run longer than most guidance suggests.
• EN 16931 underpins ViDA, the EU's VAT reform, which brings a cross-border e-invoicing mandate on July 1, 2030.
• Doxis processes EN 16931-compliant inbound invoices today, with dedicated SAP-side capabilities for both inbound and outbound e-invoicing.

EN 16931 is the European standard that defines the semantic data model for electronic invoices: the specific data elements an invoice must contain, such as invoice number, tax details, and line items, independent of file format.

Developed by CEN under EU Directive 2014/55/EU, it was first published in 2017 to standardize invoicing between suppliers and public sector buyers across the EU, and it now underpins B2B e-invoicing mandates too.

EN 16931 sets requirements at two levels: what an invoice must contain, and how that content must be represented.

The core invoice model defines the mandatory data every compliant invoice needs: seller and buyer identification, invoice and tax date, line-item detail, and tax breakdowns.

This part of the standard is syntax-independent. It says what has to be there, not what file format carries it.

Syntax bindings then map that core model onto an actual machine-readable format. EN 16931 supports two syntaxes: UBL (Universal Business Language) and UN/CEFACT CII. National formats like XRechnung and ZUGFeRD are built on top of these syntaxes, adding country-specific business rules on top of the shared European core.

Compliance also runs through two conformity levels:

• CORE: the base invoice data model, usable across any EU member state without further adaptation.
• CIUS (Core Invoice Usage Specification): a national or sector-specific extension of CORE, adding mandatory fields a specific country's tax authority requires. Germany's XRechnung is a CIUS built on the shared CORE model, which is why a business that can process CORE invoices can generally process CIUS invoices too.

The 2026 revision

CEN approved a revised version of the standard, published as EN 16931-1:2026 on March 18, 2026, following unanimous approval from the participating member states.

The revision aligns the semantic model with ViDA's Digital Reporting Requirements, so near-real-time VAT reporting can run on the same structured invoice data businesses already exchange.

A transition phase between the 2017 baseline and the 2026 version is expected to follow the same pattern as previous CEN revisions, giving software vendors and tax authorities time to adopt the update.

Any format built on the EN 16931 semantic model and one of its two supported syntaxes qualifies. In practice, that means:

• UBL-based formats, including Peppol BIS Billing 3.0
• CII-based formats, including the hybrid PDF/XML formats ZUGFeRD and Factur-X
• XRechnung, Germany's national CIUS, built on UBL

A plain PDF invoice, even a nicely formatted one, is not EN 16931 compliant. It carries no structured, machine-readable data, which is the entire point of the standard.

Yes. Peppol is a network, not a format, but the invoice documents that move across it, specifically Peppol BIS Billing 3.0, are built directly on the EN 16931 UBL syntax.

That's what makes Peppol useful as a compliance mechanism: an invoice validated against Peppol BIS Billing 3.0 is validated against EN 16931 by construction.

This is also why Peppol keeps showing up as the connective layer across otherwise fragmented national mandates, from Germany's XRechnung network to France's and Belgium's platform-based systems.

All three comply, but they represent the standard differently.

XRechnung is Germany's national CIUS, a pure XML format with no visual component. It's the format Section 4 of the German E-Invoice Ordinance (ERechV) names as the default for public sector invoicing, and it's fully machine-readable.

ZUGFeRD, from version 2.0.1 onward, is technically aligned with EN 16931 and with the French Factur-X format, which it converged with at version 2.1. ZUGFeRD is a hybrid: a visible PDF layer paired with an embedded, structured XML layer carrying the same data, which is what allows a human and a system to read the same invoice.

Factur-X is the French counterpart to ZUGFeRD, and since version 2.1 the two formats are technically identical. Both meet EN 16931 through the CII syntax binding.

The practical difference is who's on the receiving end. XRechnung suits fully automated B2G and B2B processing. ZUGFeRD and Factur-X suit businesses that still need a human-readable invoice alongside the structured data, at least for now.

Three things need to be in place before EN 16931 compliance is more than a checkbox:

1. The ability to receive and validate structured invoices: German businesses have needed this since January 1, 2025. An email inbox that can accept an XML attachment technically satisfies the letter of the requirement, but it doesn't give finance a workable process for validating, routing, and archiving what comes in.
2. The ability to issue invoices in a compliant format: This means converting whatever your billing or ERP system generates into XRechnung, ZUGFeRD, or another EN 16931-compliant format, and routing it through the right channel, whether that's Peppol, a national portal, or direct exchange. For SAP customers, this is usually where sending and receiving compliant e-invoices in SAP becomes its own project.
3. An audit-proof archive: EN 16931-compliant invoices still carry statutory retention obligations, commonly 10 years under German law. Structured e-invoices need the same long-term, tamper-proof storage as any other financial record, connected to the process that created them.

Doxis Intelligent Invoice Automation covers the inbound side of this today:

Doxis classifies incoming mail, extracts invoice data, and validates it against EN 16931-compliant formats before routing it into your approval workflow and archiving it in compliance with statutory retention rules.

EN 16931 is the technical foundation ViDA (VAT in the Digital Age) builds on.

Adopted by the EU Council on March 11, 2025 and in force since April 14, 2025, ViDA is the EU's package of VAT reforms built around real-time digital reporting, and its Digital Reporting Requirements assume invoices already conform to the EN 16931 data model.

Without a shared semantic standard, real-time cross-border VAT reporting across 27 different national systems wouldn't be technically workable.

The most consequential ViDA date for cross-border e-invoicing is July 1, 2030, when structured e-invoicing and digital reporting become mandatory for intra-EU B2B transactions.

Domestic mandates, like Germany's, France's, or Poland's, are rolling out on national timelines ahead of that date, but they're all converging on formats built around the same EN 16931 core, which is precisely why the standard now matters well beyond its original B2G scope.

Germany's e-invoicing timeline

Germany's rollout under the Growth Opportunities Act runs in three phases, and the e-invoicing compliance deadlines are more layered than a single date suggests:

Getting an invoice into EN 16931-compliant shape solves the format problem, but format compliance alone doesn't answer what happens to that invoice next.

Once it's validated, it still has to be matched against a purchase order, routed to the right approver, retained for its statutory period, and retrievable years later if a tax authority asks for it.

That's a document lifecycle question, and it's where treating e-invoicing as a standalone project starts to create problems.

An invoice that lands in one system for validation, another for approval workflow, and a third for archiving means finance loses the single view of a transaction from receipt through payment through retention, and IT ends up maintaining integrations between systems that were never designed to talk to each other.

Running e-invoicing on the same platform that handles document capture, workflow, and audit-proof archiving closes that gap.

The invoice doesn't just get validated correctly, it lands in the right customer or supplier file, connects to the purchase order it belongs to, and stays retrievable for its full retention period without a separate system to check.

Doxis processes inbound invoices against EN 16931-compliant formats as part of its document management and invoice automation capabilities.

Doxis Invoice Automation classifies incoming mail, extracts the required invoice data, and routes it into your existing approval workflow, whether that invoice arrived as XRechnung, ZUGFeRD, or another structured format.

That capability sits inside Doxis Intelligent Content Automation, the platform that also handles document management, contract management, and process automation.

For SAP customers specifically, Doxis Billing for SAP converts outbound invoices generated in SAP ECC or S/4HANA into PDF, XRechnung, or ZUGFeRD and dispatches them through the Ecosio Integration Hub, while Doxis Invoice Automation for SAP matches inbound invoices against the purchase order and goods receipt already in SAP.

Both connect to the same audit-proof archive, so inbound and outbound e-invoices sit in one customer or supplier file.

With Doxis, you get:

• Automated classification and data extraction for inbound EN 16931-compliant invoices
• Outbound invoice conversion and dispatch for SAP customers, in the formats your trading partners require
• One audit-proof archive across inbound and outbound invoices, meeting statutory retention requirements
• Full traceability from invoice receipt through approval, payment, and long-term archiving
• A platform that also covers contract management, records management, and AI-driven document capture

Doxis has been recognized as a Leader in the Gartner® Magic Quadrant™ for Document Management 2026, and a Forrester Total Economic Impact™ study found that Doxis customer SEW-EURODRIVE achieved a 336% ROI with payback in under six months.

Request a free demo to see how Doxis handles EN 16931-compliant invoicing end to end.

FAQs about EN 16931