Skip to content
Change language: English

Warning

UBL-CR-358: Leave out the validity period of the delivery location

In short

Warning: worth checking.

UBL-CR-358 means the delivery location has a validity period (cac:DeliveryLocation/cac:ValidityPeriod), which EN 16931 does not use. Remove it.

On this page

What it means

The rule checks that the delivery location (cac:Delivery/cac:DeliveryLocation) has no validity period (cac:ValidityPeriod), a period during which the location is valid. EN 16931 has no business term for it. The delivery date (BT-72) and invoicing period (BG-14) are separate fields and are not targeted by this check.

Why it matters

EN 16931 does not use a validity period for the delivery location.

How to fix it

Clear the delivery location's validity period in your invoicing software and export again. This rule does not require you to remove the delivery date (BT-72) or invoicing period (BG-14). If you build the XML yourself, delete the cac:ValidityPeriod block that sits directly under cac:DeliveryLocation.

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 DeliveryLocation ValidityPeriod

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

Updated 6 November 2026