The item attribute code is not in the extended UNTDID 6313 list

In the extended profile, an item attribute code (EXT-FR-FE-159) must come from the UNTDID 6313 list completed by the Factur-X extension.

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.

[BR-FREXT-04]-only values from the code list UNTDID 6313+Factur-X-Extension should be used on Item attribute code

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-FREXT-04 The item attribute code is not in the extended UNTDID 6313 listBR-FREXT-04 FNFE Schematron packageBR-FREXT-04 EXT-FR-FE-159[BR-FREXT-04]-only values from the code list UNTDID 6313+Factur-X-Extension should be used on Item attribute codeBR-FREXT-04 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

A code exists so that two systems qualify a characteristic the same way without talking to each other; an invented code is only a disguised label, and the recipient can neither understand it nor reject it cleanly. It only applies to documents that declare the EXTENDED-CTC-FR profile — the profile sheet replaces the CEN package and adds its own rules for hierarchical lines.

How to fix it

Pick the matching code from the list, or use an attribute name (BT-160) if no code fits. Factlint does not qualify a product characteristic on your behalf.

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)

<cbc:NameCode>COULEUR</cbc:NameCode>

AFTER (compliant)

<cbc:Name>Couleur</cbc:Name>