Skip to content

Warning

UBL-CR-349: Leave out the delivery release identifier

In short

Warning: worth checking.

UBL-CR-349 means your UBL invoice or credit note carries a release identifier on the delivery (cac:Delivery/cbc:ReleaseID), which EN 16931 does not use. Remove the element.

On this page

What it means

The rule checks that the delivery section of a UBL file (cac:Delivery) has no release identifier (cbc:ReleaseID). In UBL that field holds a release reference for the delivery, a logistics detail that EN 16931 has no business term for.

Why it matters

EN 16931 does not use a release identifier directly under cac:Delivery.

How to fix it

Clear any release reference in the delivery data of your invoicing software and export again. If it is really the buyer's purchase order number, enter it as the purchase order number (BT-13) instead, otherwise put it in an invoice note (BT-22). If you build the XML yourself, delete the cbc:ReleaseID that sits directly under cac:Delivery.

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 ReleaseID

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

Updated 6 November 2026