Skip to content
Change language: English

Warning

UBL-CR-014: The document-level invoicing period should not contain a duration

In short

Warning: worth checking.

UBL-CR-014 means a document-level invoicing period contains a duration (cbc:DurationMeasure), which EN 16931 does not use. Remove this element. If you need to retain the period, use the appropriate start date (BT-73), end date (BT-74), or both.

On this page

What it means

The rule checks that a document-level cac:InvoicePeriod has no cbc:DurationMeasure. In UBL that element states the length of the period as a number with a unit, such as 30 days. This test does not require you to add either date.

Why it matters

EN 16931's UBL rules exclude a duration measure from the document-level invoicing period.

How to fix it

Remove cbc:DurationMeasure inside cac:InvoicePeriod directly under the invoice or credit note root. If you need to record the period as dates, use cbc:StartDate, cbc:EndDate, or both, with the actual dates. Do not invent dates from a duration alone. Export again and recheck the 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 InvoicePeriod DurationMeasure

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

Updated 6 November 2026