Skip to main content
Registration on the French Directory is required for any SIREN that will issue, report or receive invoices through Invopop as its Plateforme Agréée. Each party (a SIREN) is registered once. The workflow collects a signed agreement, registers the party in the French Annuaire, publishes it on the Peppol network and registers for Reporting. After registration is completed, the party can both send and receive invoices as well as report transactions. The Annuaire requires every entry to be receive-capable, so there is no send-only option as in other Peppol countries. For parties that only need to receive invoices for now — most SMEs and micro-businesses until September 2027 — see Registering without e-reporting.
A single SIREN registered in the Annuaire can have several directory entries, registered under the same or different Plateformes Agréées. Each entry has its own electronic address, set as the code of the party’s peppol inbox. Invopop registers addresses in one of the forms SIREN, SIREN_SIRET, or SIREN_suffix; addresses with a routing code (SIREN_SIRET_routingcode) aren’t supported. See Choosing the electronic address.

Example of French supplier

This example shows a French supplier party. Key points to note:
  • The tax_id contains the French TVA number without the FR prefix: a 2-digit control key followed by the company’s 9-digit SIREN.
  • The SIREN identity uses the iso-scheme-id extension 0002 (SIRENE), and must match the last 9 digits of the TVA number.
  • The person in people is the company representative required to sign the mandat de facturation (billing mandate), including their role.
  • The peppol inbox uses scheme 0225 (French CTC electronic address). A single SIREN registered in the Annuaire can have several directory entries, registered under the same or different Plateformes Agréées. Each entry has its own electronic address, mapped to the Peppol inbox’s code, in one of the forms SIREN, SIREN_SIRET, or SIREN_suffix. Addresses with a routing code (SIREN_SIRET_routingcode) aren’t supported.
    • If no inbox is specified, the Register for Peppol step assigns one automatically, using scheme 0225 with the supplier’s bare SIREN as the code, ignoring any SIRET present in the supplier’s identities.
    • To register a specific directory entry instead, set the inbox explicitly, for example:
      This registers the endpoint 526018155_INVOPOP under the SIREN 526018155 in the Annuaire. Here is the full example of a Party
France supplier example

​
Choosing the electronic address

The address you register decides which invoices Invopop receives for the company. This matters most for platforms that register the companies they issue invoices for, such as marketplaces and invoicing software.
  • The bare SIREN is the company’s main address. With no inbox set, the workflow registers SIREN. Senders that address the company by its SIREN deliver there, so only register it if Invopop should receive all of the company’s incoming invoices.
  • Use a dedicated address when you only issue on the company’s behalf, or when it already has, or will have, another PA. Set the inbox explicitly to a SIREN_suffix address such as 526018155_PLATFORMNAME, as in the example above. The company’s other addresses stay with its own PA.
  • Statuses come back to the sending address. Lifecycle statuses on invoices you send from an address are delivered to that address, so a dedicated address still receives the statuses for the invoices you issue.
  • Companies with several establishments need only one registration per SIREN, with a single mandate signature. Put each establishment’s SIRET on its invoices, in the supplier’s identities; it’s independent of the directory address. Register one suffix per establishment only if you need statuses delivered to separate addresses: each address is a separate party entry and registration.
  • Pick a suffix with a clear meaning. The DGFiP recommends suffixes that make their purpose obvious and that don’t look like a SIRET. A 14-digit suffix that starts with the SIREN is read as a SIRET.
  • If another PA already holds the address, registration fails; see Outgoing takeovers.

​
PPF register supplier workflow

PPF register supplier

Add to my workspace →

​
Agreement signing

The gov-fr.agreement.sign step generates the mandate and publishes a link_url under the approval-link key in the silo entry meta. Each silo entry registers one Annuaire address, so the step fails on a silo entry that already has an active registration; use a new silo entry for each additional address. The party representative can complete signing through the registration wizard, or platforms that want full control can use the entry API directly.

​
Registration wizard

Once the workflow step runs, find the link_url in the approval-link meta entry of the silo entry. In console, it appears in the Meta tab of the entry’s right sidebar.
Forward the link_url to the party representative, or embed it as an iframe to keep them within your platform. The wizard walks the representative through each step:
1

Party details

Review and confirm the pre-filled company and signer information.
2

Identity document

Upload a photo of the signer’s ID card (front and back) or passport page.
3

Sign mandate

Sign the pre-filled mandate directly in the browser, or upload a pre-signed PDF.
4

Confirm

Submit for Invopop review. The party status moves to submitted until a decision is made.

​
Entry API

For platforms that want to drive the signing process programmatically, use the entry API (all endpoints under /apps/gov-fr/v1/entry/{silo_entry_id}/). Identity verification is required on both paths.
The customer signs the mandate directly. Invopop stamps the signature and verifies identity.
1

Download mandate

GET /agreement returns the mandate PDF pre-filled with the party’s details. Fails with 422 if any required signer field is missing.
2

Upload identity document

POST /identity uploads one face at a time: front + back for an ID card, or page for a passport.
3

Sign the mandate

POST /sign stamps the signature. Pass a drawn PNG or JPEG image in signature (≤ 4 MB), or omit it to render the signer’s name as a typed signature.
4

Confirm

POST /confirm finalises the submission and returns a status field. submitted means the party is under approval review before registration continues.

​
Registering without e-reporting

Obligations under the French mandate kick in separately: from 1 September 2026 every business must be registered in the Annuaire to receive e-invoices, but SMEs and micro-businesses are not required to issue e-invoices or e-report until 1 September 2027 (see the timeline). If you onboard many smaller suppliers, most of them initially need only an Annuaire line and a Peppol inbox — not a reporting registration. The default template registers the party for everything, including reporting. To register parties for receiving only, create a modified copy of the template:
1

Add the template

Add the PPF register supplier template to your workspace and rename the copy, e.g. “PPF register supplier — Annuaire only”.
2

Remove the reporting step

Delete the Register party for reporting (gov-fr.reporting.register) step. Keep the Directory and Peppol steps — every Annuaire entry is receive-capable, so nothing else needs to change.
3

Run it for receive-only parties

Use this workflow for parties that don’t yet have issuing or reporting obligations, and keep the unmodified template for those that do. Receive-only parties appear in the Parties tab with a dash in the Reporting column.
When a party’s e-reporting obligations begin — for example when the September 2027 mandate reaches SMEs and micro-businesses — complete its registration by running the Register party for reporting step against the party’s silo entry: create a workflow containing just that step and run it on the already-registered party. The VAT regime is picked the same way as in the full registration.
A party registered without the reporting step is not on any reporting cadence: Invopop only generates and files Flux 10 reports for parties registered for reporting. The signed agreement is the same in both cases, so no new mandate is needed when reporting is added later.

​
PPF unregister supplier workflow

PPF unregister supplier

Add to my workspace →

​
Reading parties registrations

The France dashboard’s Parties tab shows the registration state of every SIREN in the workspace. In the Console, open the Apps view and select the France app. The dashboard opens on this tab. Each row carries the party’s Name, its number of Annuaire entries, the SIREN, the registration State, the Silo entry that holds the party, whether Reporting is enabled, the VAT regime selected at registration, and the date the approval was Decided. A check mark in the Reporting column means the party is also registered for e-reporting; a dash marks a party registered only for e-invoicing. The VAT regime pill shows the cadence its reports follow.
Clicking a row opens a side panel with the party’s Annuaire lines: one block per directory entry with its Endpoint (the electronic address), the registered Name, and the Silo entry id. Every value has a copy button. Lines that have been unregistered appear greyed out and carry a Disabled at row with their deactivation date.
Filter the table by SIREN, State, or whether Reporting is enabled.

​
FAQ

For B2B PA flows: register the supplier via the France PA Register Party workflow (publishes the SIREN to the Annuaire and Peppol). For Chorus Pro: register the supplier with their SIRET on Chorus Pro’s portal and link credentials in the Chorus Pro app.
France PA does not require supplier-side certificates — Peppol uses Invopop’s AP cert. Chorus Pro uses an OAuth token bound to the supplier’s account; the token is encrypted at rest in Invopop.
Run the France PA Register Party workflow with the supplier’s SIREN. Invopop publishes them to the Annuaire and the Peppol SMP — they are then routable for both invoicing and e-reporting through Invopop.
Yes. This is a common setup, for example a company handling AR with one PA and AP with another. Run the registration workflow with a SIREN and suffix of your choice for the flow you want Invopop to handle, such as 434061839_AR. Invoices and statuses addressed to an entry are delivered to the platform that registered it, so the two flows never conflict and act fully independently.
Yes. Keep the existing Invopop registration for sending, and have the other PA register a new SIREN_suffix electronic address in the Annuaire and Peppol for receiving, such as 434061839_AP. The supplier then gives that address to their own suppliers.Electronic addresses work like email addresses:
  • Invoices arrive at whichever address the sender uses, and are delivered to the PA that registered it.
  • Invoices you send from an address get their lifecycle status updates back at that same address.
