errorbusinessEN 16931

BR-CL-20:Coded charge reasons MUST belong to the UNCL 7161 code list

Fix: A Charge Reason Code is not a valid UNCL 7161 code. Common codes: FC=freight, AAA=advertising, ABL=handling, DL=delivery. Upload your invoice to fix this automatically.

A Charge Reason Code is not a valid UNCL 7161 code. Common codes: FC=freight, AAA=advertising, ABL=handling, DL=delivery.

Severity
Fatal
Rule set
EN 16931
Country
All EU
Fix type
AUTO-FIX
Confidence
85%
Category
codelist

Engine Classification

Normalize document level charge reason code to valid UNCL 7161 value

Confidence: 85% · Applied automatically in pipeline

What is BR-CL-20?

BR-CL-20 is a fatal validation rule defined in the EN 16931 specification. It validates the AllowanceChargeReasonCode element in the UBL invoice XML.

When this rule fires, the invoice is rejected by Peppol access points and never reaches the buyer.

Target path: //cac:AllowanceCharge[cbc:ChargeIndicator='true']/cbc:AllowanceChargeReasonCode

Why This Error Matters

Invoice rejected. Charge categorization must use standard codes.

BR-CL-20 is a hard failure — the invoice must be corrected and re-sent before it can reach the recipient.

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-20
  • ·Specification: EN 16931

How to Fix It

1.

Find the incorrectly formatted value

Check cbc:AllowanceChargeReasonCode at //cac:AllowanceCharge[cbc:ChargeIndicator='true']/cbc:AllowanceChargeReasonCode. The current value does not match the required format.

2.

Apply the correct format

A Charge Reason Code is not a valid UNCL 7161 code. Common codes: FC=freight, AAA=advertising, ABL=handling, DL=delivery.

3.

Update your export settings

If this occurs consistently, check your invoicing software's locale and format settings for XML export. Re-validate to confirm BR-CL-20 is resolved.

Before / After

Failing XML
<Invoice>
  <!-- Issue: Coded charge reasons MUST belong to the UNCL 7161 code list. -->
</Invoice>
Corrected XML
<Invoice>
  <!-- Issue resolved per EN 16931 -->
</Invoice>

Technical Reference

XPath//cac:AllowanceCharge[cbc:ChargeIndicator='true']/cbc:AllowanceChargeReasonCode
SpecEN 16931
Operationnormalize
StrategyNormalize document level charge reason code to valid UNCL 7161 value

Common Causes

  • ·Charge reason code not from UNCL 7161 list
  • ·Custom surcharge code used instead of standard
  • ·Reason code contains text description not numeric code
  • ·Legacy charge type not mapped to UNCL 7161
  • ·ChargeReasonCode value not in allowed list

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

Frequently Asked Questions

A Charge Reason Code is not a valid UNCL 7161 code. Common codes: FC=freight, AAA=advertising, ABL=handling, DL=delivery.

A Charge Reason Code is not a valid UNCL 7161 code. Common codes: FC=freight, AAA=advertising, ABL=handling, DL=delivery. You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.

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

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

Related Content

Last updated: 14 April 2026

Share this guide:

Validate your invoice

Drop your XML here to check for BR-CL-20

Auto-fix BR-CL-20 in seconds

Upload your invoice and we fix this error automatically. Financial fields are never touched.