Skip to content

Warning

UBL-CR-385: Leave out the carrier in the delivery details

In short

Warning: worth checking.

UBL-CR-385 means the invoice or credit note names a carrier (cac:CarrierParty) in its delivery details, which EN 16931 does not use. Remove cac:CarrierParty from cac:Delivery and put the carrier details in the invoice note (BT-22) if the buyer needs them.

On this page

What it means

This rule looks at the delivery information (cac:Delivery) of a UBL invoice or credit note and checks that it has no cac:CarrierParty. That element identifies the party that transports the goods. UBL has it, but EN 16931 has no business term for a carrier.

Why it matters

EN 16931 has no business term for a carrier in the delivery information.

How to fix it

Change your invoice export so it omits the carrier block from the delivery details. If the buyer needs it, write the carrier name, and a tracking number if you have one, in the invoice note (BT-22). If you build the XML yourself, delete cac:CarrierParty from cac:Delivery. Recheck the exported file.

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 CarrierParty

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-385 still fails, and which other rules do.

Updated 6 November 2026