How do I fix BR-CL-13?

Invoice Navigator automatically fixes this Invoice compliance issue by updating the relevant XML elements (BR-CL-13). You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.

Is BR-CL-13 a critical error?

Yes, BR-CL-13 is a critical error that will cause invoice rejection. It must be fixed before submission.

Can BR-CL-13 be automatically fixed?

Many instances of BR-CL-13 can be automatically corrected using Invoice Navigator's compliance engine. The fix is applied in your pipeline with full audit evidence.

Which accounting software causes BR-CL-13?

BR-CL-13 is commonly seen in exports from All invoicing software. These packages sometimes generate invoices that need adjustment.

errorEN 16931

`BR-CL-13`:Invalid product classification scheme

A line item's classification code uses an invalid scheme identifier. The classification listID must be from the UNTDID 7143 code list. Common valid schemes include STI for UNSPSC, EN for eCl@ss, and CPV for EU public procurement.

Severity

Fatal

Rule set

EN 16931

Country

All EU

Fix type

AUTO-FIX

Confidence

85%

Engine Classification

Maps common invalid classification scheme names to valid UNTDID 7143 codes

Confidence: 85% · Applied automatically in pipeline

What is BR-CL-13?

BR-CL-13 is a fatal validation rule defined in the EN 16931 specification. It validates the @listID element under CommodityClassification > ItemClassificationCode 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: cac:InvoiceLine/cac:Item/cac:CommodityClassification/cbc:ItemClassificationCode/@listID

Get API Access Test This Error ↓

Why This Error Matters

Invoice will be rejected. Item classifications require valid UNTDID 7143 scheme codes for proper product categorization.

BR-CL-13 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
·Error returned: BR-CL-13
·Specification: EN 16931

How to Fix It

Check the classification system

Which product classification system are you using? UNSPSC, eCl@ss, or CPV?

Set the correct list ID

Use STI for UNSPSC, EN for eCl@ss, or CPV for EU public procurement codes.

Verify the code

Make sure the classification code itself is valid for the chosen scheme.

Before / After

Failing XML

<Invoice>
  <!-- Issue: Item classification identifier identification scheme identif -->
</Invoice>

Corrected XML

<Invoice>
  <!-- Issue resolved per EN 16931 -->
</Invoice>

Technical Reference

XPathcac:InvoiceLine/cac:Item/cac:CommodityClassification/cbc:ItemClassificationCode/@listID

SpecEN 16931

Operationlookup

StrategyMaps common invalid classification scheme names to valid UNTDID 7143 codes

Common Causes

·ListID attribute set to non-standard value
·ERP uses internal classification scheme names
·ListID left empty or missing

Seeing this in production? The API handles BR-CL-13 automatically. See the fix response →

Commonly Seen In

All invoicing software

Related Errors

BR-CL-21

Invalid product identifier scheme

Last updated: 27 February 2026

Share this guide:

Handle BR-CL-13 Automatically in Your Pipeline

The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.

Get API Access View API Documentation

BR-CL-13:Invalid product classification scheme