As the deadline for electronic invoicing draws nearer, companies find themselves faced with a central question: which platform to choose?
The market is structured around this question with its product demonstrations, functional comparisons, promises of rapid integration, everything contributes to positioning the choice of the solution as the starting point of the project. However, in many cases, this is an inversion of logic.
Because the reform does not primarily pose a tool problem, it highlights the complexity of invoicing situations, often poorly documented, and sometimes poorly controlled.
Technical reform, heterogeneous practices
The regulatory framework is now stabilized, from September 2026, all companies must be able to receive electronic invoices, while the largest must also issue them. The emission obligation will be generalized in 2027.
The target model is known: structured formats, interconnected platforms, a directory for addressing, and almost instantaneous transmission of data to the tax administration.
On paper, the mechanics are uniform, but in reality, it applies to organizations that are not.
And this is where you need to pay attention, because a company does not invoice within a single framework. It invoices in a succession of situations: advance payments, final invoices, multiple orders, subcontracting, factoring, expense reports, international flows. So many cases which, each obey specific rules.
Use cases that structure the project
To frame this diversity, several dozen use cases were formalized in the preparatory work for the reform. This granularity reflects the operational reality of companies.
Each case involves:
- data to be produced,
- checks to be carried out,
- validation circuits,
- integration constraints.
Two companies subject to the same regulatory obligations can therefore have very different functional needs.
One will be able to rely on simple, largely automatable flows, while the other will have to manage an accumulation of particular cases, with strong dependencies on its information system.
The blind spot: choosing before understanding
In many organizations, this complexity is not formalized, it is known to the teams, but rarely documented.
The risk is then to choose a platform on the basis of generic criteria (compliance, price, connectors) without having precisely described the flows to be covered.
Thus a solution can perfectly meet regulatory requirements while being unsuitable for the company’s business reality.
This discrepancy is not immediately visible, but it will appear during implementation, then in operation:
- with its uncovered flows,
- missing data,
- persistent manual processing,
- more frequent rejections or disputes.
Map to pilot
Mapping use cases constitutes, in this context, a structuring step.
It consists of objectifying what the company really does:
- what types of invoices are issued and received,
- what particular scenarios exist,
- which tools produce the data,
- what information is available,
- where the manual processing is located,
- how validations are organized.
This work often reveals gaps between current practices and the requirements of the target model. It also highlights areas of weakness, whether incomplete data, implicit processes, or technical dependencies.
Beyond compliance, a question of organization
All so-called “approved” platforms will ensure a minimum base: emission, reception, transmission of data, status management.
The difference, however, lies in the ability to absorb the complexity of use cases.
This is what determines, concretely, the ability to automate:
-
- reconciliation between order, receipt and invoice,
- workflow management,
- handling disputes,
- or even the management of recovery.
Without prior mapping, these dimensions remain difficult to assess.
A reform which acts as a revealer
Electronic invoicing does not only transform flows. It exposes existing fragilities, and makes visible practices that were previously tolerated:
-
- missing or approximate data,
- informal validations,
- parallel circuits,
- dependence on manual treatments.
By imposing structured formats and reinforced traceability, it forces companies to formalize what could remain implicit.
Change question
In this context, the initial question, which platform to choose? appears secondary, and the structuring question becomes: how do we actually bill?
It is from this understanding that the choice of a solution can be relevant. Not as a standard response to a regulatory obligation, but as a tool aligned with the reality of flows.
The reform standardizes the transport of the invoice but does not standardize the organizations.
