BR-DE-CVD-01: CVD invoice without contract reference (BT-12)

An XRechnung declared for the Clean Vehicles Directive reporting (the CVD use of XRechnung, for vehicles procured under the Saubere-Fahrzeuge-Beschaffungs-Gesetz) must carry the contract reference, BT-12. Below: the message, the cause and the fix.

The message validators print

BR-DE-CVD-01 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-01] Das Element … "Contract reference" (BT-12) muss übermittelt werden.

What it checks

An XRechnung declared for the Clean Vehicles Directive reporting (the CVD use of XRechnung, for vehicles procured under the Saubere-Fahrzeuge-Beschaffungs-Gesetz) must carry the contract reference, BT-12.

Why invoices fail it

The CVD identifier is used in BT-24 but the contract number is not mapped.

How to fix it

Write the contract reference (cac:ContractDocumentReference/cbc:ID, ram:ContractReferencedDocument/ram:IssuerAssignedID), or use the plain XRechnung identifier if the invoice is not a CVD report.

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:ContractDocumentReference/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:ContractReferencedDocument/ram:IssuerAssignedID[boolean(normalize-space(.))]

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