France E-Invoicing 2026: The Four New Invoice Fields ERP Teams Need to Check
Published August 2026 by Solarc Labs
The reform adds four invoice mentions that deserve explicit mapping ownership
French government guidance highlights four additional invoice mentions from 1 September 2026: the customer SIREN number; the category of the transaction, such as sale, service or a distinct combination of both; the option for VAT payment on debits where applicable; and the full delivery address when it differs from the customer billing address. These are easy to list and much harder to guarantee across every source system. Each one needs a defined source of truth and a mapping owner.
Customer SIREN is a master-data problem before it is a file-format problem
If the customer identifier is missing, stale or stored inconsistently across business units, adding a required XML element at export time does not solve the underlying data problem. The cutover team should identify where the customer SIREN comes from, which records lack it, how exceptions are handled and whether the value survives every mapping step into the final structured invoice. Test the actual production master-data patterns, not only newly cleaned customer records.
Transaction category and VAT-on-debits are conditional business semantics
A transaction-category field is only useful if the ERP can distinguish the underlying business case correctly. The VAT-on-debits mention is similarly conditional: it should be populated when the option applies, not turned into a universal hard-coded value. These fields are a good example of why schema validation alone is insufficient. A field can be syntactically present and still carry the wrong business meaning.
A separate delivery address creates another conditional mapping path
The full delivery address becomes relevant when it differs from the billing address. That means teams need to test customers where the two addresses are the same, where they differ, and where delivery information comes from an order or logistics system rather than the customer master record. A representative corpus should deliberately include these branches so a clean default address path does not hide a broken exception path.
Field presence is not a certification result
Checking these four mentions is useful, but it is not equivalent to legal certification, PA transmission or recipient acceptance. A production invoice still sits inside a larger set of syntax, profile, business-rule, routing and operational requirements. InvoiceBatch FR treats the four mentions as part of a broader representative-corpus preflight. It is not a Plateforme Agréée; the output is technical evidence for ERP and finance teams, not a claim that the administration or recipient platform will accept every invoice.
Primary sources
Sources used for this article
Continue the job