How do I fix BR-CL-19?

Invoice Navigator automatically fixes this Invoice compliance issue by updating the relevant XML elements (BR-CL-19). You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.

Is BR-CL-19 a critical error?

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

Can BR-CL-19 be automatically fixed?

Many instances of BR-CL-19 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-19`:Invalid allowance reason code

Coded allowance reasons MUST belong to the UNCL 5189 code list. This applies to AllowanceChargeReasonCode for allowances (ChargeIndicator=false).

Severity

Fatal

Rule set

EN 16931

Country

All EU

Fix type

AUTO-FIX

Confidence

85%

Engine Classification

Normalize document level allowance reason code to valid UNCL 5189 value

Confidence: 85% · Applied automatically in pipeline

What is BR-CL-19?

BR-CL-19 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 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.

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

Get API Access Test This Error ↓

Why This Error Matters

Invoice will be rejected. Allowance reason codes must use standardized UNCL 5189 values for proper processing.

BR-CL-19 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-19
·Specification: EN 16931

How to Fix It

Identify allowance

Locate AllowanceCharge with ChargeIndicator=false and invalid AllowanceChargeReasonCode

Use valid UNCL 5189 code

Replace with valid code: 95 (discount), 100 (special agreement), 41 (bonus for works ahead of schedule), 42 (other bonus)

Verify code list

Valid codes: 41, 42, 60, 62-68, 70, 71, 88, 95, 100, 102-105

Before / After

Failing XML

<Invoice>
  <!-- Issue: Coded allowance reasons MUST belong to the UNCL 5189 code li -->
</Invoice>

Corrected XML

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

Technical Reference

XPath//cac:AllowanceCharge[cbc:ChargeIndicator='false']/cbc:AllowanceChargeReasonCode

SpecEN 16931

Operationnormalize

StrategyNormalize document level allowance reason code to valid UNCL 5189 value

Common Causes

·Allowance reason code not from UNCL 5189 list
·Custom discount code used instead of standard
·Reason code contains text description not numeric code
·Legacy discount type not mapped to UNCL 5189
·AllowanceChargeReasonCode value not in allowed list

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

Handle BR-CL-19 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-19:Invalid allowance reason code