What it means
The date the goods or services were supplied is the delivery date (BT-72), and it is given in the delivery event (ActualDeliverySupplyChainEvent). This rule checks that there is no separate ActualDespatchSupplyChainEvent, which records the dispatch.
Why it matters
The date that counts on an invoice is the delivery date, the date of supply, not the day the goods left the warehouse. The invoice is not rejected, but the dispatch date has no defined meaning and is likely to be ignored.
How to fix it
Make sure the delivery date (BT-72) holds the date of supply, and remove the dispatch event from the file. If your software exports dispatch dates, switch that off or choose the EN 16931 profile. The dispatch date belongs on a despatch advice or delivery note rather than on the invoice.
The rule as published
ActualDespatchSupplyChainEvent 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-319 still fails, and which other rules do.
Related rules
- CII-SR-320 Leave the pick-up event out of the delivery section
- CII-SR-321 Delivery event must not carry an identifier
- CII-SR-322 Write the delivery date as DateTimeString, not DateTime
- CII-SR-323 Delivery event must not carry a type code
- CII-SR-324 Delivery event must not carry a description
- CII-SR-325 Delivery event must not carry an embedded file