What it means
The delivery event (ActualDeliverySupplyChainEvent) carries the delivery date (BT-72). This rule checks that it has no UnitQuantity, a quantity recorded against the event itself.
Why it matters
On an e-invoice the quantities are on the lines, as the invoiced quantity (BT-129). A quantity on the delivery event has no defined meaning, so the recipient's software is likely to ignore it. The invoice is not rejected.
How to fix it
Check that each line has the right quantity, since that is the figure the buyer reads. Then stop your software exporting a delivered quantity on the delivery event, by choosing the EN 16931 profile or changing the export settings. If a partial delivery matters, say so in the invoice note (BT-22).
The rule as published
UnitQuantity 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-326 still fails, and which other rules do.
Related rules
- 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
- CII-SR-330 Leave out the location in the delivery event
- CII-SR-331 Leave out the goods receipt event
- CII-SR-332 Leave out extra referenced documents in the delivery details