# BR-CO-20: Empty line period (BG-26)

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

If an invoice line period (BG-26) is present, it must contain a start date (BT-134), an end date (BT-135) 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-134, BT-135, BG-26
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-CO-20 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-20]-If Invoice line period (BG-26) is used, the Invoice line period start date (BT-134) or the Invoice line period end date (BT-135) shall be filled, or both.
```

## What it checks

If an invoice line period (BG-26) is present, it must contain a start date (BT-134), an end date (BT-135) or both.

## Why invoices fail it

The line period element is generated for every line, empty when the line has no period.

## How to fix it

Write the line period only for lines that have one.

## 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-20 and 1 other rule, as a real file with this mistake would.

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-CO-20** | error | `/ubl:Invoice/cac:InvoiceLine[1]/cac:InvoicePeriod` | If Invoice line period (BG-26) is used, the Invoice line period start date (BT-134) or the Invoice line period end date (BT-135) shall be filled, or both. |
| [UBL-CR-524](/einvoice-rules/ubl-cr-524) | warning | `/ubl:Invoice` | A UBL invoice should not include the InvoiceLine InvoicePeriod Description |

```diff
  …
      <cbc:InvoicedQuantity unitCode="HUR">24.00</cbc:InvoicedQuantity>
      <cbc:LineExtensionAmount currencyID="EUR">2280.00</cbc:LineExtensionAmount>
-     <cac:InvoicePeriod>
-       <cbc:Description>Oktober 2026</cbc:Description>
-     </cac:InvoicePeriod>
      <cac:Item>
        <cbc:Name>Relaunch Website, Konzeption und Umsetzung</cbc:Name>
  …
```

## 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:InvoiceLine/cac:InvoicePeriod | cac:CreditNoteLine/cac:InvoicePeriod
test:    exists(cbc:StartDate) or exists(cbc:EndDate)
```

```xpath
context: //ram:SpecifiedLineTradeSettlement/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-18: At least one VAT breakdown (BG-23)](https://veriport.io/einvoice-rules/br-co-18)
- [BR-CO-19: Empty invoicing period (BG-14)](https://veriport.io/einvoice-rules/br-co-19)
- [BR-CO-21: Document allowance without a reason](https://veriport.io/einvoice-rules/br-co-21)
- [BR-CO-22: Document charge without a reason](https://veriport.io/einvoice-rules/br-co-22)
- [BR-30: Line period ends before it starts](https://veriport.io/einvoice-rules/br-30)
- [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)
