BR-DE-CVD-06-b:Missing CVD Classification for Clean Vehicle Attribute
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.
Engine Classification
Remove non-XRechnung UBL extensions per BR-DE-CVD-06-b
Confidence: 80% · Applied automatically in pipeline
What is BR-DE-CVD-06-b?
BR-DE-CVD-06-b is a fatal validation rule defined in the XRechnung (Germany) specification (DEU national rules). It validates the ext:UBLExtension element in the UBL invoice XML.
When this rule fires, the invoice is non-compliant and will be rejected by Peppol access points and national validation services. The sending system receives a rejection response and the invoice does not reach the buyer.
Target path: //ext:UBLExtensions/ext:UBLExtension[not(contains(ext:ExtensionURI,'xrechnung'))]
Why This Error Matters
The Clean Vehicle Directive (CVD) requires consistent data when reporting clean vehicle purchases. The CVD classification must be present whenever the cva attribute is used. Missing this causes validation failures for German XRechnung CVD invoices.
BR-DE-CVD-06-b is a hard failure. Invoices that trigger this rule are rejected at the access point and never reach the recipient. In Peppol networks, this means your sending system receives an MLR (Message Level Response) with a rejection status. The invoice must be corrected and re-sent, adding delay to your payment cycle.
Invoice Navigator can automatically correct this error in your pipeline. The fix is applied with full audit evidence, so your compliance trail remains intact.
Validator Behavior
- ·Causes invoice rejection
- ·Rejected by XRechnung endpoints
- ·Error returned: BR-DE-CVD-06-b
- ·Specification: XRechnung (Germany)
How to Fix It
Before / After
<Invoice> <!-- Issue: When Item attribute name (BT-160) has value "cva", there mus --> </Invoice>
<Invoice> <!-- Issue resolved per XRechnung (Germany) --> </Invoice>
Technical Reference
//ext:UBLExtensions/ext:UBLExtension[not(contains(ext:ExtensionURI,'xrechnung'))]Code Example
<cac:CommodityClassification>
<cbc:ItemClassificationCode listID="CVD">M1</cbc:ItemClassificationCode>
</cac:CommodityClassification>Common Causes
- ·cva AdditionalItemProperty added without corresponding CVD classification
- ·CVD classification element missing from invoice line
- ·Wrong listID used on ItemClassificationCode (not CVD)
- ·Vehicle category code placed in wrong XML element
Seeing this in production? The API handles BR-DE-CVD-06-b automatically. See the fix response →
Frequently Asked Questions
This error occurs when an invoice line has a clean vehicle attribute (cva) in AdditionalItemProperty but is missing the required CVD classification in CommodityClassification.
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.
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.
Yes, if the cva value contains the vehicle category code, it can be used to automatically add the missing CVD classification.
Related Errors
Last updated: 27 February 2026
Handle BR-DE-CVD-06-b Automatically in Your Pipeline
The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.