einvoice / EN 16931 / XRechnung rule reference

BR-DE-CVD-03

So beheben Sie den Fehler

In einer Rechnung muss mindestens eine INVOICE LINE (BG-25) enthalten sein, in der der Scheme identifier von "Item classification identifier" (BT-158) den Wert 'CVD' und der "Item attribute name" (BT-160) den Wert 'cva' enthält.

Deutsche Fassung: Amtlicher KoSIT-Text (official KoSIT assert text).

A CVD invoice must contain at least one INVOICE LINE (BG-25) whose Item carries an 'Item classification identifier' (BT-158) with scheme identifier 'CVD' AND an 'Item attribute name' (BT-160) with the value 'cva' — both on the SAME cac:Item.

Requires
a CVD invoice must contain at least one INVOICE LINE (BG-25) whose Item carries an 'Item classification identifier' (BT-158) with scheme identifier 'CVD' AND an 'Item attribute name' (BT-160) with the value 'cva' — both on the SAME cac:Item.
Business terms
BG-25 BT-158 BT-160
Syntax
Binds the UBL-2.1 Invoice / CreditNote syntax and the UN/CEFACT-CII syntax
Location (UBL-2.1 path)
cac:InvoiceLine/cac:Item
Fix (Deutsch)
Ergänzen Sie das erforderliche Element bei `cac:InvoiceLine/cac:Item`: In einer Rechnung muss mindestens eine INVOICE LINE (BG-25) enthalten sein, in der der Scheme identifier von "Item classification identifier" (BT-158) den Wert 'CVD' und der "Item attribute name" (BT-160) den Wert 'cva' enthält.
Fix
Add the required element at `cac:InvoiceLine/cac:Item`: a CVD invoice must contain at least one INVOICE LINE (BG-25) whose Item carries an 'Item classification identifier' (BT-158) with scheme identifier 'CVD' AND an 'Item attribute name' (BT-160) with the value 'cva' — both on the SAME cac:Item.
Severity
fatal
Provenance source
xrechnung-ubl
Provenance assert

In einer Rechnung muss mindestens eine INVOICE LINE (BG-25) enthalten sein, in der der Scheme identifier von "Item classification identifier" (BT-158) den Wert 'CVD' und der "Item attribute name" (BT-160) den Wert 'cva' enthält.

The Location above is a UBL-2.1 path, and no UN/CEFACT-CII path for this rule is published here; Fix and Fix (Deutsch), verbatim from remediation_catalog.json and not reworded here; the UN/CEFACT-CII binding of this rule is differentially proven against the official KoSIT XRechnung 2.5.0 (XRechnung 3.0.2) Schematron.

Korrektur prüfen: Laden Sie die geänderte Rechnung in den Browser-Validator unter /einvoice/validate/ — er führt dieselbe Engine lokal im Browser aus, ohne Upload, und meldet BR-DE-CVD-03 nicht mehr, sobald die Korrektur greift.

Where to check the fix: paste the corrected invoice into the browser validator at /einvoice/validate/ — it runs this same engine locally in your browser, with no upload, and stops reporting BR-DE-CVD-03 once the edit lands.

The same invoice, failing and fixed

No vendored test suite ships a labelled example for this rule, so this pair was found rather than written. The engine was run over the vendored instance corpus/xrechnung-testsuite/src/test/technical-cases/cvd/02.01a-cvd_INVOICE_ubl.xml under --profile xrechnung, then re-run over the same file with one mechanical edit applied to one element, over and over, until the edit below changed the verdict: the ItemClassificationCode element was deleted. The page publishes it because the engine reported BR-DE-CVD-03 for the edited document and did not report it for the untouched one.

UBL Invoice (CVD profile) — fails

The vendored file around the change, verbatim:

<cac:CommodityClassification>
</cac:CommodityClassification>

UBL Invoice (CVD profile) — passes

The same lines as 02.01a-cvd_INVOICE_ubl.xml actually ships them — this block is the fix for the block above:

<cac:CommodityClassification>
  <cbc:ItemClassificationCode listID="CVD">M2</cbc:ItemClassificationCode>
</cac:CommodityClassification>

What the engine reports for the edited invoice

{
  "element": "cac:InvoiceLine/cac:Item",
  "field": "cac:InvoiceLine/cac:Item",
  "fix_hint": "Add the required element at `cac:InvoiceLine/cac:Item`: a CVD invoice must contain at least one INVOICE LINE (BG-25) whose Item carries an 'Item classification identifier' (BT-158) with scheme identifier 'CVD' AND an 'Item attribute name' (BT-160) with the value 'cva' — both on the SAME cac:Item.",
  "location": "cac:InvoiceLine/cac:Item",
  "message": "A Clean-Vehicle-Directive invoice must contain at least one INVOICE LINE (BG-25) in which the scheme identifier of 'Item classification identifier' (BT-158) is 'CVD' and the 'Item attribute name' (BT-160) is 'cva'.",
  "rule": "BR-DE-CVD-03",
  "severity": "fatal",
  "terms": [
    "BG-25",
    "BT-158",
    "BT-160"
  ],
  "title": "A CVD invoice must contain at least one INVOICE LINE (BG-25) whose Item carries an 'Item classification identifier' (BT-158) with scheme identifier 'CVD' AND an 'Item attribute name' (BT-160) with the value 'cva' — both on the SAME cac:Item."
}

Rule ids the engine reports for 02.01a-cvd_INVOICE_ubl.xml untouched: BR-CL-13. After the edit, BR-DE-CVD-03 BR-DE-CVD-06-b are reported that were not before — one mechanical edit can break more than one rule at a time, and BR-DE-CVD-06-b is the neighbour this one takes with it.

Two honest limits. This is an edit that provokes the rule, not the only one, and it is not a claim about how real exporters break it. And it is the reverse of the fix a reader needs: the passing block is the vendored file's own content, which is what a conformant invoice looks like here.

Reproduce it yourself: take corpus/xrechnung-testsuite/src/test/technical-cases/cvd/02.01a-cvd_INVOICE_ubl.xml from this repository, apply the one edit named above, and run einvoice validate 02.01a-cvd_INVOICE_ubl.xml --profile xrechnung --format json, or paste the file into the browser validator, which runs this same engine locally with no upload.

Everything here is free and open source — pick up whatever helps, at your own pace: