einvoice / EN 16931 / XRechnung rule reference

BR-DE-CVD-06-a

So beheben Sie den Fehler

Wenn der Scheme identifier von "Item classification identifier" (BT-158) mit dem Wert 'CVD' angegeben ist, muss in derselben Rechnungszeile genau ein "Item attribute name" (BT-160) mit dem Wert 'cva' vorhanden sein.

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

In a CVD invoice line whose Item carries an 'Item classification identifier' (BT-158) with scheme identifier 'CVD', exactly one 'Item attribute name' (BT-160) with the value 'cva' must be present on that Item.

Requires
in a CVD invoice line whose Item carries an 'Item classification identifier' (BT-158) with scheme identifier 'CVD', exactly one 'Item attribute name' (BT-160) with the value 'cva' must be present on that Item.
Business terms
BT-158 BT-160
Syntax
Binds the UBL-2.1 Invoice / CreditNote syntax and the UN/CEFACT-CII syntax
Location (UBL-2.1 path)
/ubl:Invoice/cac:InvoiceLine/cac:Item
Fix (Deutsch)
Korrigieren Sie `/ubl:Invoice/cac:InvoiceLine/cac:Item`, sodass gilt: Wenn der Scheme identifier von "Item classification identifier" (BT-158) mit dem Wert 'CVD' angegeben ist, muss in derselben Rechnungszeile genau ein "Item attribute name" (BT-160) mit dem Wert 'cva' vorhanden sein.
Fix
Correct `/ubl:Invoice/cac:InvoiceLine/cac:Item` so that in a CVD invoice line whose Item carries an 'Item classification identifier' (BT-158) with scheme identifier 'CVD', exactly one 'Item attribute name' (BT-160) with the value 'cva' must be present on that Item.
Severity
fatal
Provenance source
xrechnung-ubl
Provenance assert

Wenn der Scheme identifier von "Item classification identifier" (BT-158) mit dem Wert 'CVD' angegeben ist, muss in derselben Rechnungszeile genau ein "Item attribute name" (BT-160) mit dem Wert 'cva' vorhanden sein.

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-06-a 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-06-a 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 text content of Name was deleted, leaving the element present but empty. The page publishes it because the engine reported BR-DE-CVD-06-a 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:AdditionalItemProperty>
  <cbc:Name></cbc:Name>
  <cbc:Value>clean</cbc:Value>
</cac:AdditionalItemProperty>

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:AdditionalItemProperty>
  <cbc:Name>cva</cbc:Name>
  <cbc:Value>clean</cbc:Value>
</cac:AdditionalItemProperty>

What the engine reports for the edited invoice

{
  "element": "cac:InvoiceLine/cac:Item/cac:AdditionalItemProperty/cbc:Name",
  "field": "cac:InvoiceLine/cac:Item/cac:AdditionalItemProperty/cbc:Name",
  "fix_hint": "Correct `/ubl:Invoice/cac:InvoiceLine/cac:Item` so that in a CVD invoice line whose Item carries an 'Item classification identifier' (BT-158) with scheme identifier 'CVD', exactly one 'Item attribute name' (BT-160) with the value 'cva' must be present on that Item.",
  "location": "/ubl:Invoice/cac:InvoiceLine/cac:Item",
  "message": "An Item with a BT-158 scheme identifier 'CVD' must carry exactly one 'Item attribute name' (BT-160) with the value 'cva' in the same invoice line.",
  "rule": "BR-DE-CVD-06-a",
  "severity": "fatal",
  "terms": [
    "BT-158",
    "BT-160"
  ],
  "title": "In a CVD invoice line whose Item carries an 'Item classification identifier' (BT-158) with scheme identifier 'CVD', exactly one 'Item attribute name' (BT-160) with the value 'cva' must be present on that 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-a are reported that were not before — one mechanical edit can break more than one rule at a time, and BR-DE-CVD-03 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: