What it means
On each line, the unit price after discount (BT-146) sits in the NetPriceProductTradePrice block. This rule checks that the block holds no MinimumQuantity, an element that gives the smallest quantity for which the price applies.
Why it matters
EN 16931 states the price actually charged on the line, not the quantity bands it came from, so receiving software may ignore a minimum quantity. The file is still accepted, because this is a warning. It is worth fixing for a clean file, or when the buyer expects to see the price band.
How to fix it
Delete the MinimumQuantity element from NetPriceProductTradePrice in each affected line. Keep the unit price (ChargeAmount) and the quantity on the line. If the price band matters, mention it in a note on the line (BT-127). If your software writes the element, look for an EN 16931, XRechnung or Peppol BIS export setting.
The rule as published
MinimumQuantity 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-138 still fails, and which other rules do.
Related rules
- CII-SR-139 Remove the maximum quantity from the unit price after discount
- CII-SR-140 Remove the price change reason from the unit price after discount
- CII-SR-141 Remove the unit conversion factor from the unit price after discount
- CII-SR-142 Keep discounts and charges out of the unit price after discount
- CII-SR-143 Remove the validity period from the unit price after discount
- CII-SR-144 Remove the delivery location from the unit price after discount