BR-TMP-6

Every date in a UBL XRechnung must be written as YYYY-MM-DD, for example 2026-08-26. This applies to all date fields alike: issue date, due date, delivery period.

Severity
Warning
Applies to
UBL
Rule set
v2026-08-31
Checked on

Written and checked against the official KoSIT rule set by Dmytro Yalanskyi, NormAPI.

Official rule text

Datumsangaben in UBL müssen im Format JJJJ-MM-TT (YYYY-MM-DD) übermittelt werden.

Why does BR-TMP-6 happen?

The German display format 26.08.2026 ends up in the data because the date is taken from the invoice template as an already formatted string rather than as a date value. US ordering and appended times fall into the same trap.

How do you fix BR-TMP-6?

Format date values explicitly as ISO 8601 (YYYY-MM-DD) when writing the XML, and never reuse the output of the presentation layer. A time of day does not belong in a date field — see BR-TMP-7 for the same rule in CII.

In the XML

A UBL fragment — the rule applies to that syntax only.

Fails
<cbc:IssueDate>26.08.2026</cbc:IssueDate>
<cbc:DueDate>2026-09-25T00:00:00</cbc:DueDate>
Fixed
<cbc:IssueDate>2026-08-26</cbc:IssueDate>
<cbc:DueDate>2026-09-25</cbc:DueDate>

NormAPI provides technical validation, not tax or legal advice.