Skip to content

Warning

CII-SR-322: Write the delivery date as DateTimeString, not DateTime

In short

Warning: worth checking.

CII-SR-322 means a date in the delivery event is written as DateTime, which EN 16931 does not use. It is a warning, so the file is still accepted; write the delivery date as DateTimeString with format code 102 instead.

On this page

What it means

The delivery date (BT-72) sits in the delivery event, under OccurrenceDateTime. A CII file can write a date in two ways: as DateTime, a full timestamp, or as DateTimeString, a date with a format code. EN 16931 uses only the second, and this rule checks that DateTime is not used there.

Why it matters

Recipient software looks for the delivery date in DateTimeString. A date written as DateTime may not be read as the delivery date, so it can appear empty on the buyer's side. The invoice is not rejected.

How to fix it

Change how the date is written, not its value. Use DateTimeString with format code 102, which is the date in the compact year, month, day form, in place of DateTime. In invoicing software this is a format or profile setting, so check the e-invoice export settings or update the software; if your own script writes the XML, change that element.

The rule as published

DateTime should not be present

Where this rule applies

Rule set Version
EN 16931 (CII) 1.3.17
XRechnung 3.0 (CII) 3.0.2
NLCIUS (CII) 1.0.3.13
France CTC (CII) 1.4.0-04
Rule text from phive-rules 4.6.4.

Check your file

Drop your e-invoice to see whether CII-SR-322 still fails, and which other rules do.

Updated 6 November 2026