CII-FIX-DATE:CII date format must use format code 102
Fix: Convert date to YYYYMMDD format and set @format="102". Upload your invoice to fix this automatically.
All dates in CII invoices must use format code 102 (YYYYMMDD) in the udt:DateTimeString element. ISO 8601 dates with hyphens (YYYY-MM-DD) are not valid in CII — the hyphens must be removed and the @format attribute set to "102".
Engine Classification
Strip hyphens from ISO dates and set @format="102" on all DateTimeString elements
Confidence: 99% · Applied automatically in pipeline
What is CII-FIX-DATE?
CII-FIX-DATE is a fatal validation rule defined in the cii-d16b specification. It validates the udt:DateTimeString 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: //udt:DateTimeString
Why This Error Matters
CII-FIX-DATE is a hard failure — the invoice must be corrected and re-sent before it can reach the recipient.
Dates without format code 102 cause CII validation failures. The receiving system cannot parse the invoice dates, which may delay payment processing or cause automatic rejection.
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 CII schema validation
- ·Error returned: CII-FIX-DATE
- ·Specification: cii-d16b
How to Fix It
Find the incorrectly formatted value
Check udt:DateTimeString at //udt:DateTimeString. The current value does not match the required format.
Apply the correct format
Convert date to YYYYMMDD format and set @format="102".
Update your export settings
If this occurs consistently, check your invoicing software's locale and format settings for XML export. Re-validate to confirm CII-FIX-DATE is resolved.
XML Example
Generic example based on the rule's target XPath. Your actual XML structure may differ.
<!-- Triggers validation error --> <udt:DateTimeString></udt:DateTimeString>
<!-- Corrected --> <udt:DateTimeString>VALID_VALUE</udt:DateTimeString>
Technical Reference
//udt:DateTimeStringCommon Causes
- ·ERP exports dates in ISO 8601 (YYYY-MM-DD) instead of CII format 102
- ·Missing @format attribute on DateTimeString
- ·UBL-to-CII converter preserves UBL date format
Seeing this in production? The API handles CII-FIX-DATE automatically. See the fix response →
Commonly Seen In
Frequently Asked Questions
All dates in CII invoices must use format code 102 (YYYYMMDD) in the udt:DateTimeString element. ISO 8601 dates with hyphens (YYYY-MM-DD) are not valid in CII — the hyphens must be removed and the @format attribute set to "102".
Convert date to YYYYMMDD format and set @format="102". You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.
Yes, CII-FIX-DATE is a critical error that will cause invoice rejection. It must be fixed before submission.
Many instances of CII-FIX-DATE can be automatically corrected using Invoice Navigator's compliance engine. The fix is applied in your pipeline with full audit evidence.
CII-FIX-DATE is commonly seen in exports from ZUGFeRD generators, Factur-X converters, UBL-to-CII transformation tools. These packages sometimes generate invoices that need adjustment.
Related Content
Last updated: 14 April 2026
Validate your invoice
Drop your XML here to check for CII-FIX-DATE
Auto-fix CII-FIX-DATE in seconds
Upload your invoice and we fix this error automatically. Financial fields are never touched.