errorbusinessEN 16931

BR-CO-06:Surcharge reason text does not match the reason code

Fix: Invoice Navigator automatically fixes this issue by correcting the `cac:AllowanceCharge[cbc:ChargeIndicator=true]` element in your Invoice. Upload your invoice to fix this automatically.

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.

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

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 rejected by Peppol access points and never reaches 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 — the invoice must be corrected and re-sent before it can reach the recipient.

Validators reject invoices where the surcharge reason code and text contradict each other. Peppol access points and tax authorities may flag this as non-compliant.

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

Failing XML
<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>
Corrected XML
<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

XPath//cac:AllowanceCharge[cbc:ChargeIndicator=true]/cbc:AllowanceChargeReason
SpecEN 16931
Operationlookup
StrategyLook up correct reason text from UNTDID 7161 code list based on the charge reason code

Code 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.

Related Errors

Related Content

Last updated: 27 February 2026

Share this guide:

Validate your invoice

Drop your XML here to check for BR-CO-06

Auto-fix BR-CO-06 in seconds

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