The subtype of an invoice line is not in the list

In the extended profile, a line's subtype (EXT-FR-FE-163) must come from the line status code list — DETAIL for an invoiced line, GROUP for a line that groups sub-lines, among others.

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
Code : ' ' - [BR-FREXT-05]-The code for the subtype of the invoice line item (EXT-FR-FE-163) must be used from the Line Status Reason code list.

ubl
Num Fact : , Code : - [BR-FREXT-05]-The code for the subtype of the invoice line item (EXT-FR-FE-163) must be used from the Line Status Reason code list.

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-05 The subtype of an invoice line is not in the listBR-FREXT-05 FNFE Schematron packageBR-FREXT-05 EXT-FR-FE-163Code : ' ' - [BR-FREXT-05]-The code for the subtype of the invoice line item (EXT-FR-FE-163) must be used from the Line Status Reason code list.BR-FREXT-05 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

The subtype decides whether a line counts in the totals or only structures the invoice: an out-of-list value lets the recipient add up what it should not, or ignore what is owed. 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

Use the list code that describes the line's role. Factlint does not decide whether a line is invoiced or structural.

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:LineStatusReasonCode>SUBTOTAL</ram:LineStatusReasonCode>

AFTER (compliant)

<ram:LineStatusReasonCode>GROUP</ram:LineStatusReasonCode>