BR-TMP-2

Where the invoice points at an externally stored document (BT-124), the value must be a complete, absolute address including its scheme — https://example.com/attachment.pdf, not a file name, a drive path, or an address with no https:// in front of it.

Severity: Error
Applies to: CII, UBL
Rule set: v2026-08-31
Checked on: 4 September 2026

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

Official rule text

BT-124 "External document location" muss eine absolute URL mit gültigem Schema enthalten.

Why does BR-TMP-2 happen?

The value is usually copied straight out of an in-house document management system, where relative paths and network drives are normal. The recipient cannot resolve one: it points at a machine that does not exist on their side.

How do you fix BR-TMP-2?

Write an absolute URL including the scheme — cac:AdditionalDocumentReference/cac:Attachment/cac:ExternalReference/cbc:URI in UBL, ram:URIID in CII. If the document is not publicly reachable, attach it as an embedded object instead of shipping an internal path.

In the XML

A UBL fragment. The CII path is named above — same change, different element names.

Fails

<cac:AdditionalDocumentReference>
  <cbc:ID>ANL-2026-0042</cbc:ID>
  <cac:Attachment>
    <cac:ExternalReference>
      <cbc:URI>www.beispiel.de/anlagen/stundennachweis.pdf</cbc:URI>
    </cac:ExternalReference>
  </cac:Attachment>
</cac:AdditionalDocumentReference>

Fixed

<cac:AdditionalDocumentReference>
  <cbc:ID>ANL-2026-0042</cbc:ID>
  <cac:Attachment>
    <cac:ExternalReference>
      <cbc:URI>https://www.beispiel.de/anlagen/stundennachweis.pdf</cbc:URI>
    </cac:ExternalReference>
  </cac:Attachment>
</cac:AdditionalDocumentReference>

NormAPI provides technical validation, not tax or legal advice.