BR-03An Invoice shall have an Invoice issue date (BT-2).
Official rule text
The invoice must carry an issue date (BT-2) — the date it was issued, not the date of supply and not the date it was sent.
- Severity
- Error
- Applies to
- CII, UBL
- Rule set
- v2026-08-31
- Checked on
Written and checked against the official KoSIT rule set by Dmytro Yalanskyi, NormAPI.
Why does BR-03 happen?
Usually a format problem rather than a missing value, and it behaves differently per syntax. In UBL, BR-03 only checks that the field is not empty; a timestamp instead of a date is rejected by the schema, not by this rule. In CII, BR-03 itself fires.
What the validator checks
The expression the official KoSIT rule set evaluates — not paraphrased, but read from the Schematron file it ships. UBL and CII address different document trees, so the same rule reads differently in each.
- UBL
normalize-space(cbc:IssueDate) != ''- CII
normalize-space(rsm:ExchangedDocument/ram:IssueDateTime/udt:DateTimeString[@format='102']) != ''
Source: rule set v2026-08-31
How do you fix BR-03?
Send BT-2 as YYYY-MM-DD in UBL. In CII, write the value as eight digits and set format="102" on the udt:DateTimeString — the expression behind BR-03 selects exactly that element, so with 610 there it finds nothing and reports a missing issue date. It is not only the BR-TMP-7 warning that fires: the invoice is refused.
In the XML
A UBL fragment. The CII path is named above — same change, different element names.
<cbc:ID>RE-2026-0042</cbc:ID>
<cbc:IssueDate>26.08.2026</cbc:IssueDate><cbc:ID>RE-2026-0042</cbc:ID>
<cbc:IssueDate>2026-08-26</cbc:IssueDate>Related rules
NormAPI provides technical validation, not tax or legal advice.