# BR-54: Item attribute name and value (BT-160/BT-161)

Source: https://veriport.io/einvoice-rules/br-54 (published 2026-11-17)

Every item attribute (BG-32: `cac:AdditionalItemProperty` in UBL, `ram:ApplicableProductCharacteristic` in CII) must have both a name (BT-160) and a value (BT-161). Below: the message, the cause and the fix, and an invoice our validator checked, failing and fixed.

- **Specification:** [EN 16931 business rules](/einvoice-rules/en16931), CEN EN 16931 validation artefacts 1.3.16
- **Severity:** error
- **Business terms:** BT-160, BT-161, BG-32
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-54 is a rule of the EN 16931 business rules (CEN validation artefacts 1.3.16) for UBL and CII. It is an error (fatal): a validator rejects the invoice.

```text
[BR-54]-Each Item attribute (BG-32) shall contain an Item attribute name (BT-160) and an Item attribute value (BT-161).
```

## What it checks

Every item attribute (BG-32: `cac:AdditionalItemProperty` in UBL, `ram:ApplicableProductCharacteristic` in CII) must have both a name (BT-160) and a value (BT-161).

## Why invoices fail it

Optional product properties (colour, size) are written with an empty value when the master record has none.

## How to fix it

Write only the attributes that have a value; omit the others.

## A failing invoice and its fix, checked

We start from our sample invoice (two lines at 19 %, Berlin to Stuttgart), written by our own generator as EN 16931 in CII. The change below (`-` the failing version, `+` the fixed one) makes the rule fail. Both versions went through our validator on 2026-11-17 (the XML schema and the official rule files, as `POST /einvoice/validate` runs them): the fixed one is valid, the failing one reports BR-54 and 1 other rule, as a real file with this mistake would.

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-54** | error | `/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:IncludedSupplyChainTradeLineItem[1]/ram:SpecifiedTradeProduct/ram:ApplicableProductCharacteristic` | Each Item attribute (BG-32) shall contain an Item attribute name (BT-160) and an Item attribute value (BT-161). |
| [CII-SR-072](/einvoice-rules/cii-sr-072) | error | `/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:IncludedSupplyChainTradeLineItem[1]/ram:SpecifiedTradeProduct/ram:ApplicableProductCharacteristic` | Value should exist maximum once. |

```diff
  …
          <ram:ApplicableProductCharacteristic>
            <ram:Description>Umfang</ram:Description>
+           <ram:Value>12 Unterseiten</ram:Value>
          </ram:ApplicableProductCharacteristic>
        </ram:SpecifiedTradeProduct>
  …
```

## The rule as published

Where the rule applies (`context`) and what must hold (`test`), unmodified from CEN EN 16931 validation artefacts 1.3.16. An `assert` fails when its test is false.

Text and test: © CEN/TC 434, EN 16931 validation artefacts, EUPL 1.2. Quoted unmodified; the explanations on this page are Veriport’s.

```xpath
context: //cac:AdditionalItemProperty
test:    exists(cbc:Name) and exists(cbc:Value)
```

```xpath
context: //ram:ApplicableProductCharacteristic
test:    (ram:Description) and (ram:Value)
```

## Check your own invoice

Drop your XRechnung, ZUGFeRD or Peppol file into a free validator ([Peppol BIS](/tools/peppol-validator), [XRechnung](/tools/xrechnung-pruefen), [Factur-X](/tools/valider-factur-x)): each runs the same rule files and links every finding to its rule page. From your own code, `POST /einvoice/validate` ([reference](/docs/einvoice)) returns the same check as JSON, each finding with an `explanation` field pointing here (5 calls a check, anonymous within the daily allowance).

## Read next

- [BR-52: Supporting document reference (BT-122) missing](https://veriport.io/einvoice-rules/br-52)
- [BR-53: VAT total in accounting currency (BT-111)](https://veriport.io/einvoice-rules/br-53)
- [BR-55: Preceding invoice reference (BT-25) missing](https://veriport.io/einvoice-rules/br-55)
- [BR-56: Tax representative VAT identifier (BT-63)](https://veriport.io/einvoice-rules/br-56)
- [All EN 16931 business rules](https://veriport.io/einvoice-rules/en16931)
- [All e-invoice rules, search](https://veriport.io/einvoice-rules)
- [Check an e-invoice free (XRechnung prüfen)](https://veriport.io/tools/xrechnung-pruefen)
- [Create a valid e-invoice free (German form)](https://veriport.io/tools/e-rechnung-erstellen)

## Sources

- EN 16931 validation artefacts 1.3.16 (UBL and CII schematron, the business rules BR-*) — https://github.com/ConnectingEurope/eInvoicing-EN16931/releases/tag/validation-1.3.16 (2026-10-28)
- EN 16931 validation artefacts: licence, European Union Public Licence (EUPL) v1.2 (LICENSE.txt, the README « License » section and the release notes of validation-1.3.16) — https://github.com/ConnectingEurope/eInvoicing-EN16931/blob/master/LICENSE.txt (2026-11-17)
