Mandatory electronic invoicing in France: structuring your compliance

The French electronic invoicing reform is one of the most structuring regulatory changes for the information systems of businesses operating in France. It is not a format update: it reshapes invoicing flows, accounting processes, exchange architectures and reporting obligations towards the tax authorities.

Two distinct obligations, often confused

• Electronic invoicing (e-invoicing): issuing and receiving invoices in a structured or hybrid format — Factur-X, UBL, CII — between businesses subject to French VAT. Unstructured PDF invoices are no longer accepted in the B2B exchanges concerned.
• Data reporting (e-reporting): transmission to the tax authorities of data on transactions not covered by e-invoicing — B2C sales, operations with foreign businesses not established in France. This obligation applies in parallel, to the same deadlines.

The flows concerned cover the whole invoicing cycle: issuing, receiving, credit notes, deposits, recurring invoices. Each type of flow has its own format rules and its own transmission circuit.

The rollout timetable: receiving first, issuing next

The obligation applies progressively, by company size. The first two deadlines have now passed.

• Since September 2026: the obligation to receive applies to every business subject to French VAT, whatever its size. Each one must be able to receive invoices in a structured format.
• Since September 2026: the obligation to issue applies to large companies and mid-caps.
• From September 2027: the obligation to issue extends to small and mid-sized businesses.

Organisations still behind on receiving are therefore already non-compliant. Receiving is often treated as secondary to issuing. It nonetheless implies reworking the accounting processes that handle supplier invoices — automated receipt, checking, matching, dispute management.

The technical ecosystem: accredited platforms, the public portal and compatible solutions

The distribution of roles changed during the reform. Since the tax administration's announcement of October 2024, the public portal no longer transmits invoices: connecting to an accredited platform is the only route, for every business, whatever its size or volume.

• Accredited platforms: private operators registered by the administration, the only ones authorised to issue, transmit and receive invoices, and to file e-reporting data. Since July 2025, "accredited platform" has replaced the earlier "partner dematerialisation platform" designation: same status, same role, new name.
• The public invoicing portal: refocused on two infrastructure missions. It holds the central directory, which says which accredited platform each business is attached to through its company registration number, and acts as the concentrator for the data sent to the tax authorities for VAT control. The free issuing and receiving service initially announced has been dropped.
• Compatible solutions: technical intermediaries, formerly "dematerialisation operators", which prepare and format the flows between your management tool and your accredited platform. They hold no regulatory status and do not remove the need to connect to an accredited platform.

The question is therefore no longer whether to go through an accredited platform, but which one, and with what exchange architecture towards your ERP: invoice volume, ability to integrate what exists, reconciliation needs. It is an architecture decision — not a service purchase.

How to structure the implementation

A successful implementation follows a precise sequence. The projects that run into difficulty are generally those that compressed or reversed it.

1. Map the invoicing flows: identify every issuing and receiving flow, the systems involved, the formats used and the edge cases — credit notes, deposits, multi-establishment set-ups, existing EDI flows. This step takes time and determines every decision that follows.
2. Analyse what the ERP covers: check the vendor's roadmap, assess how the edge cases are covered on the instance in production, identify the custom developments concerned. This analysis has to be run against the real instance — not against the vendor's standard documentation.
3. Choose the accredited platform and the exchange architecture: on the basis of the mapped flows and the ERP analysis, define the target architecture, then select the accredited platform that fits it and, where needed, the compatible solution — in that order.
4. Bring the data up to quality: structured formats demand precise data — registration numbers, intra-community VAT numbers, normalised addresses. This workstream has to be part of the project from the start, not run alongside it.
5. Train and support the accounting teams: the processes for handling supplier invoices change. Change management is a component of the project in its own right.

On a standard ERP, full compliance generally takes six to nine months. On a heavily customised instance, or in a multi-system context, allow more. These timescales include the testing, acceptance and training phases — not only the technical build.

This logic is not specific to invoicing: a regulatory framework that imposes technical constraints on a management system always calls for the same approach — map what exists, measure the gap, plan the path to compliance. Point-of-sale software follows a comparable trajectory, with the LNE standard.