BR-DE-21: Specification identifier (BT-24) is not an XRechnung identifier
Severity: warning · Syntax: CII, UBL
Official message
Das Element "Specification identifier" (BT-24) soll syntaktisch der Kennung des Standards XRechnung entsprechen.
What this means
BT-24 should syntactically be an XRechnung identifier. Severity warning. The assertion accepts exactly three values: urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0, urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0#conformant#urn:xeinkauf.de:kosit:extension:xrechnung_3.0 or urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0#compliant#urn:xeinkauf.de:kosit:xrechnung:cvd_0.9. A plain EN 16931 identifier without the XRechnung suffix passes BR-01, but not BR-DE-21.
Typical cause
CustomizationID contains urn:cen.eu:en16931:2017 without the XRechnung part, or an older version number.
How to fix it
Set the identifier of the variant you are actually issuing. For standard XRechnung 3.0, the CIUS value.
UBL
<cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0</cbc:CustomizationID>CII
<ram:ID>urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0</ram:ID>Business term
Specification identifier (BT-24)
Related rules
Context and assertion
UBL /ubl:Invoice | /cn:CreditNote
CII /rsm:CrossIndustryInvoice/rsm:ExchangedDocumentContext
UBL
cbc:CustomizationID = $XR-CIUS-ID or cbc:CustomizationID = $XR-EXTENSION-ID or cbc:CustomizationID = $XR-CVD-IDCII
ram:GuidelineSpecifiedDocumentContextParameter/ram:ID = $XR-CIUS-ID or ram:GuidelineSpecifiedDocumentContextParameter/ram:ID = $XR-EXTENSION-ID or ram:GuidelineSpecifiedDocumentContextParameter/ram:ID = $XR-CVD-IDCheck a file now, free of charge
curl -F "file=@rechnung.xml" https://checkxrechnung.com/v1/validate
Questions
What does BR-DE-21 actually check?
BT-24 should syntactically be an XRechnung identifier. Severity warning. The assertion accepts exactly three values: urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0, urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0#conformant#urn:xeinkauf.de:kosit:extension:xrechnung_3.0 or urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0#compliant#urn:xeinkauf.de:kosit:xrechnung:cvd_0.9. A plain EN 16931 identifier without the XRechnung suffix passes BR-01, but not BR-DE-21.
How do I fix BR-DE-21?
Set the identifier of the variant you are actually issuing. For standard XRechnung 3.0, the CIUS value.
If BR-DE-21 passes, is the invoice legally compliant?
No. This page helps you read this one Schematron assertion. A pass is not a statement about tax law, portal acceptance, or bank overlays.