France PA — registration

Registration is required for any French SIREN that will issue or receive invoices through Invopop as its Plateforme Agréée. It is a prerequisite for the invoicing and status flows.

Each party (a SIREN) is registered once. The workflow collects a signed agreement, registers the party in the French Annuaire, and publishes it on the Peppol network. After it completes, the party can both send and receive invoices. 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 French-specific steps (gov-fr.directory.register) before the Peppol registration.

How it works

Sign PPF agreement

Generates the French PA mandate so the party can authorise Invopop to act on its behalf (gov-fr.agreement.sign).

Set state → processing

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

Wait for PPF agreement upload

Pauses until the signed agreement is uploaded and accepted (gov-fr.agreement.wait.approval).

Set state → completed

Marks the agreement step as completed before the directory and Peppol registrations run.

Submits the party’s SIREN to the French Annuaire so other PAs can route invoices to it (gov-fr.directory.register).

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

Set state → registered

Marks the party as fully onboarded.

Template
Code

France PA register party workflow

Registers a party in the Annuaire and on the Peppol network for sending and receiving invoices.

Copy and paste into a new Empty Party workflow.

PPF register supplier workflow

{
    "name": "PPF register supplier",
    "description": "Register a supplier with the French Directory and Peppol",
    "schema": "org/party",
    "steps": [
        {
            "id": "0adf46e0-8fdb-11f0-a8fb-61ec9e5a76ba",
            "name": "Sign PPF agreement",
            "provider": "gov-fr.agreement.sign",
            "notes": "Generates the PA mandate to authorize Invopop to act on behalf of the supplier"
        },
        {
            "id": "0e44b900-8fdb-11f0-a8fb-61ec9e5a76ba",
            "name": "Set state",
            "provider": "silo.state",
            "summary": "Set state to `processing`{.state .processing}",
            "config": {
                "state": "processing"
            }
        },
        {
            "id": "12aaf950-8fdb-11f0-a8fb-61ec9e5a76ba",
            "name": "Wait for PPF agreement upload",
            "provider": "gov-fr.agreement.wait.approval",
            "notes": "Pauses until the signed agreement is uploaded and accepted"
        },
        {
            "id": "b194f710-5451-11f1-baf5-4f2c2882107f",
            "name": "Set state",
            "provider": "silo.state",
            "summary": "Set state to `completed`{.state .completed}",
            "config": {
                "state": "completed"
            }
        },
        {
            "id": "d10a4680-1e29-11f1-8bfb-2beaa1df60f0",
            "name": "Register party in Directory",
            "provider": "gov-fr.directory.register",
            "notes": "Submits the SIREN to the French Annuaire for invoice routing"
        },
        {
            "id": "7a5a4db0-0fae-11f0-b37b-0be1c251a274",
            "name": "Register party on Peppol",
            "provider": "peppol.register",
            "summary": "Enabled · groups: france",
            "config": {
                "directory": true,
                "disable": false,
                "doc_groups": [
                    "france"
                ],
                "visibility": "smp+sml+peppol"
            },
            "notes": "Publishes the party, enabling Peppol routing for sending and receiving"
        },
        {
            "id": "b523ae4a-7b39-4410-abaa-b03a4e33f7bd",
            "name": "Register party for reporting",
            "provider": "gov-fr.reporting.register",
            "notes": "Registers the SIREN for reporting"
        },
        {
            "id": "7c2fa9f0-0fae-11f0-b37b-0be1c251a274",
            "name": "Set state",
            "provider": "silo.state",
            "summary": "Set state to `registered`{.state .registered}",
            "config": {
                "state": "registered"
            }
        }
    ],
    "rescue": [
        {
            "id": "a34e83f0-25dc-11f0-b641-350e77c28eed",
            "name": "Set state",
            "provider": "silo.state",
            "summary": "Set state to `error`{.state .error}",
            "config": {
                "state": "error"
            }
        }
    ]
}

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

Example approval-link meta entry

{
  "src": "gov-fr",
  "key": "approval-link",
  "ref": "EgDeG3pDBDe",
  "link_url": "https://gouv-fr.invopop.com/reg/EgDeG3pDBDe/start",
  "link_scope": "public",
  "indexed": true,
  "shared": true
}

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:

Party details

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

