The Annuaire

The Annuaire is the central directory of invoice recipients, managed by the French tax authority's public portal (PPF). When a supplier wants to send an invoice, their platform looks up the buyer's SIREN in the Annuaire to find which certified platform to route it through.

Every VAT-registered French company already exists in the Annuaire. Creating the inbound endpoint in Compliance Network claims the customer's Annuaire entry and activates them as a reachable invoice recipient.

Inbound compared to outbound

Address format options

Questions to ask the customer before proceeding

• Does your accounts payable team handle invoices centrally, or do different sites or departments need separate invoice streams?

• Do you self-bill (issue invoices on behalf of your suppliers)? If so, do you want a dedicated address for those, separate from purchase invoices?

• Are you planning to use more than one invoicing platform? If yes, they need a separate address per platform. A single address can only be assigned to one platform at a time.

For most private sector customers, the answer to all three questions leads to SIREN. Recommend the SUFFIXE variant only when the customer has a clear, specific reason for multiple addresses.

Before you begin

• ERP System Communications must be configured for this organization. See ERP System Communications.

• The France e-invoicing product must be assigned to the company. See Set up account for France.

Create an outbound endpoint in Compliance Network

Follow the same steps as for the inbound endpoint with these differences.

• Step 4: Select fr_invoice_outbound_1.0.

• Step 7: Set the validity start date. Use at least the following day (J+1). Same-day dates are not accepted in production.

• Step 8: Skip the Invoices tab. Outbound does not use Invoice or CreditNote subtypes.

• Step 9: Configure lifecycles only.

Create an outbound endpoint through the API

The request follows the same structure as the inbound endpoint. Change only productId and supportedDocuments.

"productId": "fr_invoice_outbound_1.0",
"supportedDocuments": [
  {
    "type": "Lifecycle",
    "subTypes": ["Lifecycle"]
  }
]

Set validityPeriod.start to at least the following day. All other fields (codeComponents, erpSystemId, headers, and URL) are identical to the inbound request.

Successful response

{
  "status": 201,
  "message": "Created",
  "success": true,
  "data": {
    "id": "789abc12-...",
    "code": {
      "value": "123456789",
      "scheme": "0225"
    },
    "registeredDirectories": ["Peppol"]
  }
}

Unlike the inbound response, registeredDirectories contains only Peppol. No Jurisdiction entry is expected or required for outbound.

What you can update

After creation, you can update the following fields through Compliance Network or a PUT request.

• validityPeriod (start and end dates)

• supportedDocuments

• erpSystemId

What you cannot change

The address (codeComponents) cannot be changed after creation. The API enforces this: the PUT request schema does not accept the codeComponents field. The start date in validityPeriod also cannot be changed once it has passed. You can only update it if it is still in the future.

If a customer's address needs to change, follow this process.

1. Remove the existing endpoint.

2. Create a new endpoint with the correct address.

To remove an endpoint through the API, send a DELETE request.

curl --location --request DELETE \
  'https://api-test.sovos.com/v2/configurations/workspaces/organizations/{orgId}/companies/{companyId}/endpoints/{endpointId}' \
  --header 'x-correlationId: SET-TO-UNIQUE-VALUE' \
  --header 'Authorization: Bearer TOKEN'

A successful deletion returns 200 OK or 204 No Content. After deletion, the company can no longer receive documents through this endpoint.

Risk: the transition gap

Between the moment an inbound endpoint is removed and the moment a new one becomes active, the customer's address is either unregistered or pointing to an inactive entry in the Annuaire. Any supplier who looks up the customer during this window and tries to send an invoice may receive a routing error. Coordinate the removal and re-creation closely, and advise the customer to notify key suppliers of any expected downtime.