BR-58:Document charge must have reason
Document level charge must have reason code or text.
Engine Classification
Business data required · Explicit input workflow · No assumptions made
Required input: Charge Reason Code, Charge Reason Description
What is BR-58?
BR-58 is a fatal validation rule defined in the en16931 specification. It validates the AllowanceCharge element under Invoice in the UBL invoice XML.
When this rule fires, the invoice is non-compliant and will be rejected by Peppol access points and national validation services. The sending system receives a rejection response and the invoice does not reach the buyer.
Target path: XPath: /Invoice/cac:AllowanceCharge[cbc:ChargeIndicator=true]
Why This Error Matters
Charge reasons required for proper accounting and VAT treatment.
BR-58 is a hard failure. Invoices that trigger this rule are rejected at the access point and never reach the recipient. In Peppol networks, this means your sending system receives an MLR (Message Level Response) with a rejection status. The invoice must be corrected and re-sent, adding delay to your payment cycle.
Validator Behavior
- ·Causes invoice rejection
- ·Fails EN 16931 business rule validation
- ·Error returned: BR-58
- ·Specification: en16931
How to Fix It
Find document charge
ChargeIndicator=true at document level
Add reason code
Common codes: FC (freight), FI (financing)
XML Example
Generic example based on the rule's target XPath. Your actual XML structure may differ.
<!-- Required block is missing --> <!-- <cac:AllowanceCharge> ... </cac:AllowanceCharge> -->
<!-- Add the required block --> <cac:AllowanceCharge> <!-- child elements --> </cac:AllowanceCharge>
Technical Reference
XPath: /Invoice/cac:AllowanceCharge[cbc:ChargeIndicator=true]Common Causes
- ·Shipping charge without code
- ·Service fee missing reason
Seeing this in production? The API handles BR-58 automatically. See the fix response →
Frequently Asked Questions
Document level charge must have reason code or text.
Add AllowanceChargeReasonCode from UNCL7161 code list. You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.
Yes, BR-58 is a critical error that will cause invoice rejection. It must be fixed before submission to ensure your invoice is accepted by the recipient's system.
Many instances of BR-58 can be automatically corrected using Invoice Navigator's Fixer tool. Upload your invoice and the tool will identify and fix common issues, including document charge must have reason.
See Also
Related Errors
Last updated: 18 January 2026
Handle BR-58 Automatically in Your Pipeline
The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.