einvoice / EN 16931 / XRechnung rule reference

Rule index

Every EN 16931 / XRechnung business rule the einvoice engine can fire, grouped by rule family, one row per rule. The row gives you the answer most lookups actually need — engine severity, profile, the BT/BG business terms the rule touches and the XML location it points at. The rule id links to that rule's own page, which adds the one-line fix in English and German and the verbatim official Schematron assert.

297 rules in total — 284 fatal, 12 warning, 1 information — across 21 families. Family headings are the standard EN 16931 / XRechnung rule-family labels; every cell below is rendered from the remediation catalog the engine itself validates against. The bindings are not uniform: 281 of the 297 bind both invoice syntaxes, 12 of the 297 bind UBL-2.1 only and 4 of the 297 bind UN/CEFACT-CII only, as published per rule id in export/rules.json and shown in the Syntax column. Back to the overview.

Profile says which artifact asserts the rule: en16931 for the 198 rules that come from the EN 16931 UBL Schematron (they fire for any EN 16931 invoice), xrechnung for the 99 that come from the German KoSIT XRechnung Schematron (they fire only when the invoice claims an XRechnung customization). Severity is what the engine does: fatal fails the run, warning and information are reported without failing it unless you raise the threshold. Syntax is which invoice syntax the rule binds, joined on rule id from export/rules.json: a cell naming both UBL-2.1 and UN/CEFACT-CII means the rule fires against either, a cell naming one means it fires only against that one — so a shop that emits a single syntax can see which rows are its own. XML location is the element the rule is anchored to, written as the UBL/CII path fragment the report prints.

Every row has a stable anchor equal to its rule id, so https://verifyhash.com/einvoice/rules/#BR-DE-15 opens this page at that rule — usable in a support reply, a ticket or a CI log.