# BR-TMP-7: CII date without format 102

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

In CII, every date (`udt:DateTimeString`, `qdt:DateTimeString`, `udt:DateString`) must carry `format="102"` and be written as YYYYMMDD. 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:** warning
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-TMP-7 is a rule of the XRechnung 3.0 rules (xrechnung-schematron 2.6.0 (XRechnung 3.0.2)) for CII. It is a warning: the invoice stays valid, but should be corrected.

```text
[BR-TMP-7] Datumsangaben in UNCEFACT/CII müssen das Attribut format="102" tragen und im Format JJJJMMTT (YYYYMMDD) übermittelt werden.
```

## What it checks

In CII, every date (`udt:DateTimeString`, `qdt:DateTimeString`, `udt:DateString`) must carry `format="102"` and be written as YYYYMMDD. It is a warning in XRechnung.

## Why invoices fail it

The ISO form 2026-10-20 is written, or the format attribute is left out.

## How to fix it

Write `<udt:DateTimeString format="102">20261020</udt:DateTimeString>`.

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

| Rule | Severity | Where | Message |
|---|---|---|---|
| [CII-DT-097](/einvoice-rules/cii-dt-097) | error | `/rsm:CrossIndustryInvoice/rsm:ExchangedDocument/ram:IssueDateTime/udt:DateTimeString` | Date time string with format attribute 102 shall be YYYYMMDD. |
| **BR-TMP-7** | warning | `/rsm:CrossIndustryInvoice/rsm:ExchangedDocument/ram:IssueDateTime/udt:DateTimeString` | Datumsangaben in UNCEFACT/CII müssen das Attribut format="102" tragen und im Format JJJJMMTT (YYYYMMDD) übermittelt werden. |

```diff
  …
      <ram:TypeCode>380</ram:TypeCode>
      <ram:IssueDateTime>
-       <udt:DateTimeString format="102">2026-10-20</udt:DateTimeString>
+       <udt:DateTimeString format="102">20261020</udt:DateTimeString>
      </ram:IssueDateTime>
    </rsm:ExchangedDocument>
  …
```

## 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: udt:DateTimeString | qdt:DateTimeString | udt:DateString
test:    normalize-space(@format) = '102' and matches(normalize-space(text()), '^\d{8}$')
```

## 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-TMP-5: Two attachments in one document reference (CII)](https://veriport.io/einvoice-rules/br-tmp-5)
- [BR-TMP-6: UBL date not in YYYY-MM-DD form](https://veriport.io/einvoice-rules/br-tmp-6)
- [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)
