> ## Documentation Index
> Fetch the complete documentation index at: https://invopop-auto-sync-workflow-templates.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# SIREN registration in France

> Register a party in the French Annuaire and on the Peppol network.

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.

| -                | Sandbox                                                                                       | Live                                                                    |
| ---------------- | --------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- |
| **Supplier**     | Use a checksum valid [generated SIREN](https://www.onsubmit.io/french-siret-siren-generator/) | Requires a valid SIREN and the signature of the company representative. |
| **Approval**     | Automatic                                                                                     | Automatic, but can be flagged for human review                          |
| **Registration** | Peppol SMK  and PPF's *environnement de qualification*                                        | Peppol SML and Annuaire production                                      |

<Accordion title="French supplier" defaultOpen="true">
  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` and passport/document id number.
  * The `peppol` inbox uses scheme `0225` (French CTC electronic address) with the SIREN as the code.
    * If no inbox is specified, the Register for Peppol step will assign one based on the supplier's SIREN.

  ```json France supplier example expandable theme={"system"}
  {
      "$schema": "https://gobl.org/draft-0/org/party",
      "name": "Marseille Commerce SAS",
      "tax_id": {
          "country": "FR",
          "code": "83526018155"
      },
      "identities": [
          {
              "type": "SIREN",
              "code": "526018155",
              "ext": {
                  "iso-scheme-id": "0002"
              }
          }
      ],
      "people": [
          {
              "name": {
                  "given": "Claire",
                  "surname": "Moreau"
              },
              "role": "Directrice",
              "identities": [{
                  "label": "Passport/document number",
                  "code": "123456"
              }]
          }
      ],
      "inboxes": [
          {
              "key": "peppol",
              "scheme": "0225",
              "code": "526018155"
          }
      ],
      "addresses": [
          {
              "num": "25",
              "street": "Avenue des Champs-Élysées",
              "locality": "Paris",
              "code": "75008",
              "country": "FR"
          }
      ],
      "emails": [
          {
              "addr": "facturation@marseillecommerce.fr"
          }
      ],
      "telephones": [
          {
              "num": "+33100200300"
          }
      ]
  }
  ```
</Accordion>

## PPF register supplier workflow

<Card iconType="duotone" title="PPF register supplier" icon="code-branch" href="https://console.invopop.com/redirect/workflows/new?template=fr-fr-pa-register" horizontal>
  Add to my workspace →
</Card>

<Tabs>
  <Tab title="Image">
    <Frame>
      <img src="https://mintcdn.com/invopop-auto-sync-workflow-templates/uPBpb_tL-P0Ii6aJ/assets/guides/fr-register.png?fit=max&auto=format&n=uPBpb_tL-P0Ii6aJ&q=85&s=919d093252cb773b715ed3f00437becc" width="650" data-path="assets/guides/fr-register.png" />
    </Frame>
  </Tab>

  <Tab title="JSON">
    ```json PPF register supplier workflow theme={"system"}
    {
        "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"
                }
            }
        ]
    }
    ```
  </Tab>
</Tabs>

## 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](#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.

<Accordion title="Example approval-link meta entry">
  ```json theme={"system"}
  {
    "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
  }
  ```
</Accordion>

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:

<Steps>
  <Step title="Party details">
    Review and confirm the pre-filled company and signer information.
  </Step>

  <Step title="Identity document">
    Upload a photo of the signer's ID card (front and back) or passport page.
  </Step>

  <Step title="Sign mandate">
    Sign the pre-filled mandate directly in the browser, or upload a pre-signed PDF.
  </Step>

  <Step title="Confirm">
    Submit for Invopop review. The party status moves to `submitted` until a decision is made.
  </Step>
</Steps>

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

<Tabs>
  <Tab title="In-app signing">
    The customer signs the mandate directly. Invopop stamps the signature and verifies identity.

    <Steps>
      <Step title="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.
      </Step>

      <Step title="Upload identity document">
        `POST /identity` uploads one face at a time: `front` + `back` for an ID card, or `page` for a passport.
      </Step>

      <Step title="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.
      </Step>

      <Step title="Confirm">
        `POST /confirm` finalises the submission and returns a `status` field. `submitted` means the party is under approval review before registration continues.
      </Step>
    </Steps>
  </Tab>

  <Tab title="Pre-signed PDF">
    The customer signs the mandate externally and uploads the result.

    <Steps>
      <Step title="Download mandate">
        `GET /agreement` returns the pre-filled mandate PDF for the customer to sign externally.
      </Step>

      <Step title="Upload identity document">
        `POST /identity` uploads one face at a time: `front` + `back` for an ID card, or `page` for a passport.
      </Step>

      <Step title="Upload signed PDF">
        `POST /agreement` stores the signed PDF (≤ 4 MB).
      </Step>

      <Step title="Confirm">
        `POST /confirm` finalises the submission and returns a `status` field. `submitted` means the party is under approval review before registration continues.
      </Step>
    </Steps>
  </Tab>
</Tabs>

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

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

## PPF unregister supplier workflow

<Card iconType="duotone" title="PPF unregister supplier" icon="code-branch" href="https://console.invopop.com/redirect/workflows/new?template=fr-fr-pa-unregister" horizontal>
  Add to my workspace →
</Card>

<Tabs>
  <Tab title="Image">
    <Frame>
      <img src="https://mintcdn.com/invopop-auto-sync-workflow-templates/uPBpb_tL-P0Ii6aJ/assets/guides/fr-unregister.png?fit=max&auto=format&n=uPBpb_tL-P0Ii6aJ&q=85&s=1cac46a2c6382efd27a1f03d956cb50d" width="650" data-path="assets/guides/fr-unregister.png" />
    </Frame>
  </Tab>

  <Tab title="JSON">
    ```json PPF unregister supplier workflow theme={"system"}
    {
        "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"
                }
            }
        ]
    }
    ```
  </Tab>
</Tabs>

## FAQ

<AccordionGroup>
  <Accordion title="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.
  </Accordion>

  <Accordion title="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.
  </Accordion>

  <Accordion title="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.
  </Accordion>

  <Accordion title="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.
  </Accordion>

  <Accordion title="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.
  </Accordion>

  <Accordion title="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`).
  </Accordion>

  <Accordion title="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.
  </Accordion>

  <Accordion title="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.
  </Accordion>

  <Accordion title="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.
  </Accordion>
</AccordionGroup>

More available in our [France FAQ](/faq/france) section

***

<AccordionGroup>
  <Accordion title="🇫🇷 Invopop resources for France">
    |            |                                                                                                                                                                                                                                                                                                                                                                                       |
    | ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
    | Compliance | <Icon icon="https://assets.invopop.com/flags/fr.svg" /> [Invoicing compliance in France](/compliance/france)<br /> <Icon icon="timeline" /> [Compliance timeline](/timelines/france)                                                                                                                                                                                                  |
    | Apps       | <Icon icon="https://assets.invopop.com/flags/fr.svg" /> [France](/apps/france)<br /><Icon icon="https://assets.invopop.com/apps/peppol/icon.svg" /> [Peppol](/apps/peppol)<br /><Icon icon="https://assets.invopop.com/apps/chroruspro/icon.svg" /> [Chorus Pro France](/apps/choruspro-france)                                                                                       |
    | Guides     | <Icon icon="book" /> Chorus Pro — [Supplier registration](/guides/fr-chorus-pro-supplier) · [Issuing invoices](/guides/fr-chorus-pro)<br /><Icon icon="book" /> [PA Guide](/guides/fr-pa) — [Registration](/guides/fr-pa-registration) · [Invoicing](/guides/fr-pa-invoicing) · [Status](/guides/fr-pa-status) · [Reporting](/guides/fr-pa-reporting)                                 |
    | FAQ        | <Icon icon="square-question" /> [France FAQ](/faq/france)                                                                                                                                                                                                                                                                                                                             |
    | GOBL       | <Icon icon="https://assets.invopop.com/icons/gobl.svg" />  [France Tax Regime](https://docs.gobl.org/regimes/fr)<br /> <Icon icon="https://assets.invopop.com/icons/gobl.svg" /> [Chorus Pro Addon](https://docs.gobl.org/addons/fr-choruspro-v1)<br /> <Icon icon="https://assets.invopop.com/icons/gobl.svg" /> [French Factur-X Addon](https://docs.gobl.org/addons/fr-facturx-v1) |
    | GitHub     | <Icon icon="github" /> [gobl.xinvoice](https://github.com/invopop/gobl.xinvoice)                                                                                                                                                                                                                                                                                                      |
  </Accordion>
</AccordionGroup>