BR-43:Allowance/charge reason required
Fix: Add the required `cac:AllowanceCharge` element to your Invoice. Ensure it contains a valid value per EN 16931 (BR-43).
Each Invoice line charge (BG-28) shall have an Invoice line charge amount (BT-141).. Check the `cac:AllowanceCharge` element in your invoice XML.
Engine Classification
Financial or legal field · Modification blocked by policy
Reason: Allowance/charge reasons affect accounting treatment and tax reporting. The reason must accurately reflect the business purpose.
What is BR-43?
BR-43 is a fatal validation rule defined in the EN 16931 specification. It validates the AllowanceChargeReason element under AllowanceCharge in the UBL invoice XML.
When this rule fires, the invoice is rejected by Peppol access points and never reaches the buyer.
Target path: XPath: //cac:AllowanceCharge/cbc:AllowanceChargeReason
Why This Error Matters
Invoice rejected. Cannot calculate line total without knowing charge amount.
BR-43 is a hard failure — the invoice must be corrected and re-sent before it can reach the recipient.
Validator Behavior
- ·Causes invoice rejection
- ·Error returned: BR-43
- ·Specification: EN 16931
How to Fix It
Add reason code
UNCL5189 for allowances, UNCL7161 for charges
Add reason text
Clear description of discount/charge
Common codes
95=discount, 100=special agreement, 64=delivery charge
Before / After
<cac:InvoiceLine> <!-- cac:AllowanceCharge is missing --> </cac:InvoiceLine>
<cac:InvoiceLine> <cac:AllowanceCharge>valid-value</cac:AllowanceCharge> </cac:InvoiceLine>
Technical Reference
XPath: //cac:AllowanceCharge/cbc:AllowanceChargeReasonCode 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>Common 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
Seeing this in production? The API handles BR-43 automatically. See the fix response →
Commonly Seen In
Frequently Asked Questions
Document and line allowances/charges must include a reason.
Add the required `cac:AllowanceCharge` element to your Invoice. Ensure it contains a valid value per EN 16931 (BR-43). This error involves a protected field — Invoice Navigator flags it in your pipeline so your team can correct it at the source.
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.
BR-43 involves a financial or legal field that cannot be auto-modified by policy. Invoice Navigator detects and flags this error immediately, but the correction must be made manually in your ERP or invoicing software.
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
Related Content
Last updated: 3 March 2026
Validate your invoice
Drop your XML here to check for BR-43
Detect BR-43 before submission
This error involves a financial field that can't be auto-modified. We'll flag it with a clear diagnosis so you can fix it at the source.