errorformatUBL 2.1

UBL-CR-006:Disallowed element: cbc:IssueTime

Fix: Invoice Navigator automatically removes the disallowed `cbc:IssueTime` element from your Invoice. Upload your invoice to fix this automatically.

UBL 2.1 Invoice schema does not include `cbc:IssueTime`. This element must be removed for EN 16931 compliance.

Severity
Fatal
Rule set
UBL 2.1
Country
All EU
Fix type
AUTO-FIX
Confidence
95%
Category
structural

Engine Classification

Remove disallowed UBL element per EN16931 specification

Confidence: 95% · Applied automatically in pipeline

What is UBL-CR-006?

UBL-CR-006 is a fatal validation rule defined in the UBL 2.1 specification. It validates the IssueTime 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: /Invoice/cbc:IssueTime

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.

UBL-CR-006 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
  • ·Fails UBL schema validation
  • ·Error returned: UBL-CR-006
  • ·Specification: UBL 2.1

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

Before / After

Failing XML
<Invoice>
  <cbc:IssueTime>value</cbc:IssueTime>
</Invoice>
Corrected XML
<Invoice>
  <!-- cbc:IssueTime removed for EN 16931 compliance -->
</Invoice>

Technical Reference

XPath/Invoice/cbc:IssueTime
SpecUBL 2.1
Operationremove
StrategyRemove disallowed UBL element per EN16931 specification

Code Example

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

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

Seeing this in production? The API handles UBL-CR-006 automatically. See the fix response →

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

Related Content

Last updated: 27 February 2026

Share this guide:

Validate your invoice

Drop your XML here to check for UBL-CR-006

Auto-fix UBL-CR-006 in seconds

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