How do I fix BR-DEC-27?

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.

Is BR-DEC-27 a critical error?

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

Can BR-DEC-27 be automatically fixed?

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.

errorEN 16931

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

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 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:InvoiceLine/cac:AllowanceCharge[cbc:ChargeIndicator='true']/cbc:Amount

Get API Access Test 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. 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-27
·Specification: EN 16931

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 →

Related Errors

BR-43

Allowance/charge reason required

Last updated: 27 February 2026

Share this guide:

Handle BR-DEC-27 Automatically in Your Pipeline

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

Get API Access View API Documentation

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