How do I fix BR-CL-23?

A Unit of Measure Code is not a valid UN/ECE Rec 20/21 code. Common codes: C62=unit, HUR=hour, KGM=kilogram, MTR=meter. You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.

Is BR-CL-23 a critical error?

Yes, BR-CL-23 is a critical error that will cause invoice rejection. It must be fixed before submission.

Can BR-CL-23 be automatically fixed?

Many instances of BR-CL-23 can be automatically corrected using Invoice Navigator's compliance engine. The fix is applied in your pipeline with full audit evidence.

errorEN 16931

`BR-CL-23`:Unit code MUST be coded according to the UN/ECE Recommendation 20 with Rec...

A Unit of Measure Code is not a valid UN/ECE Rec 20/21 code. Common codes: C62=unit, HUR=hour, KGM=kilogram, MTR=meter.

Severity

Fatal

Rule set

EN 16931

Country

All EU

Fix type

AUTO-FIX

Confidence

90%

Engine Classification

Auto-fix: Map common unit names/abbreviations to UN/ECE codes. "each"/"piece"→C62, "hour"→HUR, "kg"→KGM. Uppercase lowercase codes.

Confidence: 90% · Applied automatically in pipeline

What is BR-CL-23?

BR-CL-23 is a fatal validation rule defined in the EN 16931 specification. It checks whether unit code must be coded according to the un/ece recommendation 20 with rec....

When this rule fires, the invoice is non-compliant and will be rejected by Peppol access points and national validation services. The sending system receives a rejection response and the invoice does not reach the buyer.

Get API Access Test This Error ↓

Why This Error Matters

Invoice rejected. Quantity units must use standard codes for proper interpretation.

BR-CL-23 is a hard failure. Invoices that trigger this rule are rejected at the access point and never reach the recipient. In Peppol networks, this means your sending system receives an MLR (Message Level Response) with a rejection status. The invoice must be corrected and re-sent, adding delay to your payment cycle.

Invoice Navigator can automatically correct this error in your pipeline. The fix is applied with full audit evidence, so your compliance trail remains intact.

Validator Behavior

·Causes invoice rejection
·Error returned: BR-CL-23
·Specification: EN 16931

Before / After

Failing XML

<Invoice>
  <!-- Issue: Unit code MUST be coded according to the UN/ECE Recommendati -->
</Invoice>

Corrected XML

<Invoice>
  <!-- Issue resolved per EN 16931 -->
</Invoice>

Technical Reference

SpecEN 16931

Operationnormalize

StrategyAuto-fix: Map common unit names/abbreviations to UN/ECE codes. "each"/"piece"→C62, "hour"→HUR, "kg"→KGM. Uppercase lowercase codes.

Common Causes

·Unit code not from UN/ECE Rec 20/21 list
·Custom unit of measure code used
·Unit stored as text (pieces) not code (C62)
·unitCode attribute contains invalid value
·Legacy unit codes not mapped to UN/ECE standard

Seeing this in production? The API handles BR-CL-23 automatically. See the fix response →

Handle BR-CL-23 Automatically in Your Pipeline

The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.

Get API Access View API Documentation

BR-CL-23:Unit code MUST be coded according to the UN/ECE Recommendation 20 with Rec...