BR-CO-24

What does this rule mean?

An invoice line charge (BG-28) has neither a reason (BT-144) nor a reason code (BT-145).

Without a reason the buyer can neither understand nor book the charge.

BG-28

Invoice line charges (group)

BT-144

Invoice line charge reason

BT-145

Invoice line charge reason code

Where the rule applies

Syntax: CII · UBL

The same rule, expressed twice: UBL and CII name the same fields with different paths. Running a CII file against the UBL rules is why you get errors that mean nothing.

Technical test

The rule passes when this Schematron expression holds true:

(../ram:Reason) or (../ram:ReasonCode)

How to fix it

Touches amounts, VAT or IBAN. We never change these automatically — correct them in your source data.

Add a reason as text or a code from UNCL 7161 (e.g. FC = freight).

Correct the affected entry in your XML, then re-check the invoice. Validation runs locally in your browser — your file never leaves your machine.

Related rules

• BR-CO-03Value added tax point date (BT-7) and Value added tax point date code (BT-8) are mutually exclusive.
• BR-CO-04Each Invoice line (BG-25) shall be categorized with an Invoiced item VAT category code (BT-151).
• BR-CO-05Document level allowance reason code (BT-98) and Document level allowance reason (BT-97) shall indicate the same type of allowance.
• BR-CO-06Document level charge reason code (BT-105) and Document level charge reason (BT-104) shall indicate the same type of charge.
• BR-CO-07Invoice line allowance reason code (BT-140) and Invoice line allowance reason (BT-139) shall indicate the same type of allowance reason.
• BR-CO-08Invoice line charge reason code (BT-145) and Invoice line charge reason (BT-144) shall indicate the same type of charge reason.