BR-60:Item classification must have valid scheme
Commodity classification must have valid scheme identifier.
Engine Classification
Business data required · Explicit input workflow · No assumptions made
Required input: Classification Scheme, Classification Code
What is BR-60?
BR-60 is a fatal validation rule defined in the en16931 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: XPath: //cac:CommodityClassification/cbc:ItemClassificationCode/@listID
Why This Error Matters
Classification schemes enable automated categorization.
BR-60 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.
Validator Behavior
- ·Causes invoice rejection
- ·Fails EN 16931 business rule validation
- ·Error returned: BR-60
- ·Specification: en16931
How to Fix It
Find classification
Locate CommodityClassification element
Add scheme
Use listID or schemeID attribute
XML Example
Generic example based on the rule's target XPath. Your actual XML structure may differ.
<!-- Triggers validation error --> <@listID></@listID>
<!-- Corrected --> <@listID>VALID_VALUE</@listID>
Technical Reference
XPath: //cac:CommodityClassification/cbc:ItemClassificationCode/@listIDCommon Causes
- ·Missing listID attribute
- ·Invalid scheme code
Seeing this in production? The API handles BR-60 automatically. See the fix response →
Frequently Asked Questions
Commodity classification must have valid scheme identifier.
Add valid schemeID like TST, STI, CPV, or UNSPSC. Invoice Navigator detects this error and prompts for the required business data before applying a safe fix.
Yes, BR-60 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.
BR-60 requires specific business data to resolve. Invoice Navigator detects the error and guides you through providing the needed information, then applies the fix with full audit documentation.
Related Content
Last updated: 3 March 2026
Resolve BR-60 with Guided Input
The compliance engine detects this error and prompts for the required business data before applying a safe, auditable fix.