The seller's SIREN is missing or malformed

The seller's legal identifier must be a SIREN of exactly nine digits.

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-10/BT-30 : Le SIREN du vendeur (ram:ID) est obligatoire et doit être composé exactement de 9 chiffres. Valeur actuelle : " ". Veuillez renseigner un identifiant SIREN valide.

ubl
[BR-FR-10/BT-30] : Le SIREN du vendeur (CompanyID[@schemeID='0002']) est obligatoire et doit être composé exactement de 9 chiffres. Valeur actuelle : " ". Veuillez renseigner un identifiant SIREN valide.

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-10 The seller's SIREN is missing or malformedBR-FR-10 French BR-FR-CTC rulesBR-FR-10 BT-30BR-FR-10/BT-30 : Le SIREN du vendeur (ram:ID) est obligatoire et doit être composé exactement de 9 chiffres. Valeur actuelle : " ". Veuillez renseigner un identifiant SIREN valide.BR-FR-10 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

This is the identifier that ties the invoice to a company registered in France. Many generators put the SIRET (fourteen digits, one establishment) or the intra-EU VAT number there: the three are distinct, and only the SIREN is expected here.

How to fix it

Fill in the SIREN — the first nine digits of the SIRET. Factlint does not infer it: naming the wrong legal entity on an invoice is not a mistake a tool should make 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)

<ram:ID>12345678900012</ram:ID>

AFTER (compliant)

<ram:ID schemeID="0002">123456789</ram:ID>