All error codes · Error code · XRechnung (KoSIT)

BR-DE-21 Wrong specification identifier

The specification identifier (BT-24) says which standard the invoice follows. For XRechnung 3.0 it is urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0.

The rule's official text

Das Element "Specification identifier" (BT-24) soll syntaktisch der Kennung des Standards XRechnung entsprechen.

The specification identifier (BT-24) should be XRechnung's, for XRechnung 3.0 "urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0".

What usually causes it

  • The invoice still uses the identifier of an old XRechnung version, such as …urn:xoev-de:kosit:standard:xrechnung_2.3.
  • It is a ZUGFeRD or Factur-X invoice in the EN 16931 profile (urn:cen.eu:en16931:2017), checked as an XRechnung.
  • A typo or a space in the identifier.

How to fix it

  1. If it is meant to be an XRechnung: enter XRechnung 3.0's identifier exactly as above.
  2. For a ZUGFeRD invoice the warning is expected when it is checked as an XRechnung. Whether the recipient accepts ZUGFeRD is for you to agree with them; German authorities usually require XRechnung.
  3. Patching an old version rarely pays off. Update the software that writes the invoice instead.

Where it sits in the XML

UBL
cbc:CustomizationID
CII
rsm:ExchangedDocumentContext/ram:GuidelineSpecifiedDocumentContextParameter/ram:ID

Fixed? Check the invoice again.

Free, no account, with the KoSIT validator. The file isn't stored.

Related error codes

All error codes

Invoices that get through. From the hours you tracked.

Try it free for 14 days

docket writes every invoice as a ZUGFeRD PDF and an XRechnung at once, following exactly these rules. More on e-invoicing in docket.