errorEN 16931

BR-DEC-18:Payable amount: max 2 decimals

PayableAmount allows maximum 2 decimal places.

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

Engine Classification

Round amount due for payment to 2 decimal places per EN16931

Confidence: 95% · Applied automatically in pipeline

What is BR-DEC-18?

BR-DEC-18 is a fatal validation rule defined in the EN 16931 specification. It validates the PayableAmount 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:LegalMonetaryTotal/cbc:PayableAmount

Why This Error Matters

Invoice will be rejected by validation. Amount due is the actual payment amount and must have proper precision for payment processing.

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

How to Fix It

1.

Check payable

This is the amount to be paid

2.

Round

Must be 2 decimals for payment

Before / After

Failing XML
<cac:LegalMonetaryTotal>
  <cbc:PayableAmount>100.123456</cbc:PayableAmount>
  <!-- Too many decimal places -->
</cac:LegalMonetaryTotal>
Corrected XML
<cac:LegalMonetaryTotal>
  <cbc:PayableAmount>100.00</cbc:PayableAmount>
  <!-- Correct decimal places -->
</cac:LegalMonetaryTotal>

Technical Reference

XPath//cac:LegalMonetaryTotal/cbc:PayableAmount
SpecEN 16931
Operationnormalize
StrategyRound amount due for payment to 2 decimal places per EN16931

Common Causes

  • ·Calculation from total minus prepaid produced extra decimals
  • ·Rounding adjustment created excess precision
  • ·ERP exports amount due with full precision
  • ·Component amounts not properly rounded
  • ·Currency formatting not applied to final amount

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

Frequently Asked Questions

PayableAmount allows maximum 2 decimal places.

Round final payable amount to 2 decimals. You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.

Yes, BR-DEC-18 is a critical error that will cause invoice rejection. It must be fixed before submission to ensure your invoice is accepted by the recipient's system.

Many instances of BR-DEC-18 can be automatically corrected using Invoice Navigator's Fixer tool. Upload your invoice and the tool will identify and fix common issues, including payable amount: max 2 decimals.

See Also

Related Errors

Last updated: 27 February 2026

Share this guide:

Handle BR-DEC-18 Automatically in Your Pipeline

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