What it means
The delivery event (ActualDeliverySupplyChainEvent) carries the delivery date (BT-72). This rule checks that it has no TypeCode, a code that says what kind of event it is.
Why it matters
The place of the event in the file already says it is the delivery, so the code adds nothing a recipient can use. The invoice is not rejected, but the code is not expected to be read.
How to fix it
The code is written by the software, so there is usually no field for you to clear. Look in the export or format settings and choose the EN 16931 profile rather than a fuller one. If it still appears, ask the software supplier to stop writing a TypeCode on the delivery event.
The rule as published
TypeCode 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-323 still fails, and which other rules do.
Related rules
- 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
- CII-SR-328 Leave out the earliest delivery date and time
- CII-SR-329 Leave out the delivery period in the delivery event