French E-Invoicing 2026: What a Multi-Entity Group Must Have Decided by Now
From 1 September 2026, every VAT-registered business in France must be able to receive structured electronic invoices, and large companies and mid-caps must also issue them — smaller companies follow on 1 September 2027. For a group with several French entities, this is not one compliance project but one per legal entity, and the decisions interact. We built a free two-minute audit around exactly these questions; this article walks through the six decisions it tests, and what we see when groups answer them late.
Why is reception the deadline everyone underestimates?
The issuing mandate is phased; the receiving mandate is not. On 1 September 2026, all French entities — including the smallest subsidiary in your group — must be able to accept a structured invoice arriving through a certified platform, and there is no deferral. The reform follows the tax authority’s five-corner model: invoices travel between certified platforms (plateformes agréées, formerly called PDPs), not by email.
The practical consequence for a group: your suppliers’ invoices will start arriving as structured Factur-X or UBL files addressed to each legal entity. If an entity has no platform and no reception process on that date, its supplier invoices do not have a legal front door. Reception readiness per entity is the first line of our audit for a reason — it is the obligation with the earliest bite and the least visibility in board discussions, which revolve around issuing.
One certified platform for the group, or one per entity?
This is the structural decision, and the honest answer is: it is not automatically “one for everyone”. Certified platforms differ in pricing model, in the services bundled around the invoice flow (financing, dunning, archiving), and in how well they fit an entity’s profile. In our own partner work we operate with more than one platform deliberately, because a large multi-subsidiary client and a small single-entity company are not well served by the same offer.
Two facts shape the group decision. First, platform pricing is typically per invoice and degressive with volume: consolidating the group’s volumetry onto one platform changes the unit price band you negotiate. Second, subsidiaries are not equal: an entity doing 200 invoices a month with consumer sales has different e-reporting needs than a B2B entity doing 20,000. The group question is therefore not “which platform?” but “which platform strategy?” — one platform with a group contract, or a deliberate split by entity profile. Both are legitimate; drifting into one by default is not.
Who pilots the subject — group or subsidiary?
In the groups we audit, this is the question most often left unanswered: everyone assumes someone else owns it. Our questionnaire asks it bluntly — who pilots the subject in your organisation — because the answer determines everything downstream: who signs the platform contract, who owns the invoice data quality in each ERP company, who tests, who declares readiness.
The workable pattern we see is a group-level decision on platform strategy and contract, with entity-level ownership of data and testing. What does not work is a group IT team “handling e-invoicing” without touching each entity’s Business Central company — because the failures happen at the record level, entity by entity.
What actually gets an invoice rejected?
Not the big architecture — the small fields. The French business rules enforced on every structured invoice include: the seller’s SIRET is mandatory, the seller’s SIREN is mandatory, and the buyer’s electronic routing address is mandatory. In Business Central terms: Company Information must carry a valid SIRET and registration number in every company, and every customer card needs an electronic address. One missing SIREN on a customer, one badly configured billing mandate, and the flow is rejected — and you only discover it by opening the database, entity by entity.
This is where multi-entity groups pay the multiplication penalty: master data quality is not a group property, it is a per-company property. Our full audit runs 67 control points against a Business Central configuration, built from our real projects, and the majority of red flags we find are data-level: missing identifiers, incomplete customer records, dimensions that will not survive contact with a structured format. A clean multi-company setup makes this dramatically cheaper; a historically grown one makes it the main workstream.
Is Business Central ready — and what does that change for your timeline?
Microsoft ships French e-invoicing through the standard E-Documents module plus a French localization: Peppol BIS3 (UBL) and Factur-X formats, mandatory lifecycle statuses, and transaction e-reporting for operations outside the B2B invoicing scope. Microsoft does not act as a certified platform itself — you still need your platform choice, connected through an e-document service.
The timeline fact that matters: the localization reached general availability in July 2026, weeks before the September deadline. Nobody has years of production hindsight on this stack — which means your safety margin is not the software’s maturity, it is your own testing. For a group, multiply that: each entity’s Business Central company needs its e-document service configured, its formats selected, and at least one real supplier and customer flow tested. That is a per-entity checklist, and September is close. If your entities run on an older NAV or heavily customised base, the honest first step is knowing whether they can even take the update, which is exactly what our pre-project clarity form is built to establish.
What about the invoices that are not B2B domestic?
The reform has a second half that group DAFs discover late: e-reporting. Transactions outside the domestic B2B invoicing scope — sales to consumers, cross-border B2B, exports — must be reported to the tax authority on a monthly or quarterly rhythm. Business Central generates these payloads through the French e-reporting format, sent through the same platform plumbing.
For a group this changes the platform conversation again: an entity with significant B2C or export activity has an e-reporting profile that some platforms serve better than others. It is one more reason the platform decision is a per-profile decision, not a logo decision.
FAQ
When exactly do the French e-invoicing obligations start?
On 1 September 2026, all VAT-registered businesses in France must be able to receive electronic invoices, and large companies and mid-caps must issue them. Issuing extends to smaller companies on 1 September 2027. There is no announced deferral.
Can a group use different certified platforms for different subsidiaries?
Yes. Nothing in the reform requires a single platform per group, and profiles often justify a split — but pricing is volume-degressive, so splitting has a cost. Make it a deliberate decision on consolidated volumetry, not an accident of subsidiary autonomy.
Does Business Central handle French e-invoicing natively?
Business Central covers formats (Peppol BIS3, Factur-X), lifecycle statuses and e-reporting through its E-Documents module and French localization, generally available since July 2026. It does not replace a certified platform — you connect one through an e-document service, and that connector layer is exactly what we built with FacturaLink, our Business Central connector for Plateforme Agréée.
What is the most common blocker you find in audits?
Master data, per entity: missing SIREN/SIRET, customers without electronic routing addresses, incomplete registration data. The French business rules reject flows on these fields, and they have to be fixed company by company.
Where do we start if nothing has been decided yet?
Reception readiness first — it applies to every entity on day one. Then the platform strategy on consolidated volumes, then a data audit of each Business Central company. Our free two-minute audit tells you where your exposure is; talk to us for the full 67-point review.