BR-DEC-05:Document level charge: max 2 decimals
Document level charge amount (BT-99) allows max 2 decimal places.
Engine Classification
Round document-level charge amount to 2 decimal places per EN16931
Confidence: 95% · Applied automatically in pipeline
What is BR-DEC-05?
BR-DEC-05 is a fatal validation rule defined in the EN 16931 specification. It validates the Amount element 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: //cac:AllowanceCharge[cbc:ChargeIndicator='true']/cbc:Amount
Why This Error Matters
Invoice will be rejected by validation. Charge amounts with improper precision fail schema validation.
BR-DEC-05 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.
Invoice Navigator can automatically correct this error in your pipeline. The fix is applied with full audit evidence, so your compliance trail remains intact.
Validator Behavior
- ·Causes invoice rejection
- ·Error returned: BR-DEC-05
- ·Specification: EN 16931
How to Fix It
Locate document charge
Find AllowanceCharge with ChargeIndicator=true at document level
Round amount
Round cbc:Amount to 2 decimal places using banker's rounding
Before / After
<cac:AllowanceCharge[ChargeIndicator=true]> <cbc:Amount>100.123456</cbc:Amount> <!-- Too many decimal places --> </cac:AllowanceCharge[ChargeIndicator=true]>
<cac:AllowanceCharge[ChargeIndicator=true]> <cbc:Amount>100.00</cbc:Amount> <!-- Correct decimal places --> </cac:AllowanceCharge[ChargeIndicator=true]>
Technical Reference
//cac:AllowanceCharge[cbc:ChargeIndicator='true']/cbc:AmountCommon Causes
- ·Charge calculated with percentage producing extra decimals
- ·ERP exports full precision without rounding
- ·Manual entry with excessive decimal places
- ·Import from external billing system
- ·Currency conversion introduced extra precision
Seeing this in production? The API handles BR-DEC-05 automatically. See the fix response →
Frequently Asked Questions
Invoice line charge amount allows max 2 decimal places.
Round line charge to 2 decimals. Invoice Navigator can help identify and fix this issue.
Yes, BR-DEC-05 is a critical error that must be fixed.
See Also
Related Errors
Last updated: 27 February 2026
Handle BR-DEC-05 Automatically in Your Pipeline
The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.