errorcii-d16b

CII-FIX-DATE:CII date format must use format code 102

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".

Severity
Fatal
Rule set
cii-d16b
Country
All EU
Fix type
AUTO-FIX
Confidence
99%
Category
formatting

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 non-compliant and will be rejected by Peppol access points and national validation services. The sending system receives a rejection response and the invoice does not reach the buyer.

Target path: //udt:DateTimeString

Why This Error Matters

CII-FIX-DATE is a hard failure. Invoices that trigger this rule are rejected at the access point and never reach the recipient. In Peppol networks, this means your sending system receives an MLR (Message Level Response) with a rejection status. The invoice must be corrected and re-sent, adding delay to your payment cycle.

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

XML Example

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

Before
<!-- Triggers validation error -->
<udt:DateTimeString></udt:DateTimeString>
After
<!-- Corrected -->
<udt:DateTimeString>VALID_VALUE</udt:DateTimeString>

Technical Reference

XPath//udt:DateTimeString
Speccii-d16b
Operationnormalize
StrategyStrip hyphens from ISO dates and set @format="102" on all DateTimeString elements

Common 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

ZUGFeRD generatorsFactur-X convertersUBL-to-CII transformation tools

Last updated: 18 February 2026

Share this guide:

Handle CII-FIX-DATE Automatically in Your Pipeline

The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.