A party identifier in scheme 0002 does not have nine digits
Every party identifier carried with scheme 0002 — legal identifier or plain identifier, seller, buyer or any other party — must be a SIREN of exactly nine digits; in CII, scheme 0231 follows the same rule.
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.
ciiBR-FR-32/LEGALID : Tout identifiant légal d'une Partie avec schemeID = '0002' DOIT être composé de 9 chiffres.
ciiBR-FR-32/ID : Tout identifiant d'une Partie avec schemeID = '0231' ou '0002' DOIT être composé de 9 chiffres.
ubl[BR-FR-32/LEGALID] : Tout identifiant légal d'une Partie avec schemeID = '0002' DOIT être composé de 9 chiffres.
ubl[BR-FR-32/ID] : Tout identifiant d'une Partie avec schemeID = '0002' DOIT être composé de 9 chiffres.
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
The scheme says what the value is: 0002 announces a SIREN. A fourteen-digit SIRET, an eleven-digit VAT number, a leading “FR” are the three common ways of putting something else behind the label — most often a system copying the wrong field from the master data. A value that does not match its scheme cannot be matched to any company. 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
Put the SIREN — the first nine digits of the SIRET, without prefix — behind scheme 0002, and the SIRET behind 0009 if you also want to transmit it. Factlint does not derive a legal identifier: naming the wrong entity on an invoice is not a mistake a tool should make for you.
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:ID schemeID="0002">FR12345678901</ram:ID>
<ram:ID schemeID="0002">123456789</ram:ID>