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 |
Check your file
Drop your e-invoice to see whether CII-SR-400 still fails, and which other rules do.
Related rules
- CII-SR-401 Leave the type code out of the payment terms
- CII-SR-402 Leave the instruction type code out of the payment terms
- CII-SR-404 Leave the partial payment percentage out of the payment terms
- CII-SR-405 Leave the payment means reference out of the payment terms
- CII-SR-406 Leave the partial payment amount out of the payment terms
- CII-SR-407 Leave structured late-payment penalty terms out of the invoice