The standard

EN 16931: the standard every German e-invoice is built on

XRechnung and ZUGFeRD are two formats with one content: the data model of the European standard EN 16931. What the standard lays down, which parts it has, what the 2026 edition changes, and which of its rules a validator actually evaluates today.

What the standard lays down

EN 16931 is not a file format. It describes which information an invoice carries and how it fits together — seller, buyer, lines, VAT, totals — as a list of numbered business terms: BT-1 is the invoice number, BT-5 the currency, BT-10 the buyer reference. On top come business rules that say what is mandatory and what has to agree with what.

Only the syntax turns that into a file. The standard permits two, UBL 2.1 and UN/CEFACT CII D16B, and fixes for both which XML element each business term goes in. An XRechnung in UBL and one in CII are therefore the same content in two spellings, and a ZUGFeRD PDF carries the CII one inside it.

It came out of Directive 2014/55/EU: public buyers in the EU have had to accept e-invoices under this standard since 2019 (central bodies) and 2020 (everyone else). German VAT law has built on it since 2025: an e-invoice under § 14 UStG conforms to the European standard and its list of syntaxes — or to a format the parties agree on that is interoperable with it.

The parts of the standard

PartContentEdition
EN 16931-1The semantic data model: every business term (BT) and group (BG), with the business rules.2026, before that 2017 + A1:2019
CEN/TS 16931-2The list of permitted syntaxes: UBL 2.1 and UN/CEFACT CII D16B.2017
CEN/TS 16931-3-1 … 3-4How the model maps onto the syntaxes: methodology, UBL, CII, EDIFACT.2017; UBL and CII revised in 2020, UBL again in 2026
CEN/TS 16931-5How sectors and countries build extensions that go beyond the model.2025
CEN/TS 16931-7How a usage specification (CIUS) such as XRechnung is developed and published.2020

Parts 1 and 2 are the standard proper; part 3 is for whoever writes or reads the files. Since 2025 further parts have been added, among them a register of usage specifications and a volume of worked examples.

The 2026 edition

In spring 2026 CEN adopted a new edition of part 1, EN 16931-1:2026. It replaces the 2017 edition with its 2019 amendment and, according to the European Commission, adds to the model what automated VAT reporting under ViDA needs. The German edition is DIN EN 16931-1:2026-10.

For an invoice you send today, that changes nothing yet. The Commission writes that the 2017 edition, though formally withdrawn, stays compliant during the migration period, and the migration plans are still being drawn up. CEN’s official validation rules (version 1.3.17 of October 2026) and XRechnung 3.0 are both built on the 2017 model.

Every invoice states which edition it was built against, in the specification identifier (BT-24): urn:cen.eu:en16931:2017. That is how it begins in every file our generator writes, the XRechnung included, whose identifier merely appends the usage specification.

Where to get the standard

The 2017 edition was free: the European Commission had agreed with CEN that parts 1 and 2 be given away “for the duration of the current version”. With the new edition that has ended until the agreement is renewed. DIN EN 16931-1:2026-10 costs DIN Media €366.20 as a German PDF at DIN Media (as of 25 October 2026). The syntax list, CEN/TS 16931-2, is still free.

For practical work you rarely need the text of the standard. KoSIT’s XRechnung specification restates the model with every business term, freely available, and the validation rules are open: CEN publishes its own as Schematron on GitHub, and our error index explains the rules evaluated in Germany in plain language.

Which rules a validator evaluates

KoSIT’s German rule set, version v2026-08-31, checks 307 business rules. Counted from the rule set our validator ships — by origin:

EN 16931 (CEN)223 rules

Required content, calculations, code lists, decimal places and ten to fourteen rules per VAT category. Applies to every e-invoice, ZUGFeRD included.

BR 58BR-CL 23BR-CO 23BR-DEC 21BR-O 14BR-IC 12BR-AE 10BR-AF 10BR-AG 10BR-E 10BR-G 10BR-S 10BR-Z 10BR-B 2

XRechnung (KoSIT)61 rules

The German additions, such as the buyer reference and contact details made mandatory, plus the XRechnung extension. Only for invoices meant to be an XRechnung.

BR-DE 31BR-DEX 15BR-DE-CVD 7BR-TMP 6BR-DE-TMP 1BR-TMP-CVD 1

Peppol (OpenPeppol)23 rules

Rules from Peppol BIS Billing 3.0 that the XRechnung configuration carries along.

PEPPOL-EN16931 23

Ahead of these rules sits the syntax check: whether the file is valid UBL or CII at all and contains only permitted elements. The rules themselves change with every release of the rule set — what changed last is in the changelog.

Usage specification and extension

The standard is deliberately broad. Countries and sectors may adapt it in two ways, and the invoice says in BT-24 which one was chosen.

Core invoice usage specification (CIUS)
Restricts and clarifies without adding anything: every invoice under the CIUS is also a valid invoice under the standard. XRechnung is one, as is Peppol BIS Billing 3.0. Identifier: urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0
Extension
Adds fields the standard does not know, and is therefore only “conformant”, not “compliant”. ZUGFeRD EXTENDED is the best-known example — why an authority refuses it is on the page ZUGFeRD Extended or XRechnung.

What ViDA makes of it from 2030

With Directive (EU) 2025/516 (“VAT in the Digital Age”, in force since 14 April 2025) the standard goes from the standard for invoices to public bodies to the standard for everyone. Since then member states may require e-invoicing at home without a derogation. From 1 July 2030 e-invoices must in principle conform to EN 16931 and its list of syntaxes — states may allow other formats for domestic supplies — and digital reporting begins for business-to-business supplies between EU countries.

Common questions

Is every EN 16931 invoice an XRechnung?

No, the other way round: every XRechnung is an EN 16931 invoice, but not every EN 16931 invoice meets the German additions. XRechnung makes, for example, the buyer reference and the seller’s contact details mandatory. For an authority that matters; between businesses the standard is enough.

Which format should I choose, then?

The recipient decides that, not the standard. When XRechnung fits and when ZUGFeRD, with one invoice in both formats to compare: XRechnung or ZUGFeRD.

Where do I see what a single field means?

In the field index, with the XML element in UBL and CII and the rules that check the field.

Check an invoice against exactly these rules — the report names every rule broken, with an explanation. Or generate conforming invoices from JSON through the API.

Sources: European Commission, standard and specifications (as of 24 June 2026); obtaining the standard; Directive (EU) 2025/516. Read on 25 October 2026. This page restates the standard; the text of the standard governs.