# BR-CO-19: Empty invoicing period (BG-14)

Source: https://veriport.io/einvoice-rules/br-co-19 (published 2026-11-17)

If the invoicing period group (BG-14: `cac:InvoicePeriod` in UBL, `ram:BillingSpecifiedPeriod` in CII) is present, it must contain a start date (BT-73), an end date (BT-74) or both. Below: the message, the cause and the fix, and an invoice our validator checked, failing and fixed.

- **Specification:** [EN 16931 business rules](/einvoice-rules/en16931), CEN EN 16931 validation artefacts 1.3.16
- **Severity:** error
- **Business terms:** BT-73, BT-74, BG-14
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-CO-19 is a rule of the EN 16931 business rules (CEN validation artefacts 1.3.16) for UBL and CII. It is an error (fatal): a validator rejects the invoice.

```text
[BR-CO-19]-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.
```

## What it checks

If the invoicing period group (BG-14: `cac:InvoicePeriod` in UBL, `ram:BillingSpecifiedPeriod` in CII) is present, it must contain a start date (BT-73), an end date (BT-74) or both.

## Why invoices fail it

The period element is written empty when the period fields are blank, or holds only a description code in CII.

## How to fix it

Write the period’s start and end dates, or leave the group out.

## A failing invoice and its fix, checked

We start from our sample invoice (two lines at 19 %, Berlin to Stuttgart), written by our own generator as EN 16931 in UBL. The change below (`-` the failing version, `+` the fixed one) makes the rule fail. Both versions went through our validator on 2026-11-17 (the XML schema and the official rule files, as `POST /einvoice/validate` runs them): the fixed one is valid, the failing one reports BR-CO-19 and 1 other rule, as a real file with this mistake would.

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-CO-19** | error | `/ubl:Invoice/cac:InvoicePeriod` | 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. |
| [UBL-CR-015](/einvoice-rules/ubl-cr-015) | warning | `/ubl:Invoice` | A UBL invoice should not include the InvoicePeriod Description |

```diff
  …
    <cbc:DocumentCurrencyCode>EUR</cbc:DocumentCurrencyCode>
    <cbc:BuyerReference>EK-2026-0345</cbc:BuyerReference>
-   <cac:InvoicePeriod>
-     <cbc:Description>Oktober 2026</cbc:Description>
-   </cac:InvoicePeriod>
    <cac:AccountingSupplierParty>
      <cac:Party>
  …
```

## The rule as published

Where the rule applies (`context`) and what must hold (`test`), unmodified from CEN EN 16931 validation artefacts 1.3.16. An `assert` fails when its test is false.

Text and test: © CEN/TC 434, EN 16931 validation artefacts, EUPL 1.2. Quoted unmodified; the explanations on this page are Veriport’s.

```xpath
context: cac:InvoicePeriod
test:    exists(cbc:StartDate) or exists(cbc:EndDate) or (exists(cbc:DescriptionCode) and not(exists(cbc:StartDate)) and not(exists(cbc:EndDate)))
```

```xpath
context: //ram:ApplicableHeaderTradeSettlement/ram:BillingSpecifiedPeriod
test:    (ram:StartDateTime) or (ram:EndDateTime)
```

## Check your own invoice

Drop your XRechnung, ZUGFeRD or Peppol file into a free validator ([Peppol BIS](/tools/peppol-validator), [XRechnung](/tools/xrechnung-pruefen), [Factur-X](/tools/valider-factur-x)): each runs the same rule files and links every finding to its rule page. From your own code, `POST /einvoice/validate` ([reference](/docs/einvoice)) returns the same check as JSON, each finding with an `explanation` field pointing here (5 calls a check, anonymous within the daily allowance).

## Read next

- [BR-CO-17: VAT amount (BT-117) ≠ taxable amount × rate](https://veriport.io/einvoice-rules/br-co-17)
- [BR-CO-18: At least one VAT breakdown (BG-23)](https://veriport.io/einvoice-rules/br-co-18)
- [BR-CO-20: Empty line period (BG-26)](https://veriport.io/einvoice-rules/br-co-20)
- [BR-CO-21: Document allowance without a reason](https://veriport.io/einvoice-rules/br-co-21)
- [BR-29: Invoicing period ends before it starts](https://veriport.io/einvoice-rules/br-29)
- [BR-DE-TMP-32: Delivery date or service period missing](https://veriport.io/einvoice-rules/br-de-tmp-32)
- [All EN 16931 business rules](https://veriport.io/einvoice-rules/en16931)
- [All e-invoice rules, search](https://veriport.io/einvoice-rules)
- [Check an e-invoice free (XRechnung prüfen)](https://veriport.io/tools/xrechnung-pruefen)
- [Create a valid e-invoice free (German form)](https://veriport.io/tools/e-rechnung-erstellen)

## Sources

- EN 16931 validation artefacts 1.3.16 (UBL and CII schematron, the business rules BR-*) — https://github.com/ConnectingEurope/eInvoicing-EN16931/releases/tag/validation-1.3.16 (2026-10-28)
- EN 16931 validation artefacts: licence, European Union Public Licence (EUPL) v1.2 (LICENSE.txt, the README « License » section and the release notes of validation-1.3.16) — https://github.com/ConnectingEurope/eInvoicing-EN16931/blob/master/LICENSE.txt (2026-11-17)
