How to fix BR-DE-21
Das Element "Specification identifier" (BT-24) soll syntaktisch der Kennung des Standards XRechnung entsprechen.
XRechnung rule from the KoSIT XRechnung 3.0 schematron (German CIUS of EN 16931). It applies only to invoices whose specification identifier (BT-24) is XRechnung. Such files are checked against EN 16931 and the KoSIT XRechnung rules instead of the full Peppol BIS rule set. Check your file with the XRechnung validator.
What this rule checks
The Specification identifier (BT-24) should be the XRechnung identifier. For XRechnung 3.0 this is urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0 (the extension and CVD variants are also accepted). Our validator uses this value to decide which rules apply: files with the XRechnung identifier are checked against EN 16931 and the KoSIT XRechnung rules instead of the full Peppol BIS rule set. This rule is a warning, but many German receiving platforms reject invoices without the XRechnung identifier.
Referenced business terms
This rule references the following EN 16931 business term. Click through for the full definition, the UBL XPath and the cardinality.
How to fix it
Set cbc:CustomizationID to urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0. In CII, set rsm:ExchangedDocumentContext → ram:GuidelineSpecifiedDocumentContextParameter → ram:ID to the same value. If you send via Peppol, use the XRechnung identifier together with the Peppol ProfileID.
Common causes
- The invoice carries the Peppol BIS identifier (
urn:fdc:peppol.eu:2017:poacc:billing:3.0) instead of the XRechnung one. - An older XRechnung version is declared (for example xrechnung_2.3), which XRechnung 3.0 rules do not accept.
- The plain EN 16931 identifier
urn:cen.eu:en16931:2017was used without the XRechnung suffix. - In CII, the identifier is in the wrong element (BusinessProcess instead of GuidelineSpecifiedDocumentContextParameter).
Example: before (broken)
<Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2"
xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">
<cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_2.3</cbc:CustomizationID>
<cbc:ProfileID>urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</cbc:ProfileID>
<cbc:ID>RE-2026-0042</cbc:ID>
</Invoice>Example: after (fixed)
<Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2"
xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">
<cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0</cbc:CustomizationID>
<cbc:ProfileID>urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</cbc:ProfileID>
<cbc:ID>RE-2026-0042</cbc:ID>
</Invoice>Related rules
Validate your invoice
Upload your corrected invoice to check it passes BR-DE-21 and all other EN 16931 and XRechnung (BR-DE) rules. Free, instant, no signup.