What it means
This rule checks that the delivery section has no ActualPickUpSupplyChainEvent, an event for the moment the buyer or a carrier collected the goods. The one event EN 16931 does use is the delivery event, which carries the delivery date (BT-72).
Why it matters
The recipient's software has no field for a pick-up date, so it is likely to be ignored. The invoice is not rejected. If the buyer collected the goods, the collection date is normally what you give as the delivery date.
How to fix it
If the pick-up date is the date the goods or services were supplied, enter it as the delivery date (BT-72) in your invoicing software. Then stop the software exporting the pick-up event, or choose the EN 16931 profile. If the date only matters for logistics, leave it out of the e-invoice.
The rule as published
ActualPickUpSupplyChainEvent 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-320 still fails, and which other rules do.
Related rules
- 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
- CII-SR-326 Delivery event must not carry a quantity