errorEN 16931

BR-CL-10:Invalid party identifier scheme

The scheme identifier for a seller or buyer party identification number is not a valid code from the ISO 6523 ICD list. Every party identifier must specify which numbering system it belongs to, using a standard code like 0088 for GLN, 0007 for Swedish org number, 0106 for Dutch KvK number, etc.

Severity
Fatal
Rule set
EN 16931
Country
All EU
Fix type
AUTO-FIX
Confidence
85%
Category
identifier

Engine Classification

Infers the correct ISO 6523 ICD scheme code from the identifier value pattern and party country

Confidence: 85% · Applied automatically in pipeline

What is BR-CL-10?

BR-CL-10 is a fatal validation rule defined in the EN 16931 specification. It validates the @schemeID element under ID 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:PartyIdentification/cbc:ID/@schemeID

Why This Error Matters

Invoice rejected. Party identifiers must use recognized scheme codes for proper routing and identification.

BR-CL-10 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-10
  • ·Specification: EN 16931

How to Fix It

1.

Identify the identifier type

What kind of number is it? GLN (13 digits), VAT number (country prefix + digits), KvK number (8 digits), etc.

2.

Find the correct scheme code

Look up the ISO 6523 ICD code for your identifier type: 0088 for GLN, 0007 for Swedish org, 0106 for Dutch KvK, 0208 for Belgian enterprise, etc.

3.

Set the schemeID

Add or correct the schemeID attribute on the PartyIdentification ID element.

Before / After

Failing XML
<Invoice>
  <!-- Issue: Any identifier identification scheme identifier MUST be code -->
</Invoice>
Corrected XML
<Invoice>
  <!-- Issue resolved per EN 16931 -->
</Invoice>

Technical Reference

XPathcac:PartyIdentification/cbc:ID/@schemeID
SpecEN 16931
Operationderive
StrategyInfers the correct ISO 6523 ICD scheme code from the identifier value pattern and party country

Common Causes

  • ·SchemeID attribute missing from PartyIdentification
  • ·Invalid or non-standard scheme code used (e.g. 'GLN' instead of '0088')
  • ·ERP system does not populate the schemeID attribute

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

Commonly Seen In

All invoicing software

Frequently Asked Questions

AllowanceChargeReasonCode must be from UNCL5189.

Use valid UNCL5189 code for allowances. You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.

Yes, BR-CL-10 is a critical error that will cause invoice rejection. It must be fixed before submission to ensure your invoice is accepted by the recipient's system.

Many instances of BR-CL-10 can be automatically corrected using Invoice Navigator's Fixer tool. Upload your invoice and the tool will identify and fix common issues, including invalid allowance reason code.

See Also

Related Errors

Last updated: 27 February 2026

Share this guide:

Handle BR-CL-10 Automatically in Your Pipeline

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