errorbusinessen16931

BR-DEC-07:Item gross price: max 2 decimals

Fix: Round gross price to 2 decimals.

Item gross price allows max 2 decimal places.

Severity
Fatal
Rule set
en16931
Country
All EU
Fix type
BLOCKED

Engine Classification

Financial or legal field · Modification blocked by policy

Reason: Item gross prices must have maximum 2 decimal places. Automatic rounding of prices could affect line calculations and totals. Fix the item pricing in your source system to use proper 2-decimal precision.

What is BR-DEC-07?

BR-DEC-07 is a fatal validation rule defined in the en16931 specification. It validates the BaseAmount element under Price > 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: XPath: /Invoice/cac:InvoiceLine/cac:Price/cac:AllowanceCharge/cbc:BaseAmount

This error requires manual correction — financial fields are protected by policy.

Why This Error Matters

Gross price base for allowance calc.

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

Validator Behavior

  • ·Causes invoice rejection
  • ·Fails EN 16931 business rule validation
  • ·Error returned: BR-DEC-07
  • ·Specification: en16931

How to Fix It

1.

Check gross price

BaseAmount precision

2.

Round

2 decimal maximum

XML Example

Generic example based on the rule's target XPath. Your actual XML structure may differ.

Before
<!-- Missing or empty element triggers cbc:BaseAmount error -->
<cbc:BaseAmount></cbc:BaseAmount>
After
<!-- Provide the required value -->
<cbc:BaseAmount>VALID_VALUE</cbc:BaseAmount>

Technical Reference

XPathXPath: /Invoice/cac:InvoiceLine/cac:Price/cac:AllowanceCharge/cbc:BaseAmount
Specen16931

Common Causes

  • ·Base price with extra precision

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

Frequently Asked Questions

Item gross price allows max 2 decimal places.

Round gross price to 2 decimals. This error involves a protected field — Invoice Navigator flags it in your pipeline so your team can correct it at the source.

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

Related Errors

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

Related Content

Learn
What is Peppol?
Glossary
Evidence Packe-Reporting
Answers
What is the difference between B2G and B2B e-invoicing?
Blog
The 10 Most Common E-Invoice Errors in 2026 (and How to Fix Each One)Belgium E-Invoicing After the Grace Period: What ERP Vendors Need to Know
Validators
XRechnung ValidatorZUGFeRD Validator

Last updated: 3 March 2026

Share this guide:

Validate your invoice

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

Detect BR-DEC-07 before submission

This error involves a financial field that can't be auto-modified. We'll flag it with a clear diagnosis so you can fix it at the source.

Fix it nowAutomate via API