Hi Charles,
Thanks again for the precise questions. Good timing: the next release (version 1.4.2) was built specifically around the new mandatory mentions of the reform, and it addresses all four of your points. Let me go through them.
A quick framing note first, because your terms come from two different French e-invoicing worlds:
- B2G / Chorus Pro (selling to a Public Administration): where “cadre de facturation”, “code service” and SIRET-based deposit live. In place since 2020.
- The 2026/2027 B2B reform (selling to private companies): routing goes through a Plateforme Agréée (PA, formerly called PDP) via the central directory keyed on SIREN/SIRET.
1) Seller and buyer electronic addresses
Both are already emitted (since 1.4.0): the seller electronic address (EN 16931 BT-34) comes from a settings field, the buyer electronic address (BT-49) is taken automatically from the checkout email. One honest nuance: the plugin writes them with the email scheme, which is a valid EN 16931 value, but an email is not what actually routes an invoice to a Public Administration. For Chorus Pro the recipient is located by its SIRET (plus a service code in BT-10 and an engagement number in BT-13 when the entity requires them); for the B2B reform it is located in the central directory by SIREN/SIRET. So the addresses are present and correct in the file, just do not read them as the routing key that posts to a PA.
2) “Type de facture” = goods / services / mixed
Added in 1.4.2. This is officially the “catégorie de l’opération” (livraison de biens / prestation de services / mixte), one of the new mandatory mentions of the reform, and it is distinct from the invoice type code in the standard (BT-3 = 380 invoice / 381 credit note). The plugin now auto-detects it from the order (virtual or downloadable products count as services, shippable products as goods, a mix is reported as “mixte”) or lets you set a fixed value in the settings. The mention appears on the invoice and credit note PDF and is carried in the Factur-X XML.
3) Optional SIRET / VAT for B2C customers
Already fully handled. The B2B fields (SIREN, SIRET, VAT number, PO reference) are optional in both the classic checkout and the Block checkout, and there is a global switch to hide them entirely. A B2C customer simply leaves them blank and the invoice omits them cleanly. So a mixed B2B + B2C store works out of the box: business buyers fill in their identifiers, consumers are never asked for them.
4) “Cadre de facturation”
Added in 1.4.2. It maps to EN 16931 BT-23 (Business process), and the plugin now emits it with the safe default A1 (standard supplier invoice); A2, A9 and A12 are selectable, and you can turn it off. As context: the cadre de facturation is a Chorus Pro / B2G concept, not part of the EN 16931 core nor of the new B2B reform mentions, so for ordinary B2B/B2C sales you do not strictly need it. It becomes relevant when you deposit an invoice to a Public Administration via Chorus Pro, where A1 is the standard default.
While addressing your questions, 1.4.2 also completes the other two new mandatory mentions of the reform: the delivery address (BG-15, shown when it differs from the billing address) and the optional “VAT paid on debits” mention. So the release covers all four new mandatory mentions plus the cadre de facturation.
One honest boundary so I do not over-promise: the plugin generates compliant Factur-X (PDF/A-3 + XML), CII and UBL files, but it does not itself transmit to Chorus Pro or to a Plateforme Agréée yet. That connector is intentionally inactive until the AIFE opens the B2B API (targeted before September 2026). So for a B2G deposit today you would still upload the file through the Chorus Pro portal; the plugin gives you the correct file to deposit.
1.4.2 is rolling out now. Happy to help if you run into anything once you update.
Best,
Antoine
