IN-ALLOWANCE-AMOUNT-REQUIRED:Allowance/Charge amount required
AllowanceCharge elements must have an Amount element specified.
Engine Classification
Business data required · Explicit input workflow · No assumptions made
Required input: Allowance/Charge Amount
What is IN-ALLOWANCE-AMOUNT-REQUIRED?
IN-ALLOWANCE-AMOUNT-REQUIRED is a fatal validation rule defined in the peppol-bis-3 specification. It validates the Amount 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:Amount
Why This Error Matters
Amount determines value of adjustment.
IN-ALLOWANCE-AMOUNT-REQUIRED 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
- ·Rejected by PEPPOL Access Points
- ·Error returned: IN-ALLOWANCE-AMOUNT-REQUIRED
- ·Specification: peppol-bis-3
How to Fix It
Add Amount
Under AllowanceCharge
Include currency
currencyID attribute
XML Example
Generic example based on the rule's target XPath. Your actual XML structure may differ.
<!-- Missing or empty element triggers cbc:Amount error --> <cbc:Amount></cbc:Amount>
<!-- Provide the required value --> <cbc:Amount>VALID_VALUE</cbc:Amount>
Technical Reference
XPath: //cac:AllowanceCharge/cbc:AmountCommon Causes
- ·Missing Amount
- ·No currency
Seeing this in production? The API handles IN-ALLOWANCE-AMOUNT-REQUIRED automatically. See the fix response →
Frequently Asked Questions
AllowanceCharge must have Amount element.
Add Amount with currency attribute. Invoice Navigator detects this error and prompts for the required business data before applying a safe fix.
Yes, PEPPOL-EN16931-R041 is a critical error that must be fixed.
Related Content
Last updated: 3 March 2026
Resolve IN-ALLOWANCE-AMOUNT-REQUIRED with Guided Input
The compliance engine detects this error and prompts for the required business data before applying a safe, auditable fix.