BR-DEC-16EN 16931fatalbusiness

Paid amount: max 2 decimals

Fix: Invoice Navigator automatically fixes this issue by correcting the `cbc:AllowanceTotalAmount` element in your Invoice. Upload your invoice to fix this automatically.

The Paid amount (BT-113, also known as prepaid amount) must have a maximum of 2 decimal places. This represents amounts already paid toward the invoice.

Where is this in my invoice?

Shown on a sample invoice. The marked row is the field this rule checks; on your own invoice it sits in the same place.

Sample invoice · not your document

Invoice

SAMPLE-INV-001 · issued 4 Jan 2026 · due 4 Feb 2026 · EUR

Seller

Seller nameSample Supplier B.V.

Seller streetHerengracht 100

Seller postcode1015 BS

Seller cityAmsterdam

Seller countryNL

Seller VAT numberNL123456789B01

Seller registration number12345678

Seller electronic addressNL123456789B01

Buyer

Buyer nameSample Buyer NV

Buyer streetRue de la Loi 42

Buyer postcode1000

Buyer cityBrussels

Buyer countryBE

Buyer VAT numberBE0123456789

Buyer electronic addressBE0123456789

Invoice details

Invoice numberSAMPLE-INV-001

Issue date4 Jan 2026

Due date4 Feb 2026

Invoice type380

CurrencyEUR

Buyer referencePO-12345

Payment

Payment method30

Payment IBANNL91ABNA0417164300

Line items

No.	Item	Quantity	Unit price	VAT rate (%)	Line amount
1	Consulting Services	1	€100.00	21%	€100.00

Totals

Sum of line amounts€100.00

Total without VAT€100.00

Total VAT€21.00

Total with VAT€121.00

Amount already paid— BR-DEC-16

Amount due€121.00

VAT breakdown

VAT category	VAT rate (%)	Taxable amount	VAT amount
S	21%	€100.00	€21.00

How to Fix It

Locate PrepaidAmount

Find cbc:PrepaidAmount in cac:LegalMonetaryTotal

Check decimal places

Count the number of decimal places in the amount

Round if needed

If more than 2 decimals, round using standard rounding (half up)

See this rule against your own invoice: every finding is pinned to the row it concerns.

Check your invoice Run this check in CI

Severity

Fatal

Rule set

EN 16931

Country

All EU

Fix type

Auto-fix

Confidence

95%

Engine Classification

Round prepaid amount to 2 decimal places per EN16931

Confidence: 95% · Applied automatically in pipeline

What is BR-DEC-16?

BR-DEC-16 is a fatal validation rule defined in the EN 16931 specification. It validates the PrepaidAmount element in the UBL invoice XML.

When this rule fires, the invoice is rejected by Peppol access points and never reaches the buyer.

Target path: //cac:LegalMonetaryTotal/cbc:PrepaidAmount

Why This Error Matters

Invoice will be rejected by validation. Paid amounts affect the amount due calculation and must have proper precision.

BR-DEC-16 is a hard failure — the invoice must be corrected and re-sent before it can reach the recipient.

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-16
·Specification: EN 16931

Before / After

Failing XML

<cac:LegalMonetaryTotal>
  <cbc:AllowanceTotalAmount>100.123456</cbc:AllowanceTotalAmount>
  <!-- Too many decimal places -->
</cac:LegalMonetaryTotal>

Corrected XML

<cac:LegalMonetaryTotal>
  <cbc:AllowanceTotalAmount>100.00</cbc:AllowanceTotalAmount>
  <!-- Correct decimal places -->
</cac:LegalMonetaryTotal>

Technical Reference

XPath//cac:LegalMonetaryTotal/cbc:PrepaidAmount

SpecEN 16931

Operationnormalize

StrategyRound prepaid amount to 2 decimal places per EN16931

Common Causes

·Prepayment amount entered with extra precision
·Partial payment calculation produced excess decimals
·Import from payment system with different precision
·Currency conversion on prepaid amount
·Manual entry error

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

Frequently Asked Questions

BR-DEC-16 occurs when the Paid amount (BT-113, also called prepaid amount) has more than 2 decimal places. This typically happens during partial payment calculations or when importing from payment systems with different precision.

Round the PrepaidAmount value in cac:LegalMonetaryTotal to 2 decimal places. Invoice Navigator's automatic Fixer tool can correct this instantly.

Yes, BR-DEC-16 is a critical error that will cause invoice rejection. Monetary amounts must have proper precision for financial compliance.

Yes, BR-DEC-16 can be automatically fixed using Invoice Navigator's Fixer tool. The tool will round the paid amount to 2 decimal places.

Validate your invoice

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

Upload XML

Auto-fix BR-DEC-16 in seconds

Upload your invoice and we fix this error automatically. Financial fields are never touched.

Fix it now Automate via API