BR-CL-01
The document type code MUST be coded by the invoice and credit note related code lists of UNTDID 1001.
What does this rule mean?
The document type code (BT-3) is not a valid value from the UNTDID 1001 code list.
The code tells the receiver whether this is e.g. an invoice (380) or credit note (381) — only UNTDID 1001 values are allowed.
Official rule message (standard)
The document type code MUST be coded by the invoice and credit note related code lists of UNTDID 1001.
Where the rule applies
Syntax: CII · UBL
The same rule, expressed twice: UBL and CII name the same fields with different paths. Running a CII file against the UBL rules is why you get errors that mean nothing.
UBL
cbc:InvoiceTypeCode | cbc:CreditNoteTypeCode
CII
rsm:ExchangedDocument/ram:TypeCode
Technical test
The rule passes when this Schematron expression holds true:
((not(contains(normalize-space(.), ' ')) and contains(' 71 80 81 82 83 84 102 130 202 203 204 211 218 219 261 262 295 296 308 325 326 331 380 381 382 383 384 385 386 387 388 389 390 393 394 395 396 420 456 457 458 471 472 473 500 501 502 503 527 532 553 575 623 633 751 780 817 870 875 876 877 935 ', concat(' ', normalize-space(.), ' '))))How to fix it
A wrong code-list value. A tool can suggest a valid code, but you confirm the correct one.
Use a valid UNTDID 1001 code (e.g. 380 for a commercial invoice).
Correct the affected entry in your XML, then re-check the invoice. Validation runs locally in your browser — your file never leaves your machine.
Check an e-invoice here
Drop an XML or ZUGFeRD PDF file here. Validation runs locally in your browser against EN 16931 — your file never leaves your machine.