BR-FR-30
This is a French BR-FR rule from the AFNOR XP Z12-012 standard - a national requirement for invoices exchanged through France's e-invoicing network (PDP platforms) under the September 2026 mandate. Typical French specifics: the seller's SIREN (scheme 0002), mandatory payment mentions (late penalties, recovery costs, discount terms), and the invoicing framework code. The official rule text below is in French - the referenced BT fields identify what to add or fix.
- Read the official text - each sub-rule names the exact business term (BT) involved.
- Check the seller identifiers: SIREN in
CompanyIDwithschemeID="0002". - Check the mandatory French invoice notes (BT-22 with PMT/PMD/AAB prefixes).
- Validate against the
frprofile in our API to see all French findings at once.
[BR-FR-30/BT-128] : Parmi les identifiants d’objets facturés à la ligne (BT-128), les schémas d’identification "AFL" et "AVV" ne doivent être présents qu’une seule fois chacun. Actuellement : AFL = occurrence(s), AVV = occurrence(s). Veuillez supprimer les doublons pour respecter la règle.
[BR-FR-30/AFL] : L’identifiant associé au schéma "AFL" (cbc:ID) ne doit pas être vide. Valeur actuelle : "".
[BR-FR-30/AVV] : L’identifiant associé au schéma "AVV" (cbc:ID) ne doit pas être vide. Valeur actuelle : "".
[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, B2CINT, OUTOFSCOPE, ARCHIVEONLY. Valeur fournie : B2B : , B2BINT : , B2C : , OUTOFSCOPE : , ARCHIVEONLY : ". Veuillez corriger la valeur ou retirer le code sujet « BAR ».
Developers also reach this page searching for a “French e-invoice validation error”, a “Factur-X bill rejected” message, or how to fix a failed PDP compliance check — it's the same issue, explained above.
In short, in English: Among the line-level invoiced object identifiers (BT-128), the identification schemes "AFL" and "AVV" must each occur at most once.
Fix it faster
Paste your invoice XML in our free validator - every finding comes with its rule ID. Then generate, convert and render compliant invoices through one API.