The buyer's SIREN is missing on a B2B invoice
When a BAR note declares the transaction as B2B, the buyer's legal identifier (BT-47, scheme 0002) is mandatory and 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.
ciiBR-FR-11/BT-47 : Si une note contient le code sujet BAR avec la valeur 'B2B', alors le SIREN de l’acheteur (BT-47, ram:ID) est obligatoire et doit être composé exactement de 9 chiffres. Valeur actuelle : " ". Veuillez renseigner un identifiant SIREN valide.
ubl[BR-FR-11/BT-47] : Si une note contient le code sujet BAR avec la valeur 'B2B', alors le SIREN de l’acheteur (cbc:ID[@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.
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
Between French businesses, the buyer's SIREN is what lets the platform find its reception address: without it, the invoice has no recipient in the directory. The rule only fires on a flow declared B2B — out of scope or B2C, the buyer may have no SIREN at all. 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
Fill in your customer's SIREN — the first nine digits of its SIRET — in BT-47, scheme 0002. Factlint does not look it up in a directory: naming the wrong entity on an invoice is not a mistake to 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
<ram:BuyerTradeParty><ram:Name>Acheteur Synthetique</ram:Name> … </ram:BuyerTradeParty>
<ram:BuyerTradeParty><ram:Name>Acheteur Synthetique</ram:Name><ram:SpecifiedLegalOrganization><ram:ID schemeID="0002">987654321</ram:ID></ram:SpecifiedLegalOrganization> … </ram:BuyerTradeParty>