Counterfoil rule note

BR-CO-19

Quoted from a public specification. This page is not a validator, and it is not tax, legal, or accounting advice.

Country
EU
Syntax
UBL
Severity
fatal
Last verified
2026-10-18

Official statement

If Invoicing period (BG-14) is used, the Invoicing period start date (BT-73) or the Invoicing period end date (BT-74) shall be filled, or both.

Source: https://docs.peppol.eu/poacc/billing/3.0/rules/ubl-tc434/BR-CO-19/

Peppol BIS Billing 3.0, May 2026 release, EN 16931 model bound to UBL

Severity note: fatal, from the Flag column of the Peppol BIS Billing 3.0 UBL rules index retrieved 2026-10-18.

Plain-language reading

If an invoicing period (BG-14) is used, the invoicing period start date (BT-73) or the invoicing period end date (BT-74) must be filled, or both. The statement ends with a period. The context is the invoice period. The published test passes when either date exists, and also when a description code exists and both dates are absent. That third branch calls exists. The test does not compare the two dates.

What to change

When an invoicing period is present, send the start date (BT-73), the end date (BT-74), or both.

Illustration

Illustration of the condition in the official statement. Not an example published by the source.

Fails the stated condition. An invoicing period has neither a start date, nor an end date, nor a description code.

Passes the stated condition. An invoicing period has a start date and no end date.

Published context and test

Copied from the source. Not reimplemented on this page.

cac:InvoicePeriod
exists(cbc:StartDate) or exists(cbc:EndDate) or (exists(cbc:DescriptionCode) and not(exists(cbc:StartDate)) and not(exists(cbc:EndDate)))

All rule notes · JSON · Markdown · llms.txt · Invoice page · Privacy