SchemaGuard by Ironbark Digital · EN 16931 / Peppol / XRechnung Reference
← All 294 EN 16931 / Peppol Rules & Live Validator
FATAL Official EN 16931 / Peppol / CIUS Rule BT/BG Fields: BT-157

BR-64 — E-Invoice Validation Rule & Fix

Fixture ID: standardItemNoScheme · XPath: /ubl:Invoice/cac:InvoiceLine[1]/cac:Item/cac:StandardItemIdentification/cbc:ID/@schemeID

1. Why This Rule Triggers (Diagnostic Message)

Line 1 carries an item standard identifier (BT-157) of "04012345678901" with no scheme identifier (BT-157-1). A standard identifier is only "standard" relative to a registry: the same digits can be a GTIN, a national article number or a manufacturer's own code, and the receiver has no way to look the item up — or to detect that it has looked up the wrong one — without being told which registry to ask. EN 16931 therefore makes the scheme mandatory whenever the identifier is present, and the UBL binding asserts the @schemeID attribute directly.

2. How to Fix BR-64

Set line.standardItemId.schemeId to the ISO 6523 ICD code of the registry — "0160" for a GTIN, "0088" for a GLN-based article number. Use line.sellerItemId (BT-155) or line.buyerItemId (BT-156) instead if the code is your own rather than a registered one.

3. Valid Code / Payload Example

"standardItemId": { "schemeId": "0160", "value": "04012345678901" }
Test & Validate XML / JSON in Live SchemaGuard Validator →