einvoice / EN 16931 / XRechnung rule reference

BR-CL-21

What this rule means and how to fix it

Item standard identifier scheme MUST be an ISO 6523 ICD code.

Die Kennung des Schemas der Artikel-Standardkennung MUSS der Codeliste ISO 6523 ICD angehören.

Deutsche Fassung: Übersetzung der gleichen BT/BG-Semantik (translation — not the official assert).

Requires
Item standard identifier scheme identifier MUST belong to the ISO 6523 ICD code list
Business terms
— (no single business term)
Syntax
Binds the UBL-2.1 Invoice / CreditNote syntax and the UN/CEFACT-CII syntax
Location (UBL-2.1 path)
cac:StandardItemIdentification/cbc:ID[@schemeID]
Fix
Encode `cac:StandardItemIdentification/cbc:ID[@schemeID]` using a valid value from ISO 6523 ICD code list.
Fix (Deutsch)
Codieren Sie `cac:StandardItemIdentification/cbc:ID[@schemeID]` mit einem gültigen Wert aus der geforderten Codeliste: Die Kennung des Schemas der Artikel-Standardkennung MUSS der Codeliste ISO 6523 ICD angehören.
Severity
fatal
Provenance source
en16931-ubl
Provenance assert

Item standard identifier scheme identifier MUST belong to the ISO 6523 ICD code list

The Location above is a UBL-2.1 path, and no UN/CEFACT-CII path for this rule is published here; Fix and Fix (Deutsch), verbatim from remediation_catalog.json and not reworded here; the UN/CEFACT-CII binding of this rule is differentially proven against the official CEN EN 16931 1.3.16 Schematron.

Where to check the fix: paste the corrected invoice into the browser validator at /einvoice/validate/ — it runs this same engine locally in your browser, with no upload, and stops reporting BR-CL-21 once the edit lands.

Korrektur prüfen: Laden Sie die geänderte Rechnung in den Browser-Validator unter /einvoice/validate/ — er führt dieselbe Engine lokal im Browser aus, ohne Upload, und meldet BR-CL-21 nicht mehr, sobald die Korrektur greift.

The same invoice, failing and fixed

No vendored test suite ships a labelled example for this rule, so this pair was found rather than written. The engine was run over the vendored instance corpus/xrechnung-testsuite/src/test/technical-cases/cius/01.01_comprehensive_test_ubl.xml under --profile xrechnung, then re-run over the same file with one mechanical edit applied to one element, over and over, until the edit below changed the verdict: the schemeID attribute of ID was changed from 0088 to ZZZ, a token that appears in no code list. The page publishes it because the engine reported BR-CL-21 for the edited document and did not report it for the untouched one.

UBL Invoice — fails

The vendored file around the change, verbatim:

<cac:StandardItemIdentification>
  <cbc:ID schemeID="ZZZ">123456789</cbc:ID>
</cac:StandardItemIdentification>

UBL Invoice — passes

The same lines as 01.01_comprehensive_test_ubl.xml actually ships them — this block is the fix for the block above:

<cac:StandardItemIdentification>
  <cbc:ID schemeID="0088">123456789</cbc:ID>
</cac:StandardItemIdentification>

What the engine reports for the edited invoice

{
  "element": "cac:StandardItemIdentification/cbc:ID/@schemeID",
  "field": "cac:StandardItemIdentification/cbc:ID/@schemeID",
  "fix_hint": "Encode `cac:StandardItemIdentification/cbc:ID[@schemeID]` using a valid value from ISO 6523 ICD code list.",
  "location": "cac:StandardItemIdentification/cbc:ID[@schemeID]",
  "message": "Item standard identifier scheme identifier MUST belong to the ISO 6523 ICD code list; 'ZZZ' is not a listed ICD.",
  "rule": "BR-CL-21",
  "severity": "fatal",
  "terms": [],
  "title": "Item standard identifier scheme MUST be an ISO 6523 ICD code."
}

Rule ids the engine reports for 01.01_comprehensive_test_ubl.xml untouched: none. After the edit, BR-CL-21 is reported that was not before.

Two honest limits. This is an edit that provokes the rule, not the only one, and it is not a claim about how real exporters break it. And it is the reverse of the fix a reader needs: the passing block is the vendored file's own content, which is what a conformant invoice looks like here.

Reproduce it yourself: take corpus/xrechnung-testsuite/src/test/technical-cases/cius/01.01_comprehensive_test_ubl.xml from this repository, apply the one edit named above, and run einvoice validate 01.01_comprehensive_test_ubl.xml --profile xrechnung --format json, or paste the file into the browser validator, which runs this same engine locally with no upload.

Everything here is free and open source — pick up whatever helps, at your own pace: