The seller's electronic address does not carry its SIREN on a self-billed invoice

On a transaction declared B2B whose document type is a self-billed invoice (389, 501, 500, 471, 473, 261, 502), the seller's electronic address (BT-34) must start with its SIREN (BT-30) and carry scheme 0225.

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-22/BT-34 : Si le traitement est BAR/B2B et que le type de document (BT-3) est en autofacture (389, 501, 500, 471, 473, 261, 502), alors le BT-34 (EndpointID du vendeur) doit commencer par le SIREN (BT-30) et le BT-34-1 (schemeID) doit être égal à "0225". Valeurs actuelles : EndpointID=" ", schemeID=" ", SIREN=" ".

ubl
[BR-FR-22/BT-34] : Si le traitement est BAR/B2B et que le type de document (cbc:InvoiceTypeCode) est en autofacture (389, 501, 500, 471, 473, 261, 502), alors le BT-34 (cbc:EndpointID du vendeur) doit commencer par le SIREN (cbc:ID[@schemeID='0002']) et le schemeID doit être égal à "0225". Valeurs actuelles : EndpointID=" ", schemeID=" ", 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-22 The seller's electronic address does not carry its SIREN on a self-billed invoiceBR-FR-22 French BR-FR-CTC rulesBR-FR-22 BT-34BR-FR-22/BT-34 : Si le traitement est BAR/B2B et que le type de document (BT-3) est en autofacture (389, 501, 500, 471, 473, 261, 502), alors le BT-34 (EndpointID du vendeur) doit commencer par le SIREN (BT-30) et le BT-34-1 (schemeID) doit être égal à "0225". Valeurs actuelles : EndpointID=" ", schemeID=" ", SIREN=" ".BR-FR-22 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

In self-billing the buyer issues and the seller receives: the party to route to is therefore the seller, and it is its 0225 address the directory must recognise. The rule mirrors BR-FR-21, applied to the reverse flow. 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 BT-34 with the seller's reception address as the directory publishes it, in scheme 0225. Factlint does not query the directory and does not invent a routing address.

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:SellerTradeParty>…<ram:URIID schemeID="0088">3012345678901</ram:URIID>…</ram:SellerTradeParty>

AFTER (compliant)

<ram:SellerTradeParty>…<ram:URIID schemeID="0225">123456789</ram:URIID>…</ram:SellerTradeParty>