BR-CO-08: Line charge reason code and text agree

The reason code (BT-145) and reason text (BT-144) of a line charge must describe the same charge. Below: the message, the cause and the fix.

The message validators print

BR-CO-08 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-08]-Invoice line charge reason code (BT-145) and Invoice line charge reason (BT-144) shall indicate the same type of charge reason.

What it checks

The reason code (BT-145) and reason text (BT-144) of a line charge must describe the same charge. Like BR-CO-05 to 07, it is an assertion the published files hold as always true.

Why invoices fail it

A line surcharge carries an unrelated code.

How to fix it

Make the UNTDID 7161 code match the text, 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: //cac:InvoiceLine/cac:AllowanceCharge[cbc:ChargeIndicator = true()] | //cac:CreditNoteLine/cac:AllowanceCharge[cbc:ChargeIndicator = true()]
test:    true()
CII · CEN EN 16931 validation artefacts (CII) 1.3.16 · assert · error
context: //ram:SpecifiedLineTradeSettlement/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