Identity document

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

Sign mandate

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

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.

In-app signing
Pre-signed PDF

The customer signs the mandate directly. Invopop stamps the signature and verifies identity.

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.

Upload identity document

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

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.

Confirm

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

The customer signs the mandate externally and uploads the result.

Download mandate

GET /agreement returns the pre-filled mandate PDF for the customer to sign externally.

Upload identity document

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

Upload signed PDF

POST /agreement stores the signed PDF (≤ 4 MB).

Confirm

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

Taking over a line from another Plateforme Agréée

If a SIREN’s Annuaire line is already held by another Plateforme Agréée (PA), registration takes that line over instead of creating a duplicate. To do so, the party must specify the former PA line under fr-former-matricule meta key. This will add an additional section in the signed agreement that asks for consent to take over the line.

If a takeover is required and the matricule is missing, registration fails and asks for it.

Unregistration

Run the unregister workflow to revoke a party’s registrations when it should no longer issue or receive invoices through Invopop.

Unregister Peppol Party

Disables the party in SMP/SML so Peppol traffic no longer routes to it.

Unregister from Directory

Removes the party from the French Annuaire.

Set state → void

Marks the party as unregistered.

Template
Code

France PA unregister party workflow

Revokes Peppol and Annuaire registrations so the party can no longer issue or receive invoices.

Copy and paste into a new Empty Party workflow.

PPF unregister supplier workflow

{
    "name": "PPF unregister supplier",
    "description": "Unregister a supplier from Peppol and the French Directory",
    "schema": "org/party",
    "steps": [
        {
            "id": "453beac0-70a7-11f1-aca9-697108ec55ef",
            "name": "Unregister supplier from Peppol",
            "provider": "peppol.unregister"
        },
        {
            "id": "13c84e60-5452-11f1-baf5-4f2c2882107f",
            "name": "Disable party in Directory",
            "provider": "gov-fr.directory.disable"
        },
        {
            "id": "c91ae086-f830-425b-b67c-72af00efc22c",
            "name": "Disable party for reporting",
            "provider": "gov-fr.reporting.disable"
        },
        {
            "id": "1b8a6b80-5452-11f1-baf5-4f2c2882107f",
            "name": "Set state",
            "provider": "silo.state",
            "summary": "Set state to `void`{.state .void}",
            "config": {
                "state": "void"
            }
        }
    ],
    "rescue": [
        {
            "id": "23e0d3a0-5452-11f1-baf5-4f2c2882107f",
            "name": "Set state",
            "provider": "silo.state",
            "summary": "Set state to `error`{.state .error}",
            "config": {
                "state": "error"
            }
        }
    ]
}

Unregistering does not delete historical data already submitted to the PPF.

FAQ

How do I onboard a new supplier in France?

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.

How are supplier credentials stored in Invopop for France?

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.

How do I register a supplier with France PA?

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.

What certificates does France PA require to authenticate a supplier?

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.

How do I register for a Peppol inbox in 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.

I get 'XXXX:XXXXXXXXX is already registered' when registering a supplier — what now?

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

How do I assign multiple inboxes to a single supplier?

Register them through different silo entries, even though they represent the same legal party. The supplier must upload proof of ownership for each inbox.

What are Participant IDs?

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.

What visibility level should I set on my Peppol Party?

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

🇫🇷 Invopop resources for France


Compliance	Invoicing compliance in France Compliance timeline
Apps	France Peppol ChorusPro France
Guides	ChorusPro Guide PA Guide — Registration · Invoicing · Status · Reporting
FAQ	France FAQ
GOBL	France Tax Regime Chorus Pro Addon French Factur-X Addon
GitHub	gobl.xinvoice

Networks

Countries

Set-up

GOBL

Apps

API

Features

France PA — registration

How it works

France PA register party workflow

Agreement signing

Registration wizard

Entry API

Taking over a line from another Plateforme Agréée

Unregistration

France PA unregister party workflow

FAQ

​How it works

France PA register party workflow

​Agreement signing

​Registration wizard

​Entry API

​Taking over a line from another Plateforme Agréée

​Unregistration

France PA unregister party workflow

​FAQ

How it works

Agreement signing

Registration wizard

Entry API

Taking over a line from another Plateforme Agréée

Unregistration

FAQ