# BR-DE-TMP-32: Delivery date or service period missing

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

An XRechnung should state when the supply was made: the actual delivery date (BT-72), an invoicing period (BG-14), or a line period (BG-26) on every line. Below: the message, the cause and the fix, and an invoice our validator checked, failing and fixed.

- **Specification:** [XRechnung 3.0 rules](/einvoice-rules/xrechnung), XRechnung 3.0.2 schematron 2.6.0
- **Severity:** information
- **Business terms:** BT-72, BG-14, BG-26
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-DE-TMP-32 is a rule of the XRechnung 3.0 rules (xrechnung-schematron 2.6.0 (XRechnung 3.0.2)) for UBL and CII. It is information: reported, never rejected.

```text
[BR-DE-TMP-32] Eine Rechnung sollte zur Angabe des Liefer-/Leistungsdatums entweder BT-72 "Actual delivery date", BG-14 "Invoicing period" oder in jeder Rechnungsposition BG-26 "Invoice line period" enthalten.
```

## What it checks

An XRechnung should state when the supply was made: the actual delivery date (BT-72), an invoicing period (BG-14), or a line period (BG-26) on every line. It is reported as information: § 14 (4) UStG requires the date of supply, but the rule does not reject the invoice.

## Why invoices fail it

The delivery date is assumed to be the invoice date and not written.

## How to fix it

Write the delivery date in BT-72 or the service period in BG-14; « Leistungsdatum entspricht Rechnungsdatum » in a note does not satisfy the rule.

## 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 XRechnung 3.0 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-DE-TMP-32.

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-DE-TMP-32** | information | `/ubl:Invoice` | [BR-DE-TMP-32] Eine Rechnung sollte zur Angabe des Liefer-/Leistungsdatums entweder BT-72 "Actual delivery date", BG-14 "Invoicing period" oder in jeder Rechnungsposition BG-26 "Invoice line period" enthalten. |

```diff
  …
      </cac:Party>
    </cac:AccountingCustomerParty>
+   <cac:Delivery>
+     <cbc:ActualDeliveryDate>2026-10-15</cbc:ActualDeliveryDate>
+   </cac:Delivery>
    <cac:PaymentMeans>
      <cbc:PaymentMeansCode>58</cbc:PaymentMeansCode>
  …
```

## The rule as published

Where the rule applies (`context`) and what must hold (`test`), unmodified from XRechnung 3.0.2 schematron 2.6.0. An `assert` fails when its test is false.

Text and test: © KoSIT, Apache License 2.0. Quoted unmodified; the explanations on this page are Veriport’s.

```xpath
context: /ubl:Invoice | /cn:CreditNote
test:    cac:Delivery/cbc:ActualDeliveryDate or cac:InvoicePeriod or (every $line in (cac:InvoiceLine | cac:CreditNoteLine) satisfies $line/cac:InvoicePeriod)
```

```xpath
context: /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction
test:    ram:ApplicableHeaderTradeDelivery/ram:ActualDeliverySupplyChainEvent/ram:OccurrenceDateTime or ram:ApplicableHeaderTradeSettlement/ram:BillingSpecifiedPeriod or (every $line in ram:IncludedSupplyChainTradeLineItem satisfies $line/ram:SpecifiedLineTradeSettlement/ram:BillingSpecifiedPeriod)
```

## 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-IC-11: Intra-Community supply without a delivery date](https://veriport.io/einvoice-rules/br-ic-11)
- [BR-CO-19: Empty invoicing period (BG-14)](https://veriport.io/einvoice-rules/br-co-19)
- [BR-CO-20: Empty line period (BG-26)](https://veriport.io/einvoice-rules/br-co-20)
- [All XRechnung 3.0 rules](https://veriport.io/einvoice-rules/xrechnung)
- [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

- XRechnung — the German CIUS of EN 16931 (standard, versions and bundles; version 3.0.2 in force) — https://xeinkauf.de/xrechnung/ (2026-10-28)
- Validator configuration XRechnung v2026-08-31 (XRechnung 3.0.2, CEN schematron 1.3.16, xrechnung-schematron 2.6.0) — https://github.com/itplr-kosit/validator-configuration-xrechnung/releases/tag/v2026-08-31 (2026-10-28)
- XRechnung schematron (xrechnung-schematron) and the XRechnung validator configuration: licence, Apache License 2.0 (LICENSE files; NOTICE of the configuration: « Copyright 2020 Koordinierungsstelle für IT-Standards ») — https://github.com/itplr-kosit/xrechnung-schematron/blob/master/LICENSE (2026-11-17)
