BR-DE-CVD-06-b: « cva » attribute without CVD classification

A line with an item attribute « cva » (BT-160) must carry exactly one item classification with scheme CVD (BT-158). Below: the message, the cause and the fix.

The message validators print

BR-DE-CVD-06-b 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-06-b] Wenn … "Item attribute name" (BT-160) mit dem Wert 'cva' angegeben ist, muss in derselben Rechnungszeile genau ein … "Item classification identifier" (BT-158) mit dem Scheme identifier 'CVD' vorhanden sein.

What it checks

A line with an item attribute « cva » (BT-160) must carry exactly one item classification with scheme CVD (BT-158).

Why invoices fail it

The attribute was added but the classification uses another scheme, or appears twice.

How to fix it

Add exactly one ItemClassificationCode with listID="CVD" to the line.

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
test:    not(cac:AdditionalItemProperty[cbc:Name = 'cva']) or count(cac:CommodityClassification/cbc:ItemClassificationCode[@listID = 'CVD']) = 1
CII · XRechnung 3.0.2 schematron (CII) 2.6.0 · assert · error
context: /rsm:CrossIndustryInvoice[$isCVD]/rsm:SupplyChainTradeTransaction/ram:IncludedSupplyChainTradeLineItem/ram:SpecifiedTradeProduct
test:    not(ram:ApplicableProductCharacteristic/ram:Description = 'cva') or count(ram:DesignatedProductClassification/ram:ClassCode[@listID = 'CVD']) = 1

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