A private identifier exceeds 100 characters

A party identifier in scheme 0224 — the private identifier of the seller (BT-29) or the buyer (BT-46) — is limited to 100 characters.

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-26/BT-29 : L'identifiant privé (ram:GlobalID) dépasse 100 caractères. Valeur actuelle : " ". Veuillez raccourcir cette valeur pour respecter la limite.

cii
BR-FR-26/BT-46 : L'identifiant privé (ram:GlobalID) dépasse 100 caractères. Valeur actuelle : " ". Veuillez raccourcir cette valeur pour respecter la limite.

ubl
[BR-FR-26/BT-29] : L'identifiant privé (cbc:ID) dépasse 100 caractères. Valeur actuelle : " ". Veuillez raccourcir cette valeur pour respecter la limite.

ubl
[BR-FR-26/BT-46] : L'identifiant privé (cbc:ID) dépasse 100 caractères. Valeur actuelle : " ". Veuillez raccourcir cette valeur pour respecter la limite.

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-26 A private identifier exceeds 100 charactersBR-FR-26 French BR-FR-CTC rulesBR-FR-26 BT-29BR-FR-26/BT-29 : L'identifiant privé (ram:GlobalID) dépasse 100 caractères. Valeur actuelle : " ". Veuillez raccourcir cette valeur pour respecter la limite.BR-FR-26 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

A code agreed between partners fits in a few dozen characters; beyond that, it is almost always a label or a concatenation of fields that took the code's place, and the partner will not recognise it. 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 the code as the partner expects it, and nothing else. Factlint does not truncate 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">COMPTE-CLIENT-1234-OUVERT-LE-12-03-2019-PAR-LE-SERVICE-COMMERCIAL-REGION-SUD-OUEST-CONDITIONS-2026-NET-30-JOURS</ram:GlobalID>

AFTER (compliant)

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