France's e-invoicing reform doesn't just change how you send a bill. It changes who's legally allowed to send it, what's allowed to count as one, and how it finds its way to the right desk once it's out the door. Most teams don't discover that until they're already mid-implementation, staring at terms like PA, PPF, and "the Annuaire" with no idea what any of it actually means.
This guide lays out the vocabulary and the mental model behind all of it: who's actually involved in a French e-invoicing exchange, what the reform considers an "invoice" in the first place, and how invoices and their statuses actually find their way to the right inbox. If you're on an AR, AP, tax, or IT/solution delivery team gearing up for implementation, this is the layer everything else gets built on.
Meet the players
Every invoice has a Seller and a Buyer, that part isn't new. The Seller books the invoice as revenue and is generally on the hook for collecting VAT; the Buyer books it as an expense and is generally the one who deducts VAT and pays. What's new is how many other roles the reform formally recognizes, because real B2B transactions in France rarely stay that simple.
A few show up often enough to know by name:
- Payee: whoever actually receives payment, when it isn't the Seller. A factoring company is a Payee. An invoice can have more than one.
- Seller's Tax Representative: stands in for the Seller with the tax authority when the Seller doesn't represent itself directly.
- Payer: whoever actually pays, when it isn't the Buyer. Common in group structures where a parent company settles invoices for its subsidiaries, or in insurance scenarios where a claim partially covers the bill.
And a smaller "extended cast" that only shows up in specific scenarios, but matters a lot when it does:
- Invoicer: a third party creating and sending invoices on the Seller's behalf, under a formal billing mandate.
- Seller's Agent: acts for the Seller, often handling sales and invoicing together.
- Addressee ("Billed to"): the party that technically receives and processes the invoice on the Buyer's behalf, even though the Buyer is still the legal party on the hook. Think shared services centers or outsourced AP teams.
- Buyer's Agent: acts for the Buyer, typically during ordering or dispute handling.
Then there's a second layer of actors that aren't parties to the transaction at all, they're the plumbing:
- Accredited Platform (PA): the only entities actually authorized to exchange e-invoices between businesses and to transmit the required tax data to the French authorities. Every company sends and receives through one (or several).
- Compatible Solution (OD/SC): software or service providers that sit between a company's own systems and its Accredited Platform. Your ERP add-on or middleware vendor is probably one of these.
- PPF (Public Invoicing Portal): this is the part that trips people up, because its role changed partway through the reform's design. The PPF no longer routes invoices directly. Today it's a directory and tax data hub: it maintains the master list of who can receive what at which address, and it's where the mandatory tax-relevant statuses ultimately land. The actual invoice traffic flows platform-to-platform.
That last point is worth sitting with, because a lot of outdated commentary still describes the PPF as the central hub every French invoice passes through. It isn't, anymore. The real question for your implementation isn't "how do we connect to the government portal," it's "which Accredited Platform do we use, and how does it talk to our ERP."
A framework for the complexity
If you've looked at the full catalogue of French e-invoicing use cases, the sheer number can feel overwhelming: subcontracting, factoring, self-billing, multi-vendor invoices, barter arrangements. It helps to know that the standard itself groups them into three underlying kinds of complexity, and most of them boil down to one of these:
- Data cases: the transaction itself is straightforward, but the invoice needs to carry more (or different) data than a plain sale. Multiple delivery addresses on one invoice is a good example: nothing unusual about the deal, just extra structure required on the document.
- Third-party cases: someone besides the Buyer and Seller needs to see, pay, or process the invoice. This is where Payer, Payee, Invoicer, and the various Agent roles above actually get used, and where questions about who has access to what become real.
- Lifecycle cases: less about who's on the invoice, more about what happens to it afterward: rejections, disputes, credit notes, corrected invoices. These hinge on status tracking more than document structure.
Some scenarios genuinely straddle more than one bucket. Factoring, for instance, is both a third-party case and one with its own lifecycle statuses. But as a rule of thumb, this framework is a fast way to size up a new scenario: is this fundamentally about what data goes on the invoice, who else is involved, or what happens after it's sent? That answer tells you roughly where to look and how much implementation lift to expect.
What actually counts as an "invoice"
The reform recognizes seven distinct invoice types, and it's worth knowing all seven before you assume every French B2B document you handle is a "simple invoice":
| Type | What it is |
|---|---|
| Simple invoice | The standard case, one Seller, one Buyer, nothing unusual. |
| Pre-payment invoice | Issued for a deposit or down payment, before delivery or performance. |
| Factored invoice | Sold to a third-party factor, the Payee on the invoice is the factor, not the Seller. |
| Self-billed invoice | Created by the Buyer on the Seller's behalf, under a billing mandate, common when a large buyer standardizes billing across its suppliers. |
| Corrected invoice | Cancels and replaces an earlier invoice. It functions as both a credit note against the original and a new invoice at once. |
| Credit note | The standard reduction or refund document. |
| Multi-vendor invoice | A single invoice covering goods or services from several Sellers, consolidated by a transparent intermediary and paid to one centralized Payee. Only available under the France-specific extended profile. |
If your business only ever issues plain sales invoices and the occasional credit note, most of the reform's complexity won't touch you. If you factor receivables, self-bill your suppliers, or run anything through a consolidating intermediary, you're going to live in the other rows on this table.
Electronic addresses: the postal system for e-invoices
Every party in a French e-invoicing exchange, Seller, Buyer, and any of the third parties above, needs an electronic address. It's the digital equivalent of a postal address: the piece of data that tells the network where an invoice, or a status update about that invoice, should actually go.
Most French companies are addressed simply by their official business registration number, so you're rarely negotiating this with a customer directly. The PPF Directory, often called "the Annuaire," is the master lookup table for all of it: a government-maintained registry, publicly searchable through the Chorus Pro portal, that already lists where every VAT-registered company's invoices need to go. In practice, this means once you know who you're billing, you can look up exactly where to route their invoices. You don't need to ask them for their address separately, and you shouldn't need to guess.
If a recipient isn't listed in the Directory yet, there's a built-in tolerance: you're allowed to treat them as not currently subject to the e-invoicing obligation and fall back to e-reporting instead, without being penalized for a gap that isn't your fault.
A few practical points worth internalizing early, especially if you're the one deciding how your company's addressing gets set up:
- Fewer, more stable addresses beat many narrow ones. Every address change means notifying every counterparty who sends you invoices, that's real operational churn, not a one-click update.
- If you need more than one address (for example, to route high-volume employee-expense invoices somewhere dedicated), prefer ones you choose and manage yourself over ones tied to your physical or legal location structure. Addresses tied to that structure break whenever it changes; freely-chosen ones don't.
- Don't create a separate address per department or approver. It's tempting to want a mailbox per cost center, but organizations reorganize far more often than invoicing infrastructure should. Route internally using data that's already on the invoice, order numbers, contract references, buyer references, not by multiplying addresses.
- Self-billing flips the usual direction. When the Buyer is creating the invoice on the Seller's behalf, it's the Seller's receiving address that matters for the invoice itself, since the roles of "who's sending" and "who's being billed" are reversed from the normal flow.
Where this leaves you
Know who the players can be in France's system, which of the seven invoice types you're actually dealing with, and how addressing works, and you're already ahead of most teams walking into their first implementation conversation.
Ready to see where your organization actually stands? Take our free France readiness check, or talk to us about e-Invoicing implementation.