What it means
The check looks at the delivery information (BG-13) of the invoice or credit note and warns when it contains cac:Delivery/cac:MinimumDeliveryUnit, the smallest unit in which the goods may be delivered. This is ordering and logistics information. The invoiced quantity (BT-129) sits on the invoice lines.
Why it matters
The EN 16931 UBL mapping does not include a minimum delivery unit in the delivery information. This is separate from the quantity invoiced on each line.
How to fix it
Delete cac:MinimumDeliveryUnit from cac:Delivery in your XML export. Keep the invoiced quantity (BT-129) on the lines. Export the corrected file and check it again.
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
A UBL invoice should not include the Delivery MinimumDeliveryUnit Where this rule applies
| Rule set | Version |
|---|---|
| EN 16931 (UBL) | 1.3.17 |
| EN 16931 (UBL credit note) | 1.3.17 |
| XRechnung 3.0 (UBL) | 3.0.2 |
| XRechnung 3.0 (UBL credit note) | 3.0.2 |
| Peppol BIS Billing 3.0 (invoice) | 2026.5 |
| Peppol BIS Billing 3.0 (credit note) | 2026.5 |
| SI-UBL 2.0 / NLCIUS (invoice) | 2.0.3.13 |
| SI-UBL 2.0 / NLCIUS (credit note) | 2.0.3.13 |
| France CTC (UBL invoice) | 1.4.0-04 |
| France CTC (UBL credit note) | 1.4.0-04 |
| CIUS-RO UBL Invoice 1.0.9 | 1.0.9 |
| CIUS-RO UBL Credit Note 1.0.9 | 1.0.9 |
Check your file
Drop your e-invoice to see whether UBL-CR-407 still fails, and which other rules do.
Related rules
- UBL-CR-408 The delivery should not contain a maximum delivery unit
- UBL-CR-409 The delivery should not contain shipment details
- UBL-CR-410 The invoice should not contain delivery terms at document level
- UBL-CR-411 A payment means should not have its own identifier
- UBL-CR-412 An invoice should not give its due date inside the payment means
- UBL-CR-413 A payment means should not have a payment channel code