Invoices sent to the Invopop-registered address still reach Invopop, so make sure suppliers switch to the new one.
Yes. Copy the PPF register supplier template and remove the Register party for reporting step. The party gets its Annuaire line and Peppol inbox and can receive invoices, but no reporting cadence starts. When its obligations begin, run the removed step against the party to complete the registration. See Registering without e-reporting.
None at the supplier level. The Plateforme Agréée holds an OpenPeppol-issued mTLS certificate (Invopop’s), and the PA-to-PPF channel uses additional DGFiP credentials managed by Invopop.
This error means the PPF has not yet referenced the SIREN in the annuaire de la facturation électronique. Before an accredited platform like Invopop can register a directory entry, the PPF has to list the SIREN first — even if the company is correctly registered and active with the tax administration, there may still be no directory entry for a PA to take over.The fix has to come from the tax administration, not from Invopop:
  1. Confirm the business is in scope for the reform using the PPF’s questionnaire.
  2. If it’s in scope but still missing from the directory, have the business or its accountant contact the Service des Impôts des Entreprises (SIE) that handles it and ask for the SIREN to be referenced in the annuaire.
  3. For general questions about the reform, the DGFiP runs a free national helpline: 0 806 807 807.
Invopop has no way to create the directory entry directly — only the SIE can. Once the supplier confirms the SIREN is referenced, re-run the registration workflow.
The party’s peppol inbox code has three parts, such as 526018155_52601815500012_AP. In the Annuaire, an address with a third part carries a routing code (code routage), which Invopop doesn’t support.Use one of the supported forms instead: SIREN, SIREN_SIRET, or SIREN_suffix. If you need an address of your own alongside the company’s other addresses, for example because you only issue invoices on its behalf, register a dedicated SIREN_suffix such as 526018155_PLATFORMNAME. See Choosing the electronic address.
It depends on the flows the merchant uses:
  • E-invoicing (B2B) — 150 pops per merchant: 50 pops for the French directory (Annuaire) registration plus 100 pops for Peppol.
  • E-reporting only (B2C or international B2B) — 50 pops per merchant to register the party for reporting.
Each registered merchant counts as a seat: the same seat pops are deducted on registration and again every 30 days for as long as the merchant stays registered — see Pops & pricing for how seats are billed.
Upload the company as a party (Console → Parties → Suppliers → + New Supplier, or via the Create an Entry API) with name, tax_id, address, and email. Then run it through the party registration workflow — the contact will receive a registration wizard link to provide proof of ownership.Once approved, the party is registered on the Peppol network (SMP+SML+Peppol visibility by default with the ubl-invoice doc group) and ready to receive invoices.
A supplier with that Participant ID already exists in your workspace. Either reuse the existing party or, if it really is a new entity, check whether it should be registered under an alternative scheme (for example Belgium’s 9925 VAT scheme rather than the default 0208).
Register them through different silo entries, even though they represent the same legal party. The supplier must upload proof of ownership for each inbox.
Unique identifiers for entities on the Peppol network, made up of two parts:
  • Scheme — identifies the type of identifier (e.g. 9920 for Spanish VAT, 0208 for Belgian KBO/BCE)
  • Code — the actual identification number
Participant IDs are usually based on VAT numbers or local business identifiers, and Invopop can derive them automatically from a Tax ID. Some countries support multiple schemes — Belgium, for example, defaults to 0208 but some entities are only registered under 9925 (VAT). If you hit a “receiver not found” error, the recipient may be registered under an alternative scheme.
Peppol Party visibility determines what you can send and receive:
  • smp — SMP only, for testing
  • smp+sml — SMP and SML, useful when you only want to send
  • smp+sml+peppol — SMP, SML, and the Peppol Directory, recommended for both sending and receiving (and for being discoverable in the Directory)
In general, use the highest visibility available.
More available in our France FAQ section