BR-CO-06: Charge reason code and text agree

The reason code of a document-level charge (BT-105, UNTDID 7161) and its reason text (BT-104) must describe the same kind of charge. Below: the message, the cause and the fix.

The message validators print

BR-CO-06 is a rule of the EN 16931 business rules (CEN validation artefacts 1.3.16) for UBL and CII. It is an error (fatal): a validator rejects the invoice.

UBL and CII
[BR-CO-06]-Document level charge reason code (BT-105) and Document level charge reason (BT-104) shall indicate the same type of charge.

What it checks

The reason code of a document-level charge (BT-105, UNTDID 7161) and its reason text (BT-104) must describe the same kind of charge. As with BR-CO-05, the published files express this as an assertion that always holds: no validator reports it.

Why invoices fail it

A code such as FC (freight) is paired with a text describing another charge.

How to fix it

Use the UNTDID 7161 code that matches the text (FC freight, ABL packaging, ZZZ mutually defined), or send the text alone.

Why no validator reports it

The published files write the test as true(): whether a code and a text mean the same thing is beyond what a schematron rule can check. No invoice can fail it, so there is no checked example; the standard’s requirement holds all the same.

The rule as published

Where the rule applies (context) and what must hold (test), unmodified from CEN EN 16931 validation artefacts 1.3.16. An assert fails when its test is false.

Text and test: © CEN/TC 434, EN 16931 validation artefacts, EUPL 1.2. Quoted unmodified; the explanations on this page are Veriport’s.

UBL · CEN EN 16931 validation artefacts (UBL) 1.3.16 · assert · error
context: /ubl:Invoice/cac:AllowanceCharge[cbc:ChargeIndicator = true()] | /cn:CreditNote/cac:AllowanceCharge[cbc:ChargeIndicator = true()]
test:    true()
CII · CEN EN 16931 validation artefacts (CII) 1.3.16 · assert · error
context: //ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeAllowanceCharge/ram:ChargeIndicator[udt:Indicator='true']
test:    true()

Check your own invoice

Drop your XRechnung, ZUGFeRD or Peppol file into a free validator (Peppol BIS, XRechnung, Factur-X): each runs the same rule files and links every finding to its rule page. From your own code, POST /einvoice/validate (reference) returns the same check as JSON, each finding with an explanation field pointing here (5 calls a check, anonymous within the daily allowance).

Sources