France spent years designing a system in which the tax administration would hold data on every domestic business-to-business invoice, and then arranged matters so that it would not carry a single one. That is not a contradiction. It is the compromise the French reform makes, and most of what a finance function needs to know follows from it.
The document travels between two private operators, each registered by the administration for that purpose. What the administration receives is an extract of the invoice data, plus a stream of statuses telling it what happened after the document left. Neither the vocabulary of a pure network nor the vocabulary of clearance describes that arrangement, and people who arrive holding one of them get the important part wrong.
The important part is this. The operator that moves your invoice is also the operator that files data about it. Two jobs, two different failure modes, one registration.
The shape France chose
In a network model the seller's provider hands the document to the buyer's provider and the administration is nowhere in the path. In a clearance model the administration's own platform sits in the path, and the invoice is not an invoice until that platform says so. France sits between the two: exchange happens provider to provider, and a fifth participant receives data rather than documents.
That fifth position is what separates the French design from the architectures set side by side elsewhere on this site. The administration is not a gate each document passes through and is cleared by. It is a recipient of structured data and the holder of the directory that makes routing possible. Delivery does not wait on it.
What registration obliges a platform to do
Registration is not a badge. It is a set of continuing obligations owed to the tax administration, granted for a fixed and renewable term and conditional on audit. A registered platform must be able to:
- accept and produce the base set of syntaxes the reform names — the two European syntaxes and a hybrid format carrying a readable rendering and structured data in one file — and convert between them without losing meaning
- extract the required invoice data and transmit it for every in-scope document it handles
- emit and receive the defined lifecycle statuses, some of them mandatory, some left to the parties
- maintain its customers' routing entries in the central directory and keep them current
- report transactions falling outside the domestic invoicing obligation, with the payment information that services require
- meet security, hosting and certification conditions, and submit to periodic verification of them
- hand its customers over intact if the registration ends
That is a messaging service and a filing service under one registration, with the tax administration as counterparty to half of it.
Two jobs, one registration
The useful comparison is not between platforms. It is between a registered platform and the ordinary access point a European business already knows from network countries.
| Responsibility | Registered partner platform | Ordinary network access point |
|---|---|---|
| Source of standing | Registered by the tax administration, renewable term | Admitted under the network's own governance |
| Owes duties to | Its customer and the tax administration | Its customer and the network operator |
| Delivery job | Carry the document to the counterparty's platform | Carry the document to the counterparty's access point |
| Data to the administration | A defined extract of every in-scope invoice | None |
| Statuses | Mandatory lifecycle statuses, reported onward | Transport acknowledgement between operators |
| Directory duties | Registers and maintains customers' routing entries centrally | Publishes capabilities in the network lookup service |
| Format duties | The national base set, with conversion between it | The network's own profile |
| Out-of-scope transactions | Reports them, payment data included for services | Not its concern |
| If the status is lost | Customers must migrate to stay compliant | Another operator picks up the traffic |
The directory is the part that hurts first
Routing needs an address, and a company name is not an address. In France the anchor is the national business identifier, and routing frequently has to go finer than the legal entity — an establishment, or a service code within one, because a group with a single legal identity may run six accounts payable teams that must not receive each other's invoices.
The central directory holds that mapping: participant, granularity, and the platform that speaks for them. Platforms populate it on behalf of their customers, from data the customers supply.
A routing entry that is well formed but wrong does not bounce. It delivers the document, on time, to a platform the buyer does not read. The invoice is legally issued, the seller's system shows success, and nobody notices until the payment run does not happen. Entries also go stale: a buyer changes platform, an establishment opens after onboarding, a service code is retired. And on the first day of an obligation wave, every entry in the country is new at once.
What leaves the invoice and what stays between the parties
The administration receives an extract, not the document. The required set is defined; the rest of the invoice — attachments, contract references, free-text explanations, the commercial detail that makes the document useful to the buyer — travels between the platforms and stops there.
Statuses are the other half of what it sees. They record that a document was deposited, that it reached the recipient, that it was refused. That is a stream about the life of the invoice, not about its contents.
Then there are the transactions that never produce a French domestic invoice: sales to consumers, and cross-border supplies. There is nothing in the exchange path to extract from, so the obligation becomes a reporting one, and for services the timing follows payment rather than issue. That split is set out in invoicing and reporting as two separate obligations.
A platform can only transmit what your system gives it. A VAT number that is right on a printed invoice and wrong against a code list, a country carried as a label rather than a value, a customer record with no establishment identifier — none of these stop a PDF from being sent, and all of them stop a filing from being clean.
The calendar has moved, and any summary of it is already suspect
The French timetable has been changed more than once, and the scope of the public portal changed with it. The stable part is the sequence rather than the dates: the obligation to be able to receive comes first and applies broadly, and the obligation to issue and to report follows in waves ordered by company size.
Take the dates from the tax administration and the ministry as they stand on the day you plan — not from a vendor deck, not from a conference slide, and not from this article. Which entities are caught, and the current state of each step, belong in the reform's scope and timetable, read against the primary sources beneath it.
What actually decides whether this works for you
Registration is table stakes; every serious candidate holds it. The questions that separate operators are duller. Who maintains your directory entries, and how quickly is a correction live? Which statuses does the platform emit on its own, and which does it expect your system to originate? What does it do with a reporting obligation for a transaction that never became an invoice? What happens to your entries and your archive if you leave?
Many registered platforms also operate on the interoperability network most of your other counterparties use, which saves running two providers. That is a convenience, not a substitute: network membership does not confer French registration, and registration does not put you on the network. The broader criteria are in how to assess a provider.
What decides the outcome is upstream of all of it. A platform can only publish the identifiers you give it and file the data your ledger produces. France arranged for one private company to do the exchange work and the filing work at once, which means one contract instead of two. It does not mean one problem instead of two, and the half that stays yours is the half nobody can register on your behalf.
