Reference

BR-CL-08 Invoice note subject code must come from UNCL4451

When an invoice note (BT-22) carries a subject code (BT-21), that code must belong to the UNCL4451 list used by EN 16931.

In UBL, the validator reads the text between the first two hash signs of a note as a subject code, but only when it is exactly three characters long. A lowercase code ("#aai#") or a three-character code outside the list ("#XYZ#") therefore fails, while a single hash sign in free text, such as "Delivery note #4711", does not. In CII, every ram:SubjectCode is checked. Example: "#AAI#Please quote the order number" passes.

Solution

In UBL, put the code in capital letters between two hash signs at the start of cbc:Note, e.g. "#AAI#General information" or "#REG#...". In CII, put the code in ram:IncludedNote/ram:SubjectCode. A note without a subject code is also valid.

Quick actions

Validate XML Convert invoice

Valid Examples

Note = "#AAI#General information"
Note = "Delivery note #4711" — a single hash sign is not read as a code

Invalid Examples

Note = "#XYZ#..." — XYZ is not a UNCL4451 code
Note = "#aai#..." — lowercase; codes are case-sensitive

Code Examples

Valid XML

<cbc:Note>#AAI#General information for the buyer</cbc:Note>

Invalid XML

<cbc:Note>#XYZ#General information for the buyer</cbc:Note>

Affected Fields

BT-21 Invoice note subject code

Validation Tools

Official KoSIT Validator

Run the official KoSIT validator with the XRechnung configuration to check EN 16931 and XRechnung rules.

Convert PDF to XRechnung

Find validation errors during conversion and review each correction.