BR-59:Allowance base amount required when percentage used
If allowance/charge has percentage, base amount is mandatory.
Engine Classification
Business data required · Explicit input workflow · No assumptions made
Required input: Base Amount
What is BR-59?
BR-59 is a fatal validation rule defined in the en16931 specification. It validates the MultiplierFactorNumeric requires BaseAmount element under AllowanceCharge 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: //cac:AllowanceCharge/cbc:MultiplierFactorNumeric requires BaseAmount
Why This Error Matters
Base amount needed to verify percentage calculations.
BR-59 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-59
- ·Specification: en16931
How to Fix It
Check for percentage
If MultiplierFactorNumeric exists
Add base amount
Amount = BaseAmount × Percentage / 100
XML Example
Generic example based on the rule's target XPath. Your actual XML structure may differ.
<!-- Missing or empty element triggers cbc:MultiplierFactorNumeric requires BaseAmount error --> <cbc:MultiplierFactorNumeric requires BaseAmount></cbc:MultiplierFactorNumeric requires BaseAmount>
<!-- Provide the required value --> <cbc:MultiplierFactorNumeric requires BaseAmount>VALID_VALUE</cbc:MultiplierFactorNumeric requires BaseAmount>
Technical Reference
XPath: //cac:AllowanceCharge/cbc:MultiplierFactorNumeric requires BaseAmountCommon Causes
- ·Percentage discount without base
- ·Template configuration error
Seeing this in production? The API handles BR-59 automatically. See the fix response →
Frequently Asked Questions
If allowance/charge has percentage, base amount is mandatory.
Add BaseAmount element when using percentage-based allowances. Invoice Navigator detects this error and prompts for the required business data before applying a safe fix.
Yes, BR-59 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-59 requires specific business data to resolve. Invoice Navigator detects the error and guides you through providing the needed information, then applies the fix with full audit documentation.
Related Content
Last updated: 3 March 2026
Resolve BR-59 with Guided Input
The compliance engine detects this error and prompts for the required business data before applying a safe, auditable fix.