What it means
The delivery event (ActualDeliverySupplyChainEvent) carries the delivery date (BT-72). This rule checks that it has no ID element, a reference number for the event itself. A despatch advice reference (BT-16) or receiving advice reference (BT-15) is given elsewhere and stays allowed.
Why it matters
The invoice standard has no field for an event number, so the buyer's software cannot map it. The invoice is not rejected, but the number is likely to be dropped.
How to fix it
Check whether your software exports a delivery or shipment number into the delivery event, and turn that off in the export settings. If the buyer needs the number, give it as the despatch advice reference (BT-16) when it refers to a despatch advice, or in the invoice note (BT-22). Leave the delivery date in place.
The rule as published
ID 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-321 still fails, and which other rules do.
Related rules
- 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
- CII-SR-327 Leave out the latest delivery date and time