EN 16931 rules › BR-54
BR-54 — Each Item attribute (BG-32) shall contain an Item attribute name (BT-160) and an Item attribute value (BT-161)
| Rule id | BR-54 |
|---|---|
| Rule set | EN 16931 itself, not a national or network addition |
| Severity | fatal in CII and UBL — a validator enforcing this rule set rejects the invoice |
| Applies to | the CII and UBL syntaxes |
| Checked by | the validator on this site and invoicekit.go v0.2.11, the library behind it |
The rule as published
Each Item attribute (BG-32) shall contain an Item attribute name (BT-160) and an Item attribute value (BT-161).
fatal in CII and UBL — a validator enforcing this rule set rejects the invoice.
What runs for it
Straight from the artefacts the engine embeds: the node the assertion selects and the test it applies there. A failing invoice is reported with the message above.
| Syntax | Severity | Artefact phase | Applied to | Fails when |
|---|---|---|---|---|
| CII | fatal | EN16931-model-phase | //ram:ApplicableProductCharacteristic | (ram:Description) and (ram:Value) |
| UBL | fatal | EN16931model_phase | //cac:AdditionalItemProperty | exists(cbc:Name) and exists(cbc:Value) |
Data elements it names
- BG-32 Item attribute (cited by 1 rule)
- BT-160 Item attribute name (cited by 1 rule)
- BT-161 Item attribute value (cited by 1 rule)
See also
- Every EN 16931 rule id — the same list as a filterable table, with the assertions as CSV and JSON.
- What XRechnung and Peppol BIS add — rule sets that run these ids plus their own.
- The data elements — every BT and BG with the rules that name it.