What causes the BR-DE-CVD-06-b error?

This error occurs when an invoice line has a clean vehicle attribute (cva) in AdditionalItemProperty but is missing the required CVD classification in CommodityClassification.

Is BR-DE-CVD-06-b a critical error?

Yes, for XRechnung CVD invoices this is a fatal error. The invoice will be rejected if the CVD classification is missing when cva is present.

Can BR-DE-CVD-06-b be automatically fixed?

Yes, if the cva value contains the vehicle category code, it can be used to automatically add the missing CVD classification.

Error codes · XRechnung · Germany

BR-DE-CVD-06-bIn your invoicing software

Missing CVD Classification for Clean Vehicle Attribute

Q: How do I fix BR-DE-CVD-06-b?

Add a CommodityClassification element with ItemClassificationCode[@listID="CVD"] containing the vehicle category code (M1, N1, etc.) to the invoice line that has the cva property.

This is the rejection, word for word: „[BR-DE-CVD-06-b] When an invoice line has an AdditionalItemProperty with Name="cva" (clean vehicle attribute), it must also have exactly one CommodityClassification with ItemClassificationCode[@listID="CVD"] containing the vehicle category. This is required for German XRechnung invoices under the Clean Vehicle Directive.“

XPath: cac:InvoiceLine/cac:Item/cac:CommodityClassification/cbc:ItemClassificationCode[@listID="CVD"]. When BT-160 (Item attribute name) equals "cva", there must be exactly one BT-158 (Item classification identifier) with scheme identifier "CVD".

What to have readyNothing. The file has to be re-exported from your invoicing software; we check it again afterwards.

What we doInvoice Navigator automatically fixes this issue by updating the BT-160 field in your Invoice.

Choose the rejected invoiceor drop it here

XRechnung XML or ZUGFeRD PDF. Checking is free · corrected file €1.90 · the first every 30 days is free · no sign-up.

If you enter it yourself in your invoicing software

Before

<Invoice>
  <!-- Issue: When Item attribute name (BT-160) has value "cva", there mus -->
</Invoice>

After

<Invoice>
  <!-- Issue resolved per XRechnung (Germany) -->
</Invoice>

Element order is part of the rule: if the element sits in the wrong place, the validator rejects with BR-DE-CVD-06-b.

What the finding looks likeExample

FindingStructure invalid · BR-DE-CVD-06-b

Location//ext:UBLExtensions/ext:UBLExtension[not(contains(ext:ExtensionURI,'xrechnung'))]

From youA re-exported file

ThenRe-export

ProofSHA-256 and /verify link after the check

Often appears together with

BR-DE-01Invalid Leitweg-ID Format BR-DE-02Payment terms text recommended BR-DE-1Eine Rechnung (INVOICE) muss Angaben zu "PAYMENT INSTRUCTIONS" (BG-16)...