BR-CL-23Unit code isn't a UN/ECE Recommendation 20 code

ErrorEN 16931BT-130BT-150

What it means

Every quantity carries a unit code, and EN 16931 only accepts codes from UN/ECE Recommendation 20 (with the Rec 21 extension), such as C62 for ‘one’, HUR for hour or KGM for kilogram. Words like ‘pcs’, ‘st’, ‘uur’ or ‘h’ are not codes and fail this rule.

Official message

Rejects the invoice (fatal)
[BR-CL-23]-Unit code MUST be coded according to the UN/ECE Recommendation 20 with Rec 21 extension

EN 16931 validation artefacts 1.3.17, CEN/TC 434, released 12 October 2026 · Read the rule at the source

Peppol BIS 3.0.22 runs these EN 16931 checks with the CEN artefacts 1.3.16; the message is the same.

Text compared with the published file on 17 November 2026.

Direct fix

Use a code from UN/ECE Recommendation 20/21: unitCode="C62" (one) or "H87" (piece) for items, HUR for hours, DAY for days, MON for months, KGM for kilograms, MTR for metres, LTR for litres.

Typical causes

  • The unit is exported as the software's own abbreviation: PCE, PC, ST, pcs, UUR, h.
  • A code in lowercase (c62, hur): the list check is exact.
  • Units typed by users in the article master are passed through without mapping.

How to fix it

  1. Map each unit in your software to a Rec 20 code: C62 or H87 for pieces, HUR for hours, DAY for days, KGM for kilograms, LTR for litres, MTR for metres.
  2. Write the code in capitals, exactly as listed.
  3. Check the BaseQuantity unit too: it follows the same list.

Before and after

A real invoice from our sample library, cut down to the lines that matter. The first version fails BR-CL-23; the second passes.

The line's quantity uses PCE, which isn't on the UN/ECE list.

Before: fails BR-CL-23
<cbc:InvoicedQuantity unitCode="PCE">10</cbc:InvoicedQuantity>
After: passes
<cbc:InvoicedQuantity unitCode="C62">10</cbc:InvoicedQuantity>

It’s one of our sample files, so checking it doesn’t count towards your free validations.

Check your invoice for BR-CL-23

Open the free validator with BR-CL-23 already explained: paste or upload your XML and the finding, if any, is highlighted with its exact line.

Check my invoice

3 free validations a month without an account. Invoice contents are never stored.

Where validators check it

For developers and software suppliers: the test exactly as the official Schematron runs it. The validator applies it to every element that matches the context and reports the rule wherever the test comes out false.

UBL 2.1BR-CL-23
Runs on (context)
cbc:InvoicedQuantity[@unitCode] | cbc:BaseQuantity[@unitCode] | cbc:CreditedQuantity[@unitCode]
Test
((not(contains(normalize-space(@unitCode), ' ')) and contains(' … ', concat(' ', normalize-space(@unitCode), ' '))))

The list of 2162 allowed codes is shortened to ' … ' here; the full list is in the official file.

Copied from EN16931-UBL-codes.sch, EN 16931 validation artefacts 1.3.17. Text compared with the published file on 17 November 2026.

UN/CEFACT CIIBR-CL-23
Runs on (context)
ram:BasisQuantity[@unitCode] | ram:BilledQuantity[@unitCode]
Test
((not(contains(normalize-space(@unitCode), ' ')) and contains(' … ', concat(' ', normalize-space(@unitCode), ' '))))

The list of 2162 allowed codes is shortened to ' … ' here; the full list is in the official file.

Copied from EN16931-CII-codes.sch, EN 16931 validation artefacts 1.3.17. Text compared with the published file on 17 November 2026.

What the rule says (technical)

Unit code MUST be coded according to the UN/ECE Recommendation 20 with Rec 21 extension.

Replace the unit with a Rec 20 / Rec 21 code: C62 (one/piece), H87 (piece), HUR (hour), DAY (day), KGM (kilogram), LTR (litre), MTR (metre).

More errors with a worked fix

Related rules