errorEN 16931

BR-64:Item standard identifier needs scheme

If item has standard identifier, scheme must be specified.

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

Engine Classification

Add default item standard identifier scheme ID (GTIN/EAN)

Confidence: 85% · Applied automatically in pipeline

What is BR-64?

BR-64 is a fatal validation rule defined in the EN 16931 specification. It validates the @schemeID element under StandardItemIdentification > 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:InvoiceLine/cac:Item/cac:StandardItemIdentification/cbc:ID/@schemeID

Why This Error Matters

Invoice rejected. The scheme tells receivers how to look up the product in their systems.

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

How to Fix It

1.

Find standard ID

Locate StandardItemIdentification/ID

2.

Add scheme

Use schemeID like 0088 for EAN/GTIN

Before / After

Failing XML
<cac:ClassifiedTaxCategory>
  <!-- cbc:ID is missing -->
</cac:ClassifiedTaxCategory>
Corrected XML
<cac:ClassifiedTaxCategory>
  <cbc:ID>valid-value</cbc:ID>
</cac:ClassifiedTaxCategory>

Technical Reference

XPath//cac:InvoiceLine/cac:Item/cac:StandardItemIdentification/cbc:ID/@schemeID
SpecEN 16931
Operationset_default
StrategyAdd default item standard identifier scheme ID (GTIN/EAN)

Common Causes

  • ·Item standard identifier without scheme identifier
  • ·StandardItemIdentification/ID missing schemeID
  • ·Product code present but coding scheme not specified
  • ·Template missing schemeID on item identifier
  • ·GTIN/EAN exported without scheme attribute

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

Frequently Asked Questions

If item has standard identifier, scheme must be specified.

Add schemeID attribute (0088 for GTIN/EAN, 0160 for GTIN-13). You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.

Yes, BR-64 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-64 can be automatically corrected using Invoice Navigator's Fixer tool. Upload your invoice and the tool will identify and fix common issues, including item standard identifier needs scheme.

See Also

Related Errors

Last updated: 27 February 2026

Share this guide:

Handle BR-64 Automatically in Your Pipeline

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