# BR-30: Line period ends before it starts

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

When an invoice line period (BG-26) has both dates, its end date (BT-135) must be on or after its start date (BT-134): `cac:InvoicePeriod` of the line in UBL, `ram:BillingSpecifiedPeriod` of the line settlement in CII. 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
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-30 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-30]-If both Invoice line period start date (BT-134) and Invoice line period end date (BT-135) are given then the Invoice line period end date (BT-135) shall be later or equal to the Invoice line period start date (BT-134).
```

## What it checks

When an invoice line period (BG-26) has both dates, its end date (BT-135) must be on or after its start date (BT-134): `cac:InvoicePeriod` of the line in UBL, `ram:BillingSpecifiedPeriod` of the line settlement in CII.

## Why invoices fail it

Start and end of a subscription or rental line are swapped, or the end is computed as start minus one day.

## How to fix it

Write the first day of the line period in BT-134 and the last in BT-135.

## 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-30.

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-30** | error | `/ubl:Invoice/cac:InvoiceLine[1]/cac:InvoicePeriod` | If both Invoice line period start date (BT-134) and Invoice line period end date (BT-135) are given then the Invoice line period end date (BT-135) shall be later or equal to the Invoice line period start date (BT-134). |

```diff
  …
      <cbc:LineExtensionAmount currencyID="EUR">2280.00</cbc:LineExtensionAmount>
      <cac:InvoicePeriod>
-       <cbc:StartDate>2026-10-31</cbc:StartDate>
-       <cbc:EndDate>2026-10-01</cbc:EndDate>
+       <cbc:StartDate>2026-10-01</cbc:StartDate>
+       <cbc:EndDate>2026-10-31</cbc:EndDate>
      </cac:InvoicePeriod>
      <cac:Item>
  …
```

## 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:EndDate) and exists(cbc:StartDate) and xs:date(cbc:EndDate) >= xs:date(cbc:StartDate)) or not(exists(cbc:StartDate)) or not(exists(cbc:EndDate))
```

```xpath
context: //ram:SpecifiedLineTradeSettlement/ram:BillingSpecifiedPeriod
test:    (ram:EndDateTime/udt:DateTimeString[@format = '102']) >= (ram:StartDateTime/udt:DateTimeString[@format = '102']) or not (ram:EndDateTime) or not (ram:StartDateTime)
```

## 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-28: Item gross price (BT-148) negative](https://veriport.io/einvoice-rules/br-28)
- [BR-29: Invoicing period ends before it starts](https://veriport.io/einvoice-rules/br-29)
- [BR-31: Document allowance amount (BT-92) missing](https://veriport.io/einvoice-rules/br-31)
- [BR-32: Document allowance VAT category (BT-95) missing](https://veriport.io/einvoice-rules/br-32)
- [BR-CO-20: Empty line period (BG-26)](https://veriport.io/einvoice-rules/br-co-20)
- [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)
