errorubl-2.1
UBL-CR-004:Invalid date format
Dates must be in ISO 8601 format: YYYY-MM-DD.
We can fix this automatically
AUTO-FIXAuto-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 NowWhy 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 date format
Must be YYYY-MM-DD (e.g., 2024-12-19)
2
No time component
Do not include time for date-only fields
3
Validate dates
Ensure dates are valid (not Feb 30, etc.)
Code Example
<cbc:IssueDate>2024-12-19</cbc:IssueDate>
<cbc:DueDate>2025-01-18</cbc:DueDate>Technical Details
XPath: //cbc:IssueDate, //cbc:DueDate, 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
Custom exportsManual editing
Frequently Asked Questions
Dates must be in ISO 8601 format: YYYY-MM-DD.
Use YYYY-MM-DD format for all dates. You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.
Yes, UBL-CR-004 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-004 can be automatically corrected using Invoice Navigator's Fixer tool. Upload your invoice and the tool will identify and fix common issues, including invalid date format.
UBL-CR-004 is commonly seen in exports from Custom exports, Manual editing. These software packages sometimes generate invoices that need adjustment to meet full compliance standards.
Related Errors
Last updated: 16 January 2026
Share this guide: