Skip to content

Warning

UBL-CR-408: The delivery should not contain a maximum delivery unit

In short

Warning: worth checking.

UBL-CR-408 means the UBL file states a maximum delivery unit in the delivery information (cac:MaximumDeliveryUnit), which EN 16931 does not use. Remove it and export again.

On this page

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:MaximumDeliveryUnit, the largest unit in which the goods may be delivered. This is ordering and logistics information, and EN 16931 has no field for it. The invoiced quantity (BT-129) sits on the invoice lines.

Why it matters

The EN 16931 UBL mapping does not include a maximum delivery unit in the delivery information. This is separate from the quantity invoiced on each line.

How to fix it

Delete cac:MaximumDeliveryUnit 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 MaximumDeliveryUnit

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
Rule text from phive-rules 4.6.4.

Check your file

Drop your e-invoice to see whether UBL-CR-408 still fails, and which other rules do.

Updated 6 November 2026