errorbusinessEN 16931

`BR-DEC-27`:The allowed maximum number of decimals for the Invoice line charge amount...

Fix: Invoice Navigator automatically fixes this issue by updating the BT-141 field in your Invoice. Upload your invoice to fix this automatically.

The invoice line charge amount has too many decimal places. Line-level charge amounts must have a maximum of 2 decimal places.

Severity

Fatal

Rule set

EN 16931

Country

All EU

Fix type

AUTO-FIX

Confidence

95%

Engine Classification

Round invoice line charge amount to 2 decimal places per EN16931

Confidence: 95% · Applied automatically in pipeline

What is BR-DEC-27?

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

Fix this error

Why This Error Matters

Invoice will be rejected by validation. Line charges affect line net amount and must have proper precision.

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

How to Fix It

Find the incorrectly formatted value

Check cbc:Amount at //cac:InvoiceLine/cac:AllowanceCharge[cbc:ChargeIndicator='true']/cbc:Amount. The current value does not match the required format.

Apply the correct format

Invoice Navigator automatically fixes this issue by updating the BT-141 field in your Invoice.

Update your export settings

If this occurs consistently, check your invoicing software's locale and format settings for XML export. Re-validate to confirm BR-DEC-27 is resolved.

Before / After

Failing XML

<Invoice>
  <!-- Issue: The allowed maximum number of decimals for the Invoice line  -->
</Invoice>

Corrected XML

<Invoice>
  <!-- Issue resolved per EN 16931 -->
</Invoice>

Technical Reference

XPath//cac:InvoiceLine/cac:AllowanceCharge[cbc:ChargeIndicator='true']/cbc:Amount

SpecEN 16931

Operationnormalize

StrategyRound invoice line charge amount to 2 decimal places per EN16931

Common Causes

·Charge percentage calculation produced extra decimals
·Charge amount entered with excess precision
·ERP surcharge calculation preserves full precision
·Manual charge entry error
·Import with different decimal rules

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

Frequently Asked Questions

The invoice line charge amount has too many decimal places. Line-level charge amounts must have a maximum of 2 decimal places.

Invoice Navigator automatically fixes this issue by updating the BT-141 field in your Invoice. You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.

Yes, BR-DEC-27 is a critical error that will cause invoice rejection. It must be fixed before submission.

Many instances of BR-DEC-27 can be automatically corrected using Invoice Navigator's compliance engine. The fix is applied in your pipeline with full audit evidence.

Related Errors

BR-43Allowance/charge reason required

Validate your invoice

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

Upload XML

Auto-fix BR-DEC-27 in seconds

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

Fix it now Automate via API

BR-DEC-27:The allowed maximum number of decimals for the Invoice line charge amount...