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.
- Specification: XRechnung 3.0 rules, XRechnung 3.0.2 schematron 2.6.0
- Severity: error
- Business terms: BT-158, BT-160
- Reported by
POST /einvoice/validateand our free validators, with a link to this page
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.
[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.
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']) = 1context: /rsm:CrossIndustryInvoice[$isCVD]/rsm:SupplyChainTradeTransaction/ram:IncludedSupplyChainTradeLineItem/ram:SpecifiedTradeProduct
test: not(ram:ApplicableProductCharacteristic/ram:Description = 'cva') or count(ram:DesignatedProductClassification/ram:ClassCode[@listID = 'CVD']) = 1Check 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
- XRechnung — the German CIUS of EN 16931 (standard, versions and bundles; version 3.0.2 in force) — KoSIT (Koordinierungsstelle für IT-Standards), Bremen, consulted 2026-10-28
- Validator configuration XRechnung v2026-08-31 (XRechnung 3.0.2, CEN schematron 1.3.16, xrechnung-schematron 2.6.0) — KoSIT, consulted 2026-10-28
- XRechnung schematron (xrechnung-schematron) and the XRechnung validator configuration: licence, Apache License 2.0 (LICENSE files; NOTICE of the configuration: « Copyright 2020 Koordinierungsstelle für IT-Standards ») — KoSIT (Koordinierungsstelle für IT-Standards), Bremen, consulted 2026-11-17. Apache 2.0 permits redistribution with the licence and the notices kept. KoSIT’s LICENSE adds that the copyright in the EN 16931 standard lies with CEN. The rule library quotes the BR-DE-*, BR-DEX-* and BR-TMP-* messages unmodified, in KoSIT’s German.