The SIRET does not start with the SIREN or does not have 14 digits

When a party carries both a SIRET (identifier in scheme 0009) and a SIREN (scheme 0002), the SIRET must have 14 digits and start with the 9 digits of the SIREN — seller, buyer, payee, deliver-to and extension parties.

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-09/BT-29 : Le SIRET doit contenir 14 chiffres et commencer par le SIREN. SIRET : " ", SIREN : " ".

cii
BR-FR-09/BT-46 : Le SIRET doit contenir 14 chiffres et commencer par le SIREN. SIRET : " ", SIREN : " ".

cii
BR-FR-09/BT-60 : Le SIRET doit contenir 14 chiffres et commencer par le SIREN. SIRET : " ", SIREN : " ".

cii
BR-FR-09/EXT-FR-FE-06 : Le SIRET doit contenir 14 chiffres et commencer par le SIREN. SIRET : " ", SIREN : " ".

cii
BR-FR-09/EXT-FR-FE-46 : Le SIRET doit contenir 14 chiffres et commencer par le SIREN. SIRET : " ", SIREN : " ".

cii
BR-FR-09/EXT-FR-FE-69 : Le SIRET doit contenir 14 chiffres et commencer par le SIREN. SIRET : " ", SIREN : " ".

cii
BR-FR-09/EXT-FR-FE-92 : Le SIRET doit contenir 14 chiffres et commencer par le SIREN. SIRET : " ", SIREN : " ".

cii
BR-FR-09/EXT-FR-FE-115 : Le SIRET doit contenir 14 chiffres et commencer par le SIREN. SIRET : " ", SIREN : " ".

cii
BR-FR-09/BT-71 : Le SIRET doit contenir 14 chiffres et commencer par le SIREN. SIRET : " ", SIREN : " ".

cii
BR-FR-09/EXT-FR-FE-146 : Le SIRET doit contenir 14 chiffres et commencer par le SIREN. SIRET : " ", SIREN : " ".

ubl
[BR-FR-09/BT-29] : Le SIRET doit contenir 14 chiffres et commencer par le SIREN. SIRET : " ", SIREN : " ".

ubl
[BR-FR-09/BT-46] : Le SIRET doit contenir 14 chiffres et commencer par le SIREN. SIRET : " ", SIREN : " ".

ubl
[BR-FR-09/BT-60] : Le SIRET doit contenir 14 chiffres et commencer par le SIREN. SIRET : " ", SIREN : " ".

ubl
[BR-FR-09/EXT-FR-FE-06] : Le SIRET doit contenir 14 chiffres et commencer par le SIREN. SIRET : " ", SIREN : " ".

ubl
[BR-FR-09/EXT-FR-FE-46] : Le SIRET doit contenir 14 chiffres et commencer par le SIREN. SIRET : " ", SIREN : " ".

ubl
[BR-FR-09/EXT-FR-FE-69] : Le SIRET doit contenir 14 chiffres et commencer par le SIREN. SIRET : " ", SIREN : " ".

ubl
[BR-FR-09/EXT-FR-FE-92] : Le SIRET doit contenir 14 chiffres et commencer par le SIREN. SIRET : " ", SIREN : " ".

ubl
[BR-FR-09/EXT-FR-FE-115] : Le SIRET doit contenir 14 chiffres et commencer par le SIREN. SIRET : " ", SIREN : " ".

ubl
[BR-FR-09/BT-71] : Le SIRET doit contenir 14 chiffres et commencer par le SIREN. SIRET : " ", SIREN : " ".

ubl
[BR-FR-09/EXT-FR-FE-146] : Le SIRET doit contenir 14 chiffres et commencer par le SIREN. SIRET : " ", SIREN : " ".

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-09 The SIRET does not start with the SIREN or does not have 14 digitsBR-FR-09 French BR-FR-CTC rulesBR-FR-09 BT-29BR-FR-09/BT-29 : Le SIRET doit contenir 14 chiffres et commencer par le SIREN. SIRET : " ", SIREN : " ".BR-FR-09 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 SIRET is the SIREN followed by the five digits of the establishment: two identifiers that do not nest designate two companies, and the platform cannot route to one while invoicing the other. The typical case is a SIREN copied from the VAT number, or the SIRET of a former establishment. 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

Check both identifiers in your master data and fix the wrong one. Factlint does not derive one from the other: getting the establishment wrong 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:GlobalID schemeID="0009">98765432100012</ram:GlobalID> … <ram:ID schemeID="0002">123456789</ram:ID>

AFTER (compliant)

<ram:GlobalID schemeID="0009">12345678900012</ram:GlobalID> … <ram:ID schemeID="0002">123456789</ram:ID>