A charge states no reason
Each document level charge (BG-21) must carry a reason in plain text (BT-104), a reason code (BT-105), or both.
Only the issuer holds this value: Factlint reports it and never fabricates it. Test your invoice to find out whether it is affected.
The message your validator prints
Copied verbatim from the sealed artefact: this is the exact sentence the check prints when this rule fails.
[BR-CO-22]-Each Document level charge (BG-21) shall contain a Document level charge reason (BT-104) or a Document level charge reason code (BT-105), or both.
Quoted from schematron-cen 1.3.16, licensed under EUPL-1.2.
Common searches around this code
These phrases mirror what an integrator searches for: code, syntax, rule, business field and correction.
Test your file with this error in mind
Upload the invoice involved: the report will say whether this code appears, where it appears in the document, and whether Factlint can only report it or also fix it.
To automate this check in an ERP flow, call the validation API and link every returned code to its public page.
Why this error happens
The typical case is freight added by a shipping module, which knows the amount but not the billing nomenclature. The amount reaches the document, the reason stays in the shipping system.
How to fix it
Add either one on the reported group. For freight, the dedicated UNCL 7161 code avoids free text that every recipient will read their own way.
XML correction example
<ram:SpecifiedTradeAllowanceCharge> <ram:ActualAmount>12.50</ram:ActualAmount> </ram:SpecifiedTradeAllowanceCharge>
<ram:SpecifiedTradeAllowanceCharge> <ram:ActualAmount>12.50</ram:ActualAmount> <ram:ReasonCode>FC</ram:ReasonCode> </ram:SpecifiedTradeAllowanceCharge>