What it means
Inside the delivery details (ApplicableHeaderTradeDelivery), the delivery event (ActualDeliverySupplyChainEvent) should not contain an EarliestOccurrenceDateTime, the earliest date and time at which the delivery took place. The delivery date (BT-72) is a single date in OccurrenceDateTime, and that element is allowed.
Why it matters
This is a warning, so the file is still accepted. EN 16931 has no field for an earliest delivery date and time, so receiving software normally drops it. If the buyer relies on that value, it never reaches them.
How to fix it
Check the delivery details of the invoice in your invoicing software and keep one delivery date. Clear any start date or delivery window if the software offers one. If you can choose a profile when you export, pick EN 16931 rather than Extended. It is worth fixing when the buyer needs the date, because only the single delivery date is read.
The rule as published
EarliestOccurrenceDateTime 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-328 still fails, and which other rules do.
Related rules
- CII-SR-329 Leave out the delivery period in the delivery event
- CII-SR-330 Leave out the location in the delivery event
- CII-SR-331 Leave out the goods receipt event
- CII-SR-332 Leave out extra referenced documents in the delivery details
- CII-SR-333 Leave out the line number of the despatch advice
- CII-SR-334 Despatch advice reference must not carry a line number