Skip to main content

Documentation Index

Fetch the complete documentation index at: https://invopop-mintlify-changelog-week-1778411791.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

Registration is required for any French SIREN that will issue, receive, or report transactions through Invopop as its Plateforme Agréée. Registration is a prerequisite for all flows: invoicing, status, and reporting.
Each party (a SIREN) is registered once. The workflow signs the contract, records the party in the Annuaire, opens a reporting register, and publishes the party on the Peppol network. After it completes, the party can both send and receive invoices and is ready to start recording transactions for reporting. The Annuaire requires every entry to be receive-capable, so there is no send-only option as in other Peppol countries. Internally, the workflow extends the standard Peppol registration with a French Annuaire step and the reporting register.

How it works

1

Sign Contract

Kicks off the contract signature flow with the party. The job pauses here until the party returns the signed agreement.
2

Set State → processing

Moves the silo entry into a visible “in progress” state so operator dashboards reflect that registration is underway.
3

Wait for Approval

Pauses until Invopop’s KYC review of the signed contract clears.
4

Register in Annuaire

Submits the party’s SIREN to the French national directory so other PAs can route invoices to it.
5

Register Reporter

Opens a reporting record keyed by SIREN and stores the cadence chosen during onboarding. See reporting for the cadence options.
6

Register Peppol Party

Publishes the party in SMP/SML with the france document group, enabling Peppol-level routing for sending and receiving.
7

Set State → registered

Marks the party as fully onboarded.

Workflow code

France PA register party workflow

Registers a party in the Annuaire, on the Peppol network, and as a reporter.

Unregistration

Our unregistration workflow will be available soon
When a party stops trading or moves to another platform, run an unregistration workflow. The workflow steps remove the party from the Annuaire, Peppol and close out its reporting register.
1

Unregister in Annuaire

Removes the inbox from the French directory.
2

Disable Reporter

Closes the reporting register so no more periodic reports are generated for this SIREN.
3

Unregister in Peppol

disables the party on Peppol so no further invoices are routed to it.
Unregistering does not delete historical reports already submitted to the PPF.

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.
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.
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