The document-level allowance or charge indicator is neither “true” nor “false”
In CII syntax, `ram:ChargeIndicator/udt:Indicator` must be exactly `true` or `false` on document-level and line-level allowances and charges.
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.
Allowance/charge ChargeIndicator value MUST equal 'true' or 'false'
Quoted from schematron-xrechnung 3.0.2, licensed under Apache-2.0.
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 same requirement as `PEPPOL-EN16931-R043`, applied to allowances and charges declared in `SpecifiedTradeAllowanceCharge`. The package splits the two CII locations into two codes so the report can say which one is at fault.
How to fix it
Have your generator write `true` or `false`. Factlint does not normalise this value: it governs the direction of an amount.
XML correction example
<ram:ChargeIndicator><udt:Indicator>1</udt:Indicator></ram:ChargeIndicator>
<ram:ChargeIndicator><udt:Indicator>false</udt:Indicator></ram:ChargeIndicator>