Skip to content

Warning

CII-SR-400: Write the due date as a date string, not a date-time

In short

Warning: worth checking.

CII-SR-400 means the due date is written with a DateTime element, but EN 16931 expects a DateTimeString. It is only a warning and the invoice is still accepted; write the date as DateTimeString with format 102.

On this page

What it means

The due date (BT-9) inside the payment terms is written with a DateTime element. EN 16931 expects the due date in a DateTimeString element with format 102, which is the date as eight digits in the order year, month, day.

Why it matters

This is a warning, so the invoice is still accepted. But a system that reads the due date only from DateTimeString will not find it, and may treat the invoice as having no due date. It is worth fixing because the due date tells the buyer when to pay.

How to fix it

Replace the DateTime element inside the due date with a DateTimeString element, add the attribute format with the value 102, and write the date as eight digits. Most invoicing software writes this for you, so if you cannot edit the file, look for an export setting or an update that produces EN 16931 dates, or ask the vendor.

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-400 still fails, and which other rules do.

Updated 6 November 2026