What the field is for
The specification's description (above, in German) translates as: "An identification of the specification containing the total set of rules regarding semantic content, cardinalities and business rules to which the data contained in the invoice conforms." With BT-24 the invoice declares which rules it follows: EN 16931, XRechnung or a ZUGFeRD profile. The field is mandatory (rule BR-01). Above all, BT-24 decides which rules a validator applies — the same file with another identifier can be checked quite differently.
The valid identifiers
| Format | BT-24 |
|---|---|
| XRechnung 3.0 | urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0 |
| XRechnung extension 3.0 | urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0#conformant#urn:xeinkauf.de:kosit:extension:xrechnung_3.0 |
| EN 16931 (also the ZUGFeRD profile EN 16931) | urn:cen.eu:en16931:2017 |
| ZUGFeRD BASIC | urn:cen.eu:en16931:2017#compliant#urn:factur-x.eu:1p0:basic |
| ZUGFeRD EXTENDED | urn:cen.eu:en16931:2017#conformant#urn:factur-x.eu:1p0:extended |
| ZUGFeRD BASIC WL | urn:factur-x.eu:1p0:basicwl |
| ZUGFeRD MINIMUM | urn:factur-x.eu:1p0:minimum |
The XRechnung identifiers are in the XRechnung specification 3.0.2, the ZUGFeRD ones in the Factur-X 1.09.2 / ZUGFeRD 2.5.2 specification. Whether BASIC WL and MINIMUM count as e-invoices in Germany is on the page ZUGFeRD profiles.
How the KoSIT check uses BT-24
KoSIT's validator configuration compares BT-24 character by character with the identifiers of XRechnung, the XRechnung extension and EN 16931, and picks the scenario by it:
- XRechnung: the EN 16931 rules plus the German rules BR-DE-*.
- EN 16931: only the EN 16931 rules — without BR-DE-* (KoSIT, issue #93).
- Any other identifier: no matching scenario. The KoSIT check does not run; our report then shows "No scenario for this profile" and checks ZUGFeRD BASIC and EXTENDED by the FeRD rules.
Where the field is in the file
| Syntax | Element |
|---|---|
| CII | rsm:ExchangedDocumentContext/ram:GuidelineSpecifiedDocumentContextParameter/ram:ID |
| UBL | cbc:CustomizationID |
Common mistakes
- Outdated identifier, e.g.
xrechnung_2.3or the earlier formurn:xoev-de:kosit:standard:xrechnung_…: the current check has no scenario for it. - Spaces or a line break around the identifier: the comparison is exact, the identifier is not recognised.
- EN 16931 declared, XRechnung required: the KoSIT check reports no BR-DE errors, but the recipient checks by XRechnung — and rejects. Other validators then report BR-DE-21.
- XRechnung declared, but mandatory fields missing: with the XRechnung identifier all BR-DE rules apply, e.g. BR-DE-15 (buyer reference).
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>
<!-- UBL -->
<cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0</cbc:CustomizationID>
Sources: KoSIT, XRechnung specification 3.0.2 (BT-24, BR-01, BR-DE-21); validator configuration XRechnung 3.0.2 (choice of scenarios); KoSIT, issue #93; Factur-X 1.09.2 / ZUGFeRD 2.5.2 (BT-24 of the profiles).