What it means
Each line's ram:SpecifiedLineTradeDelivery should be free of ram:ActualDeliverySupplyChainEvent children. This restriction applies to the whole event element, not just its date.
Why it matters
EN 16931 places the delivery date (BT-72) at invoice level. A line's invoicing period, expressed through BT-134 and BT-135, has a different meaning and is not automatically a replacement for its delivery date.
How to fix it
Remove ram:ActualDeliverySupplyChainEvent from the affected line's ram:SpecifiedLineTradeDelivery. Record an invoice-level delivery date (BT-72) only if it accurately describes the invoice's delivery. Use the line period start date (BT-134) and end date (BT-135) only for the period you are invoicing, not merely to relocate delivery dates. Export the corrected file and recheck it.
Once the file is corrected, check it again for free: Validate an invoice against EN 16931
Or fix the invoice in a form and download the corrected file, for 1 credit: Fix a rejected e-invoice
The rule as published
ActualDeliverySupplyChainEvent 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-170 still fails, and which other rules do.
Related rules
- CII-SR-171 Invoice lines should not include goods receipt details
- CII-SR-172 Line delivery details should not refer to extra documents
- CII-SR-173 Invoice lines should not give a despatch advice reference
- CII-SR-174 Invoice lines should not give a receiving advice reference
- CII-SR-175 Invoice lines should not give a delivery note reference
- CII-SR-176 Invoice lines should not give a consumption report reference