errorsyntaxubl-2.1

UBL-SR-06:Invalid date format

Fix: Use ISO 8601 date format (YYYY-MM-DD).

UBL dates must use YYYY-MM-DD format.

Severity
Fatal
Rule set
ubl-2.1
Country
All EU
Fix type
CONFIRM
Confidence
90%
Category
structural

Engine Classification

Requires user confirmation before application

What is UBL-SR-06?

UBL-SR-06 is a fatal validation rule defined in the ubl-2.1 specification. It validates the InvoiceDocumentReference element under BillingReference 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/cac:BillingReference/cac:InvoiceDocumentReference

Why This Error Matters

Invoice will be rejected by EN16931 validators. These structural constraints ensure consistent processing by receiving systems.

UBL-SR-06 is a hard failure — the invoice must be corrected and re-sent before it can reach the recipient.

Validator Behavior

  • ·Causes invoice rejection
  • ·Fails UBL schema validation
  • ·Error returned: UBL-SR-06
  • ·Specification: ubl-2.1

How to Fix It

1.

Check format

Must be YYYY-MM-DD

2.

Convert if needed

From DD/MM/YYYY or other formats

XML Example

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

Before
<!-- Required block is missing -->
<!-- <cac:InvoiceDocumentReference> ... </cac:InvoiceDocumentReference> -->
After
<!-- Add the required block -->
<cac:InvoiceDocumentReference>
  <!-- child elements -->
</cac:InvoiceDocumentReference>

Technical Reference

XPath/Invoice/cac:BillingReference/cac:InvoiceDocumentReference
Specubl-2.1
Operationremove_duplicates
StrategyRemove duplicate preceding invoice references, keeping the first occurrence

Common Causes

  • ·ERP system exports multiple references where only one is allowed in EN16931
  • ·Data consolidation merged records that should have been deduplicated
  • ·Template or mapping incorrectly configured to output duplicate elements
  • ·Manual editing introduced extra elements
  • ·Invoice conversion from another format did not merge duplicate entries

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

Frequently Asked Questions

UBL dates must use YYYY-MM-DD format.

Use ISO 8601 date format (YYYY-MM-DD). Invoice Navigator can propose a fix for this error, which you review and confirm before it is applied.

Yes, UBL-SR-06 is a critical error that will cause invoice rejection. It must be fixed before submission.

Related Errors

Related Content

Last updated: 3 March 2026

Share this guide:

Validate your invoice

Drop your XML here to check for UBL-SR-06

Fix UBL-SR-06 with one click

Upload your invoice and we'll suggest a fix for your review before applying it.