Skip to content

Fatal

BR-FR-28-VALUE: Use a plain attribute value or a quantity with a unit

In short

Fatal: fails the selected checks.

BR-FR-28-VALUE means your line's item attribute does not use an allowed value form. Use cbc:Value without cbc:ValueQuantity, or use cbc:ValueQuantity with a non-empty unitCode and no cbc:Value. Choose one form and remove the other.

On this page

What it means

For each cac:AdditionalItemProperty on a UBL invoice or credit note line, cbc:Value (BT-161) must exist without cbc:ValueQuantity, or cbc:Value must be absent and at least one cbc:ValueQuantity must have a non-empty unitCode attribute. The test checks element presence, not value content. It does not trim or validate unitCode, so whitespace alone is not excluded by this expression.

Why it matters

The attribute needs one form of value, either a plain value or a quantity associated with a unit.

How to fix it

Find the affected line's cac:AdditionalItemProperty. For a descriptive attribute, enter its value in cbc:Value and remove all cbc:ValueQuantity elements. For a measured attribute, enter the quantity in cbc:ValueQuantity, supply the correct unit code in unitCode and remove all cbc:Value elements. Recheck your file.

Once the file is corrected, check it again for free: Check an e-invoice

The rule as published

La valeur d’attribut (cbc:Value) ou la valeur (cbc:ValueQuantity avec unité de mesure) doivent être présents, mais pas les deux Valeur actuelle Value : " … ", Valeur actuelle Value Quantity : " … ". unité de mesure : " … " Veuillez fournir une valeur d’attribut valide ou utiliser une Valeur avec unité de mesure.

Where this rule applies

Rule set Version
France CTC (UBL invoice) 1.4.0-04
France CTC (UBL credit note) 1.4.0-04
France CTC (CII) 1.4.0-04
Rule text from phive-rules 4.6.4.

Check your file

Drop your e-invoice to see whether BR-FR-28-VALUE still fails, and which other rules do.

Updated 6 November 2026