Set up account for France

Review France-specific requirements and considerations for each step of the account setup process.

Important:

Only workspace administrators can create organizations.

Account setup for France follows the same process as other countries in Compliance Network.

Before you begin

Make sure that you do the following tasks:

Assign France e-invoicing products to your company in the Compliance Services UI. See Manage products.
Register your company and verified its SIREN is active with INSEE (https://www.insee.fr/).
Collect SIREN numbers, if the customer has multiple physical locations. You use these numbers during endpoint configuration, not at this stage.
Register your French VAT and verify it is active. Verify at https://www.impots.gouv.fr/ or the EU VIES system at https://ec.europa.eu/taxation_customs/vies/. The VAT number is not required as a platform field — the SIREN is the mandatory identifier in Sovos. Confirming active VAT registration is a regulatory prerequisite.
If you plan to use legal archiving, you must also assign the Legal Archive product(s) to your organization and company. Assigning France e-invoicing or e-reporting products does not activate legal archiving. See Legal archiving for steps.
Review the setup sequence described in the following sections.

Note:

If you see a "No product assigned to organization" error, contact your account manager or organization administrator to add the product.

Implementation coordination

France setup needs two different roles that don't always work together day-to-day:

Your business analyst who knows the tax details, legal entities, and business rules.
Your API specialist who turns those details into working configuration.

Ensure they communicate regularly. This table shows who owns each step, who provides input, and where to hand off between teams.


Step	Business analyst (BA)	API specialist	Handoff note
Create an organization	Decides which products to assign	Creates the organization and assigns products	BA confirms product scope before API specialist starts.
Add companies	Provides the SIREN and VAT number for each legal entity	Enters those values into the portal or API	BA must supply the exact SIREN and VAT number first. Both fields lock after saving and can't be changed.
Create ERP System IDs	Confirms the notification method (polling or push)	Creates the ERP System ID and sets the communication method	BA confirms method first. API specialist handles the technical setup.
Create company endpoints	Provides the SIRET for each location	Calls the endpoint API using the SIRET values BA provided	Each company needs two endpoints: outbound and inbound. BA provides one SIRET per location.
Add users	Identifies who needs access and at what level	Creates user accounts and assigns roles	BA provides the list of users and their access levels.

Tip:

Before the API specialist opens the portal, the business analyst should have the SIREN, VAT number, SIRET numbers, and product scope confirmed and written down. Most setup blockers happen when these values aren't ready at the moment they're needed.

Legal archiving requires a separate product assignment at both the organization and company levels. Complete this after the core e-invoicing setup is done.

Set up account sequence

Set up your account in this order:

Create an organization.
Assign products.
Add companies (one per tax ID).
Add branches (optional).
Add users and assign roles.

Note: You can also edit a company

Create an organization

Create an organization and assign the France products your companies will use.

Assign all products the customer will use at the organization level. Companies created under the organization inherit these products by default.

Tip:

This step applies to partners who manage their own Sovos workspace. If you're a direct customer, your organization is already set up. Go to Add companies to continue.

Before you begin

Keep the following in mind:

In France, each company represents one legal entity identified by its SIREN.
Create one company per SIREN, regardless of how many physical locations the customer operates.
The France Compliance Network configuration can live in the same workspace as the Belgium configuration.

France account setup specifics

France account setup follows the same process as other countries, with these differences:

Assign France-specific product IDs for your account.
Replace each company's tax ID with the company's SIREN.
Create ERP System IDs instead of branches.

Product IDs


Product ID	Description	Who needs it
`fr_invoice_inbound_1.0`	Receiving invoices as buyer	All customers, required to receive invoices
`fr_invoice_outbound_1.0`	Issuing invoices as supplier	Customers who also send invoices
`fr_Report__1.0`	E-reporting (B2C, cross-border, and out-of-scope transactions)	Customers who have B2C sales, cross-border transactions, or other out-of-scope transactions to report
`fr_archiving_inbound_1.0`	Archiving inbound invoices as buyer	Customers who are required to archive received invoices for legal compliance
`fr_archiving_outbound_1.0`	Archiving outbound invoices as supplier	Customers who are required to archive issued invoices for legal compliance

Set up in Compliance Network

You must have workspace administrator permissions to create an organization.

Click the Settings icon.
Go to Organization on the navigation menu.
Click Create organization.
Enter the organization name and a brief description.
Click Save.

Set up using API

You need workspace administrator permissions to create an organization.

Send a POST request to /v2/configurations/organizations.
In the request body, include the name field with your organization name.
Request body:
```
{
  "name": "{organization-name}"
}
```
Important:
name is a required field. It can't be empty. No character limit.
Confirm the response returns a 200 status and an organization ID.
Response body:
```
{
  "id": "{organization-id}",
  "name": "{organization-name}",
  "createdAt": "{timestamp}",
  "createdBy": "{user-email}",
  "isDeleted": false
}
```
Important:
If you get a 400 or 409 HTTP status code, make sure you have entered a unique organization name.
Save the id value from the response. You need this for all subsequent API calls.

Add companies to your organization

Add companies to your organization to represent each of your legal entities and manage their configuration and access separately.

Before you begin

Make sure you've done the following:

Created company endpoints.
Created an organization. See Create an organization.

Companies as legal entities

Companies represent legal entities with their own tax ID. You can manage each company independently, and each company allows you to:

Set up separate configuration per tax ID.
Restrict user access per specific tax IDs.
Organize transactional data by legal entity.

You can add a company to your organization using the SIREN in Compliance Network (for manual setup) or using the Indirect Tax API (for automated workflows).

Key concepts

Tax ID: SIREN

The portal labels this tax ID. In the API, it maps to taxId. For France, each company represents one legal entity identified by its SIREN . Create one company per SIREN , regardless of how many physical locations the customer operates.

Enter the SIREN in the tax ID field (taxId). This is the nine-digit legal identifier that the Institut National de la Statistique et des Études Économiques (INSEE) assigns when a business registers in France.


Property	Detail
Format	Nine digits, no separators
Example	`123456789`
Validation	Luhn algorithm checksum on the ninth digit
Where to verify	https://www.insee.fr/
Country code prefix	Don't include it. Enter nine digits only, no `FR` prefix

The platform validates the SIREN format on submission, not SIRET. Do not use SIRET as the company tax ID. Use SIRET for establishment-level address configuration during endpoint setup, not here.

Note:

SIRET is the 14-digits establishment identifier made up of SIREN plus a five-digit location code (NIC).

VAT registration

VAT number format: FR + two check digits + nine-digit SIREN (example: FR12345678901). Confirm the customer's VAT registration is active before proceeding. See the details in Set up account for France.

The international VAT number is optional in both e-invoicing and e-reporting submissions. SIREN is the mandatory company identifier on the Sovos platform. If you plan to include the VAT number in submitted documents, configure it in the international VAT ID field during the company setup before submitting. If the field is not configured but the value is present in the document, Compliance Network may not match the record correctly.

Important:

After you create the company, the system locks the Tax ID and the International Tax ID fields. You can't edit them later. Double-check both values before you save.

Multiple locations

If a customer has multiple physical locations (establishments), they still have one SIREN and one company record. Each establishment has its own SIRET, a 14-digit identifier made up of SIREN (digits one through nine) plus a five-digit establishment code (NIC).

No more setup is needed at this stage for multi-location customers. SIRET-based address configuration happens during endpoint setup. See Network and endpoint configuration.

ERP System ID

Leave this field empty at this step. In the France workflow, you set up the ERP system after creating the company. See Create an ERP System ID in Compliance Network for the correct sequence.

Adding companies sequence in France

When following the France setup guide, you create the company before the ERP system ID exists. Compliance Network generates the ERP system ID later, after you set up the ERP system in Compliance Services (Delta).

Don't include an ERP System ID in the Create Company payload at this stage. Leave the field empty or omit it entirely.

The correct sequence is:

Add the company (this step).
Set up the ERP system in Compliance Services (Delta): go to Settings > Organization Settings > Compliance > ERP System.
After the ERP system is set up, update the company record with the ERP System ID if needed.

Set up using Compliance Network

Click the Settings icon.
Go to Organizations on the navigation menu.
Select an organization's name under the Name column.
Go to Companies.
Select New company.
Enter the company details and company address, then Save.

Set up using API

Use the API to add a company to your organization by providing its tax registration details and assigned products.

Send a POST request to /v2/configurations/organizations/{organizationId}/companies.

In the request body, include the following required fields for your company:

Request body:


                    
                {
  "taxId": "{tax-id}",
  "legalName": "{legal-entity-name}",
  "dba": "{business-name}",
  "products": [
    {
      "productId": "{product-id}",
      "allowedProcessTypes": {
        "inbound": false,
        "outbound": true
      }
    }
  ]
}

Check the complete list of parameters:


Parameter	Type	Required	Description
`taxId`	string	Yes	Tax registration number of your company's tax ID. Validates for country-specific format
`legalName`	string	Yes	Official legal entity name. It can't be empty
`dba`	string	Yes	"Doing Business As" registered name. It can't be empty
`products`	array of strings	Yes	Array of products with process types
`country`	string	No	Country code (ISO 3166-1 alpha-2, for example: "FR", "PL")

Note:

If the products list is left empty, the created company will acquire all the products assigned to the organization.

Confirm the response returns a 200 status.

Response body:


                {
  "id": "{company-id}",
  "taxId": "{tax-id}",
  "legalName": "{legal-entity-name}",
  "dba": "{business-name}",
  "country": "{country-code}",
  "products": [...],
  "createdAt": "{timestamp}",
  "isDeleted": false
}

Save the id (company ID) for future API calls.

After successfully adding a company, the Indirect Tax API returns a JSON object containing the company details and their assigned company ID.

Note:

Always save the company ID value from the response when creating a company. You will need the company ID value in future API calls. To find it, look for the ID value in the samples.

Create ERP System IDs

ERP System IDs identify each connected system for diagnostics and analytics, and define the communication method (push or pull) for API notifications. To create an ERP System ID, go to ERP Setup in Compliance Network.

All France accounts need at least one ERP System ID for receiving documents from the network. If the customer also has e-reporting obligations, create a second ERP System ID for that purpose. See France e-reporting for details on e-reporting scope and setup.

Important:

You must fully set up the ERP system in Compliance Services before you set up communication in Network Services. If you go to Network Services first, the ERP system does not appear and you cannot set up communication. The UI gives no error and shows an empty list.

The platform automatically creates default ERP System IDs when you provision a new organization, but these are not synchronized to Network Services and cannot be used for network endpoint configuration. Create new ERP System IDs manually

Create an ERP System ID in Compliance Network

Go to ERP Setup in the left sidebar.
Click New System Notification.
Enter an ERP System ID.
Use a name that clearly identifies the customer and purpose (for example, CustomerName_FR_Invoicing).
Set Communication Method.
- Polling — the customer's system polls Sovos for new notifications.
- Pushing V2 (Svix) — Sovos pushes notifications to the customer's system through a webhook. Do not select Pushing (Deprecated).
Important:
For France, always select Pull as the delivery method in Network Services. When Pull is selected, Network Services passes document processing notifications into Compliance Services, which then delivers them to your system using the communication method you configured in Step 1 (Polling or Pushing V2). Do not select Push for France.
Network Services and Compliance Services each have a separate configuration that work together to route notifications to your system:
Network Services delivery method (Pull):
Set in ERP System Communications in Network Services. Pull means Network Services passes notifications into Compliance Services.
Compliance Services communication method (Polling/Pushing V2):
Set in ERP Setup in Compliance Services. Controls how Compliance Services delivers those notifications to your system — either your system polls the Notifications API (Polling), or Sovos pushes them to your webhook endpoint (Pushing V2).
For more information, see ERP system communication types.
Leave Event Mapping empty.
Don't add events for the e-invoicing ERP System ID. The network handles all routing for network countries.
Click Save.

The ERP System ID is now available for use in endpoint configuration.

Set up ERP system communication in Network Services

Before you begin, make sure you have created an ERP System ID in Compliance Services. The ERP system must exist in Compliance Services before it appears in Network Services. See Create an ERP System ID in Compliance Network.

Log in to the Network Services UI.
Go to your organization and open ERP System Communications.
Select the ERP system you created in Create an ERP System ID in Compliance Network.
It now appears in the list.
Note:
If the ERP system does not appear, confirm it was saved in Compliance Services and refresh the page.
Set the Type to Invoice or Lifecycle, depending on the notification type you are configuring.
Set the Delivery method:
Pull
Network Services passes document processing notifications into Compliance Services, which then delivers them to your system using the communication method you set in Step 1 (Polling or Pushing V2). For France, always select Pull.
Push
Do not select Push for France implementations.
Important:
For France, always select Pull as the delivery method. Do not select Push for France.
Select the plugin for this communication format.
Click Save.
Note:
This step always uses the Network Services UI. There is no API path for setting up ERP system communication in Network Services.

ERP system communication types

ERP system communication for France involves the delivery method in Network Services and the communication method in Compliance Services. Both settings work together to route document processing notifications from the network to your system.

Network Services: Delivery method

The delivery method is set in ERP System Communications in Network Services. It controls how Network Services routes document processing notifications after it processes a document.


Option	Behavior
Pull	Network Services passes notifications into Compliance Services. Compliance Services then delivers them to your system using the communication method you configured in ERP Setup (Polling or Pushing V2).

Important:

For France, always select Pull as the delivery method. Do not select Push for France.

Compliance Services: Communication method

The communication method is set in ERP Setup in Compliance Services. It controls how Compliance Services delivers notifications to your system after receiving them from Network Services.


Option	Behavior
Polling	Your system polls the Notifications API at intervals to retrieve notifications.
Pushing V2 (Svix)	Sovos pushes notifications to your system using a webhook. When you select this option, a webhook URL is registered on the Compliance Services side. Sovos recommends enabling both AutoAcknowledge and ApplicationResponse as link options when using Pushing V2.

Note:

Do not select Pushing (Deprecated). This option is no longer supported.

For more information on asynchronous communication setup, which applies to both Polling and Pushing V2, see Synchronous and asynchronous transactions.

For more information on setting up webhooks for Pushing V2, see Using webhooks for event notifications.

How the two settings work together

When you set the Network Services delivery method to Pull and the Compliance Services communication method to Polling or Pushing V2, the full notification path works as follows:

Network Services processes a document and generates a notification.
Network Services passes the notification into Compliance Services (because delivery method = Pull).
Compliance Services delivers the notification to your system using whichever method you configured. Either your system polls for it (Polling) or Sovos pushes it to your webhook endpoint (Pushing V2).

Add people and assign roles

France has no specific role requirements for user management.

User management is the same across all countries. There are no France-specific role requirements.

How can we help?

Set up account for France

Before you begin

Implementation coordination

Set up account sequence

Create an organization

Before you begin

France account setup specifics

Product IDs

Set up in Compliance Network

Set up using API

Add companies to your organization

Before you begin

Companies as legal entities

Key concepts

Adding companies sequence in France

Set up using Compliance Network

Set up using API

Create ERP System IDs

Create an ERP System ID in Compliance Network

Set up ERP system communication in Network Services

ERP system communication types

How the two settings work together

Add people and assign roles

sovos-footer