errorubl-2.1

UBL-CR-006:Invalid decimal format

Decimal numbers must use dot (.) as decimal separator with max 2 decimal places for amounts.

We can fix this automatically

AUTO-FIX

Auto-fix: Remove the disallowed element from the invoice XML. No data loss occurs because EN16931 explicitly prohibits this element.

No manual changes needed
Upload and Fix Now

Why This Error Matters

Invoice will be rejected by PEPPOL/EN16931 validators. Safe to remove - this element is explicitly prohibited and contains no required business data.

How to Fix It

1

Check separator

Use . not , for decimals

2

Limit decimals

Max 2 for currency amounts

3

No thousands separator

Write 1000.00 not 1,000.00

Code Example

<!-- BAD: -->
<cbc:Amount>1.234,56</cbc:Amount>
<!-- GOOD: -->
<cbc:Amount>1234.56</cbc:Amount>

Technical Details

XPath: //cbc:Amount, //cbc:PriceAmount, etc.

Common Causes

  • Source ERP exports full UBL 2.1 instead of EN16931 subset
  • Generic UBL template includes optional elements not needed for e-invoicing
  • Conversion from another format added unsupported elements
  • Manual XML editing introduced non-standard elements
  • Invoice software not configured for EN16931 compliance

Commonly Seen In

Regional software configurations

Frequently Asked Questions

Decimal numbers must use dot (.) as decimal separator with max 2 decimal places for amounts.
Use correct decimal format with dot separator. You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.
Yes, UBL-CR-006 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 UBL-CR-006 can be automatically corrected using Invoice Navigator's Fixer tool. Upload your invoice and the tool will identify and fix common issues, including invalid decimal format.
UBL-CR-006 is commonly seen in exports from Regional software configurations. These software packages sometimes generate invoices that need adjustment to meet full compliance standards.

Related Errors

Last updated: 16 January 2026

Share this guide: