errorEN 16931

BR-DEC-06:Document level charge base: max 2 decimals

Document level charge base amount (BT-100) allows max 2 decimal places.

Severity
Fatal
Rule set
EN 16931
Country
All EU
Fix type
AUTO-FIX
Confidence
95%
Category
calculation

Engine Classification

Round document-level charge base amount to 2 decimal places per EN16931

Confidence: 95% · Applied automatically in pipeline

What is BR-DEC-06?

BR-DEC-06 is a fatal validation rule defined in the EN 16931 specification. It validates the BaseAmount 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:BaseAmount

Why This Error Matters

Invoice will be rejected by validation. Base amounts with wrong precision cause downstream calculation issues.

BR-DEC-06 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-06
  • ·Specification: EN 16931

How to Fix It

1.

Locate document charge

Find AllowanceCharge with ChargeIndicator=true at document level

2.

Round base amount

Round cbc:BaseAmount to 2 decimal places using banker's rounding

Before / After

Failing XML
<Invoice>
  <!-- Issue: The allowed maximum number of decimals for the Document leve -->
</Invoice>
Corrected XML
<Invoice>
  <!-- Issue resolved per EN 16931 -->
</Invoice>

Technical Reference

XPath//cac:AllowanceCharge[cbc:ChargeIndicator='true']/cbc:BaseAmount
SpecEN 16931
Operationnormalize
StrategyRound document-level charge base amount to 2 decimal places per EN16931

Common Causes

  • ·Base amount from source system has excessive precision
  • ·Calculation produced more than 2 decimals
  • ·ERP does not truncate base amounts
  • ·Data migration preserved original precision
  • ·Manual entry error

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

Frequently Asked Questions

Item net price (BT-146) allows max 2 decimal places.

Round price to 2 decimal places. Invoice Navigator can help identify and fix this issue.

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

See Also

Last updated: 27 February 2026

Share this guide:

Handle BR-DEC-06 Automatically in Your Pipeline

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