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-160, BT-161

BR-54 — E-Invoice Validation Rule & Fix

Fixture ID: itemAttributeEmpty · XPath: /ubl:Invoice/cac:InvoiceLine[1]/cac:Item/cac:AdditionalItemProperty[1]/cbc:Name

1. Why This Rule Triggers (Diagnostic Message)

Item attribute 1 on line 1 has neither a name (BT-160) nor a value (BT-161). BG-32 is a name/value pair and EN 16931 requires both halves, because half a pair carries no information at all: a value with no name is a number nobody can interpret, and a name with no value is a question. These attributes are what a buyer's catalogue matching reads to confirm that the thing invoiced is the thing ordered — colour, capacity, licence term — so an unmatched half silently breaks that check rather than failing it visibly.

2. How to Fix BR-54

Give every entry in line.itemAttributes both a name and a value, or drop the entry. Put unstructured detail in line.longDescription (BT-154) instead.

3. Valid Code / Payload Example

"itemAttributes": [{ "name": "Farbe", "value": "anthrazit" }]
Test & Validate XML / JSON in Live SchemaGuard Validator →