erroren16931

BR-DEC-03:Document charge: max 2 decimals

Document level charge amount allows max 2 decimal places.

Severity
Fatal
Rule set
en16931
Country
All EU
Fix type
BLOCKED

Engine Classification

Financial or legal field · Modification blocked by policy

Reason: Document level charge amounts must have maximum 2 decimal places. Automatic rounding of financial amounts could cause calculation discrepancies. Fix the charge amount in your source system to use proper 2-decimal precision before generating the invoice.

What is BR-DEC-03?

BR-DEC-03 is a fatal validation rule defined in the en16931 specification. It validates the Amount element under Invoice > 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: /Invoice/cac:AllowanceCharge[cbc:ChargeIndicator=true]/cbc:Amount

This error requires manual correction — financial fields are protected by policy.

Why This Error Matters

Monetary amounts need standard precision.

BR-DEC-03 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-DEC-03
  • ·Specification: en16931

How to Fix It

1.

Check precision

Charge Amount decimal places

2.

Round

To 2 decimal places

XML Example

Generic example based on the rule's target XPath. Your actual XML structure may differ.

Before
<!-- Missing or empty element triggers cbc:Amount error -->
<cbc:Amount></cbc:Amount>
After
<!-- Provide the required value -->
<cbc:Amount>VALID_VALUE</cbc:Amount>

Technical Reference

XPathXPath: /Invoice/cac:AllowanceCharge[cbc:ChargeIndicator=true]/cbc:Amount
Specen16931

Common Causes

  • ·Calculation creates extra decimals

Seeing this in production? The API handles BR-DEC-03 automatically. See the fix response →

Frequently Asked Questions

Document level charge amount allows max 2 decimal places.

Round charge amount to 2 decimals. Invoice Navigator can help identify and fix this issue.

Yes, BR-DEC-03 is a critical error that must be fixed.

See Also

Related Errors

Last updated: 18 January 2026

Share this guide:

Handle BR-DEC-03 Automatically in Your Pipeline

The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.