What it means
The invoicing period (BG-14), or the period on a line (BG-26), sits in BillingSpecifiedPeriod. Its end date (BT-74, or BT-135 on a line) goes in EndDateTime. This rule checks that EndDateTime does not hold a DateTime element, which is a full date and time value. EN 16931 uses the plain date form, DateTimeString.
Why it matters
The standard fixes the form in which this date is written so that every receiving system reads it the same way. An end date written another way does not meet it, so the file fails and is rejected.
How to fix it
Look in the e-invoice or XML export settings of your invoicing software and choose the standard EN 16931 output. If you build the XML yourself, replace the DateTime element inside EndDateTime with DateTimeString, set its format attribute to 102 and write the date as YYYYMMDD. Check the start date in the same way, as it has its own rule.
The rule as published
DateTime shall not be used. 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-DT-072 still fails, and which other rules do.
Related rules
- CII-DT-073 Leave the complete date-time out of the invoicing period
- CII-DT-074 Leave the open flag out of the invoicing period
- CII-DT-075 Leave the season code out of the invoicing period
- CII-DT-076 Leave the identifier out of the invoicing period
- CII-DT-077 Leave the name out of the invoicing period
- CII-DT-078 Leave the sequence number out of the invoicing period