errorpeppol-bis-3
BR-43:Allowance/charge reason required
Document and line allowances/charges must include a reason.
Fix this in your source system
MANUALAllowance/charge reasons affect accounting treatment and tax reporting. The reason must accurately reflect the business purpose.
See the step-by-step instructions below to fix this error manually.
Why This Error Matters
Invoice rejected. Cannot calculate line total without knowing charge amount.
How to Fix It
1
Add reason code
UNCL5189 for allowances, UNCL7161 for charges
2
Add reason text
Clear description of discount/charge
3
Common codes
95=discount, 100=special agreement, 64=delivery charge
Code Example
<cac:AllowanceCharge>
<cbc:ChargeIndicator>false</cbc:ChargeIndicator>
<cbc:AllowanceChargeReasonCode>95</cbc:AllowanceChargeReasonCode>
<cbc:AllowanceChargeReason>Volume discount</cbc:AllowanceChargeReason>
<cbc:Amount currencyID="EUR">100.00</cbc:Amount>
</cac:AllowanceCharge>Technical Details
XPath: //cac:AllowanceCharge/cbc:AllowanceChargeReasonCommon Causes
- Line charge added without amount value
- AllowanceCharge/Amount not mapped for line charges
- Percentage line surcharge without base amount
- Line charge template missing amount mapping
- Null amount for line-level surcharge
Commonly Seen In
All invoicing software
Frequently Asked Questions
Document and line allowances/charges must include a reason.
Add reason text and code to allowances/charges. You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.
Yes, BR-43 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-43 can be automatically corrected using Invoice Navigator's Fixer tool. Upload your invoice and the tool will identify and fix common issues, including allowance/charge reason required.
BR-43 is commonly seen in exports from All invoicing software. These software packages sometimes generate invoices that need adjustment to meet full compliance standards.
Related Errors
Last updated: 18 January 2026
Share this guide: