BR-DE-CVD-02: CVD invoice without tender reference (BT-17)

A CVD XRechnung must carry the tender or lot reference, BT-17 (cac:OriginatorDocumentReference/cbc:ID in UBL), linking the vehicle to the procurement procedure. Below: the message, the cause and the fix.

The message validators print

BR-DE-CVD-02 is a rule of the XRechnung 3.0 rules (xrechnung-schematron 2.6.0 (XRechnung 3.0.2)) for UBL and CII. It is an error (fatal): a validator rejects the invoice.

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

What it checks

A CVD XRechnung must carry the tender or lot reference, BT-17 (cac:OriginatorDocumentReference/cbc:ID in UBL), linking the vehicle to the procurement procedure.

Why invoices fail it

The award notice number is not part of the invoice data.

How to fix it

Write the tender or lot reference of the procurement in BT-17.

No checked example yet

A CVD invoice classifies the vehicle with listID="CVD", which the CEN rule BR-CL-13 (UNTDID 7143 only) rejects: with the published files no CVD invoice passes both rule sets at once, so no valid fix can be shown. The page is not indexed until that is resolved.

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.

UBL · XRechnung 3.0.2 schematron (UBL) 2.6.0 · assert · error
context: (/ubl:Invoice | /cn:CreditNote)[$isCVD]
test:    cac:OriginatorDocumentReference/cbc:ID[boolean(normalize-space(.))]
CII · XRechnung 3.0.2 schematron (CII) 2.6.0 · assert · error
context: /rsm:CrossIndustryInvoice[$isCVD]/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement
test:    ram:AdditionalReferencedDocument[normalize-space(ram:TypeCode) = '50' and normalize-space(ram:IssuerAssignedID)]

Check your own invoice

Drop your XRechnung, ZUGFeRD or Peppol file into a free validator (Peppol BIS, XRechnung, Factur-X): each runs the same rule files and links every finding to its rule page. From your own code, POST /einvoice/validate (reference) returns the same check as JSON, each finding with an explanation field pointing here (5 calls a check, anonymous within the daily allowance).

Sources