Several BAR notes declare different processing scopes

When several notes carry the BAR subject code (BT-21), they must all carry the same value: an invoice has a single processing scope — B2B, B2BINT, B2C, OUTOFSCOPE or ARCHIVEONLY.

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.

BR-FR-31/BT-21 : Lorsque plusieurs notes ont le code sujet « BAR » (BT-21), Il ne peut y avoir qu'une seule valeur associée (BT-22, contenu de la note) parmi l’une des suivantes : B2B, B2BINT, B2C, OUTOFSCOPE, ARCHIVEONLY. Valeur fournie : " " , Nombre de valeurs présentes (pas plus de 1) : "/>". Veuillez corriger la valeur ou retirer le code sujet « BAR ».

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-31 Several BAR notes declare different processing scopesBR-FR-31 French BR-FR-CTC rulesBR-FR-31 BT-21BR-FR-31/BT-21 : Lorsque plusieurs notes ont le code sujet « BAR » (BT-21), Il ne peut y avoir qu'une seule valeur associée (BT-22, contenu de la note) parmi l’une des suivantes : B2B, B2BINT, B2C, OUTOFSCOPE, ARCHIVEONLY. Valeur fournie : " " , Nombre de valeurs présentes (pas plus de 1) : "/>". Veuillez corriger la valeur ou retirer le code sujet « BAR ».BR-FR-31 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

Two contradictory scopes — B2B and OUTOFSCOPE — would both transmit and not transmit the same invoice. The platform does not decide; it refuses. The case comes from a template that sets a default scope and a module that adds another. 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

Keep a single BAR note, with the transaction's actual scope. Factlint does not qualify a transaction 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:IncludedNote><ram:Content>B2B</ram:Content><ram:SubjectCode>BAR</ram:SubjectCode></ram:IncludedNote><ram:IncludedNote><ram:Content>OUTOFSCOPE</ram:Content><ram:SubjectCode>BAR</ram:SubjectCode></ram:IncludedNote>

AFTER (compliant)

<ram:IncludedNote><ram:Content>B2B</ram:Content><ram:SubjectCode>BAR</ram:SubjectCode></ram:IncludedNote>