What the rule requires
The specification identifier (BT-24) states which rules the invoice is built by. An XRechnung 3.0 carries, according to the specification:
urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0
The XRechnung extension has its own, longer identifier. BR-DE-21 is a warning.
Why one validator reports BR-DE-21 and another does not
KoSIT's validator configuration picks the rules by BT-24. If it holds the EN 16931 identifier
(urn:cen.eu:en16931:2017), as with ZUGFeRD in the EN 16931 profile, it checks only the EN 16931
rules — without the German BR-DE rules. KoSIT explained this in its repository in August 2024
(issue #93).
Other validators apply the XRechnung rules to every invoice. Then BR-DE-21 appears, often together with BR-DE errors such as BR-DE-15 that the KoSIT check did not test at all. The same file is then "valid" or "invalid" depending on the tool.
What to do
What matters is what the recipient requires:
- They require an XRechnung (e.g. every public authority): BT-24 must carry the XRechnung identifier and the invoice must meet all BR-DE rules.
- They accept an invoice by EN 16931 (e.g. ZUGFeRD in the EN 16931 profile): then the warning of a validator that applies XRechnung rules does not matter for this invoice.
If BT-24 holds an outdated identifier (e.g. xrechnung_2.3), the current KoSIT check finds no
matching rules — our report then shows "No scenario for this profile".
Example (CII)
<rsm:ExchangedDocumentContext>
<ram:GuidelineSpecifiedDocumentContextParameter>
<ram:ID>urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0</ram:ID> <!-- BT-24 -->
</ram:GuidelineSpecifiedDocumentContextParameter>
</rsm:ExchangedDocumentContext>
Sources: KoSIT, XRechnung specification 3.0.2 (BT-24, rule BR-DE-21); validator configuration XRechnung 3.0.2 (choice of the check by BT-24); KoSIT, issue #93.