errorbusinessen16931

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

Fix: Round charge amount to 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 rejected by Peppol access points and never reaches 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 — the invoice must be corrected and re-sent before it can reach the recipient.

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. This error involves a protected field — Invoice Navigator flags it in your pipeline so your team can correct it at the source.

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

Related Errors

BR-DEC-01Document allowance: max 2 decimalsBR-DEC-02Document allowance base: max 2 decimals

Related Content

Learn
What is Peppol?
Glossary
Evidence Packe-Reporting
Answers
What is the difference between B2G and B2B e-invoicing?
Blog
The 10 Most Common E-Invoice Errors in 2026 (and How to Fix Each One)Belgium E-Invoicing After the Grace Period: What ERP Vendors Need to Know
Validators
XRechnung ValidatorZUGFeRD Validator

Last updated: 3 March 2026

Share this guide:

Validate your invoice

Drop your XML here to check for BR-DEC-03

Detect BR-DEC-03 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.

Fix it nowAutomate via API