The parent line identifier designates no line of the invoice
In the extended profile, every parent line identifier (EXT-FR-FE-162) must match the identifier (BT-126) of another line of the same invoice.
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.
ciiNum line : , ParentID : - [BR-FREXT-11]-Each "Identifier of parent line" (EXT-FR-FE-162) must refer to an existing "Invoice line Identifier" (BT-126) of another invoice line (BG-25).
ublNum Fact : , Num line : , ParentID : - [BR-FREXT-11]-Each "Identifier of parent line" (EXT-FR-FE-162) must refer to an existing "Invoice line Identifier" (BT-126) of another invoice line (BG-25).
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.
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.
Why this error happens
An orphan sub-line attaches to nothing: the recipient can neither group it nor check it against its total. The typical case is a parent line deleted or renumbered after the sub-lines were generated. 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
Point the sub-line to a line that exists, or remove the reference. Factlint does not rebuild an invoice's hierarchy.
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
<ram:LineID>3</ram:LineID> … <ram:ParentLineID>7</ram:ParentLineID> <!-- aucune ligne 7 -->
<ram:LineID>3</ram:LineID> … <ram:ParentLineID>1</ram:ParentLineID>