BR-CO-06:Surcharge reason text does not match the reason code
The surcharge (extra charge) reason code and the reason text on your invoice describe different types of charges. For example, code FC means "Freight" but the text says something else. These must match.
Engine Classification
Look up correct reason text from UNTDID 7161 code list based on the charge reason code
Confidence: 95% · Applied automatically in pipeline
What is BR-CO-06?
BR-CO-06 is a fatal validation rule defined in the EN 16931 specification. It validates the AllowanceChargeReason 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=true]/cbc:AllowanceChargeReason
Why This Error Matters
Semantic consistency between reason codes and text prevents ambiguity. When processing systems see code FC, they expect freight-related text. Mismatches can cause confusion in automated processing and reporting.
BR-CO-06 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-CO-06
- ·Specification: EN 16931
How to Fix It
Before / After
<cac:AllowanceCharge>\n <cbc:ChargeIndicator>true</cbc:ChargeIndicator>\n <cbc:AllowanceChargeReasonCode>FC</cbc:AllowanceChargeReasonCode>\n <cbc:AllowanceChargeReason>Handling fee</cbc:AllowanceChargeReason>\n <cbc:Amount currencyID="EUR">25.00</cbc:Amount>\n</cac:AllowanceCharge>
<cac:AllowanceCharge>\n <cbc:ChargeIndicator>true</cbc:ChargeIndicator>\n <cbc:AllowanceChargeReasonCode>FC</cbc:AllowanceChargeReasonCode>\n <cbc:AllowanceChargeReason>Freight charge</cbc:AllowanceChargeReason>\n <cbc:Amount currencyID="EUR">25.00</cbc:Amount>\n</cac:AllowanceCharge>
Technical Reference
//cac:AllowanceCharge[cbc:ChargeIndicator=true]/cbc:AllowanceChargeReasonCode Example
<cac:AllowanceCharge>\n <cbc:ChargeIndicator>true</cbc:ChargeIndicator>\n <cbc:AllowanceChargeReasonCode>FC</cbc:AllowanceChargeReasonCode>\n <cbc:AllowanceChargeReason>Freight charge</cbc:AllowanceChargeReason>\n <cbc:Amount currencyID="EUR">25.00</cbc:Amount>\n</cac:AllowanceCharge>Common Causes
- ·Copy-paste error from different charge type
- ·Code changed but text not updated
- ·Unknown UNTDID 7161 code meanings
- ·Template with placeholder text
Seeing this in production? The API handles BR-CO-06 automatically. See the fix response →
Frequently Asked Questions
BR-CO-06 occurs when the document level charge reason code (BT-105) and reason text (BT-104) describe different types of charges. They must indicate the same type according to UNTDID 7161.
Align the charge reason code with the reason text. Either update the text to match the UNTDID 7161 code meaning, or change the code to match your text description.
Yes, BR-CO-06 is a business rule violation that can cause invoice rejection. Inconsistent charge information confuses accounting reconciliation.
Partially. Invoice Navigator can suggest corrections by mapping common text patterns to UNTDID 7161 codes, but review is recommended since the correct value depends on business context.
See Also
Related Errors
Last updated: 27 February 2026
Handle BR-CO-06 Automatically in Your Pipeline
The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.