A private identifier contains characters that are not allowed

A party identifier in scheme 0224 — the private identifier of the seller (BT-29) or the buyer (BT-46) — only allows letters, digits and the symbols - _ . ; no spaces.

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-24/BT-29 : L'identifiant privé (ram:GlobalID) ne respecte pas le format autorisé. Valeur actuelle : " ". Seuls les caractères alphanumériques et les symboles "-", "_", "." sont autorisés.

cii
BR-FR-24/BT-46 : L'identifiant privé (ram:GlobalID) ne respecte pas le format autorisé. Valeur actuelle : " ". Seuls les caractères alphanumériques et les symboles "-", "_", "." sont autorisés.

ubl
[BR-FR-24/BT-29] : L'identifiant privé (cbc:ID) ne respecte pas le format autorisé. Valeur actuelle : " ". Seuls les caractères alphanumériques et les symboles "-", "_", "." sont autorisés.

ubl
[BR-FR-24/BT-46] : L'identifiant privé (cbc:ID) ne respecte pas le format autorisé. Valeur actuelle : " ". Seuls les caractères alphanumériques et les symboles "-", "_", "." sont autorisés.

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-24 A private identifier contains characters that are not allowedBR-FR-24 French BR-FR-CTC rulesBR-FR-24 BT-29BR-FR-24/BT-29 : L'identifiant privé (ram:GlobalID) ne respecte pas le format autorisé. Valeur actuelle : " ". Seuls les caractères alphanumériques et les symboles "-", "_", "." sont autorisés.BR-FR-24 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

Scheme 0224 carries a code two partners gave each other — a customer account number, a supplier code. Platforms copy it verbatim and match it character for character on arrival: a space or a comma is enough for the match to fail. 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

Normalise the code in your master data, in agreement with the partner who reads it. Factlint does not modify an identifier agreed between two companies.

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="0224">CLIENT 1234, AGENCE SUD</ram:GlobalID>

AFTER (compliant)

<ram:GlobalID schemeID="0224">CLIENT-1234_AGENCE-SUD</ram:GlobalID>