An item attribute carries both a value and a quantity, or neither

An item attribute (BG-32) carries either a text value (BT-161) or a quantity with its unit of measure (EXT-FR-FE-160 and EXT-FR-FE-161) — one of the two, never both, never neither.

Only the issuer holds this value: Factlint reports it and never fabricates it. Test your invoice to find out whether it is affected.

The message your validator prints

Copied verbatim from the sealed artefact: this is the exact sentence the check prints when this rule fails.

cii
[BR-FR-28] : La valeur d’attribut (ram:Value) ou la valeur (ram:ValueMeasure 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.

ubl
[BR-FR-28] : 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.

Quoted from schematron-fnfe 1.4.0.03, licensed under Apache-2.0.

Common searches around this code

These phrases mirror what an integrator searches for: code, syntax, rule, business field and correction.

BR-FR-28 An item attribute carries both a value and a quantity, or neitherBR-FR-28 French BR-FR-CTC rulesBR-FR-28 BT-161[BR-FR-28] : La valeur d’attribut (ram:Value) ou la valeur (ram:ValueMeasure 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.BR-FR-28 correction

Test your file with this error in mind

Upload the invoice involved: the report will say whether this code appears, where it appears in the document, and whether Factlint can only report it or also fix it.

To automate this check in an ERP flow, call the validation API and link every returned code to its public page.

Open the validator See the API

Why this error happens

Two values for the same attribute cannot be told apart: do “1.5” as text and “1500 g” as a quantity mean the same thing? An automated reader cannot decide, so the French extension imposes a single form per attribute. The rule comes from the FNFE Schematron package, not from the European standard: an invoice perfectly compliant with EN 16931 triggers it as soon as it is judged against the French base.

How to fix it

Keep the form that describes the attribute — text or measured quantity — and remove the other. Factlint does not choose which one is right.

Severity returned by the rule set

Blocking since 1 September 2026: the current base, `fr-2026-09`, seals the FNFE 1.4.0.03 artefact in fatal mode, and it is the one the pinned engine applies by default. An invoice issued in August 2026 is judged against `fr-2026-08`, where the same rule comes out as a warning — which already rules out a “compliant” verdict. The API returns the severity of the rule set pinned for the judged invoice.

XML correction example

BEFORE (invalid)

<ram:ApplicableProductCharacteristic><ram:Description>Poids</ram:Description><ram:Value>1,5 kg</ram:Value><ram:ValueMeasure unitCode="KGM">1.5</ram:ValueMeasure></ram:ApplicableProductCharacteristic>

AFTER (compliant)

<ram:ApplicableProductCharacteristic><ram:Description>Poids</ram:Description><ram:ValueMeasure unitCode="KGM">1.5</ram:ValueMeasure></ram:ApplicableProductCharacteristic>