BR-DE-CVD-02Das Element […] "Tender or lot reference" (BT-17) muss übermittelt werden.

Official rule text

A CVD invoice must carry the tender or lot reference (BT-17) — the identifier of the procurement procedure or lot the invoice belongs to. Only the presence of content is checked. In UBL only cac:OriginatorDocumentReference/cbc:ID counts; in CII, BT-17 has no element of its own but is a ram:AdditionalReferencedDocument, and the expression wants ram:TypeCode 50 and a ram:IssuerAssignedID in the same element.

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-DE-CVD-02 happen?

Systems that produce both syntaxes from one model easily carry the CII construct over into UBL and write the number as a cac:AdditionalDocumentReference with cbc:DocumentTypeCode 50. That does not count — in an invoice a CEN rule even rejects type code 50 in its own right. In a UBL credit note, on the other hand, the form is a natural choice, because the CEN rules allow type code 50 precisely there; yet BR-DE-CVD-02 looks only for cac:OriginatorDocumentReference in credit notes too. In CII the number fails when its document carries type code 916, that of a supporting document (BG-24), or none at all.

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
cac:OriginatorDocumentReference/cbc:ID[boolean(normalize-space(.))]
CII
ram:AdditionalReferencedDocument[normalize-space(ram:TypeCode) = '50' and normalize-space(ram:IssuerAssignedID)]

Source: rule set v2026-08-31

How do you fix BR-DE-CVD-02?

In UBL, write the number as cac:OriginatorDocumentReference/cbc:ID — in an invoice before cac:ContractDocumentReference, in a credit note only after cac:ContractDocumentReference and cac:AdditionalDocumentReference, because the order differs there. In CII it goes into ram:ApplicableHeaderTradeAgreement as a ram:AdditionalReferencedDocument with ram:IssuerAssignedID and ram:TypeCode 50.

In the XML

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

Fails
<cac:ContractDocumentReference>
  <cbc:ID>RV-2026-0815</cbc:ID>
</cac:ContractDocumentReference>
<cac:AdditionalDocumentReference>
  <cbc:ID>VG-2026-017-L2</cbc:ID>
  <cbc:DocumentTypeCode>50</cbc:DocumentTypeCode>
</cac:AdditionalDocumentReference>
Fixed
<cac:OriginatorDocumentReference>
  <cbc:ID>VG-2026-017-L2</cbc:ID>
</cac:OriginatorDocumentReference>
<cac:ContractDocumentReference>
  <cbc:ID>RV-2026-0815</cbc:ID>
</cac:ContractDocumentReference>

Related rules

NormAPI provides technical validation, not tax or legal advice.