BR-DE-CVD-05: CVD attribute « cva » with an invalid value

When an item attribute is named « cva » (BT-160), its value (BT-161) must be one of clean, zero-emission or other (the vehicle’s classification under the directive). Below: the message, the cause and the fix.

The message validators print

BR-DE-CVD-05 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-05] Wenn innerhalb von … ITEM ATTRIBUTES (BG-32) der … "Item attribute name" (BT-160) den Wert 'cva' hat, muss der … "Item attribute value" (BT-161) einen der zulässigen Werte enthalten.

What it checks

When an item attribute is named « cva » (BT-160), its value (BT-161) must be one of clean, zero-emission or other (the vehicle’s classification under the directive).

Why invoices fail it

The attribute carries a description instead of a code.

How to fix it

Write clean, zero-emission or other, in lower case.

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[$isCVD]/cac:InvoiceLine | /cn:CreditNote[$isCVD]/cac:CreditNoteLine)/cac:Item/cac:AdditionalItemProperty[cbc:Name = 'cva']
test:    normalize-space(cbc:Value) = $CVA-CODES
CII · XRechnung 3.0.2 schematron (CII) 2.6.0 · assert · error
context: /rsm:CrossIndustryInvoice[$isCVD]/rsm:SupplyChainTradeTransaction/ram:IncludedSupplyChainTradeLineItem/ram:SpecifiedTradeProduct/ram:ApplicableProductCharacteristic[ram:Description = 'cva']
test:    normalize-space(ram:Value) = $CVA-CODES

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