KSIDol documentation > KSIDol modules > Third party by SIREN

Module guide: Third party by SIREN

Non-technical user guide: what the module does, how to use it and how it fits into Dolibarr.

One input, one cardThe SIREN is enough: company name, address, SIRET, APE, legal form, VAT

E-invoicingDirectory verdict on every lookup (Peppol and approved platform)

Cards under watchDifferences with the Sirene register flagged when a card is opened

Quota preservedINSEE responses cached locally for 30 days

1. Module overview

SirenCreatTiers removes manual data entry for French third parties: type the SIREN number in the "Prof. id 1" field of the third-party creation or edit form, and the module queries the official INSEE Sirene API to fill the form for you. Along the way it checks whether the company can receive electronic invoices (central Peppol directory, plus the approved platform's directory when the EInvoicing module is connected), then keeps watching your cards over time: when a card is opened, differences with the Sirene register are listed in a banner, with a one-click update.

Automatic fill from the SIREN: company name (and acronym as alias), head-office address, zip code, town, head-office SIRET, APE code, legal form, computed intra-community VAT number.
Magnifying-glass button next to the SIREN field, and automatic lookup as soon as a valid SIREN is typed (can be disabled).
E-invoicing directory verdict: company reachable or not, reception platform, Factur-X acceptance.
Periodic card check: a banner lists the differences, with "Update the card" and "Validate as is" buttons.
Useful warnings: company closed, restricted dissemination, unusual SIREN check digit.
30-day local cache, and access restricted to authenticated users with third-party read permission.

2. Getting started: the INSEE API key

The module relies on the official INSEE Sirene API — free, but key-protected.

Create a free key on the INSEE API portal (portail-api.insee.fr): the module's setup page contains the complete step-by-step guide (account, application, Sirene API subscription, key retrieval).
Paste the key in the module setup and use "Test the connection" to validate.
The INSEE public plan (30 requests/minute, 2,000 requests/hour) is plenty: the module caches responses locally for 30 days.
Enable the module, open a third-party creation form, type a SIREN: you are up and running.

3. Creating a third-party card from the SIREN

On the third-party creation form, everything starts from the "Prof. id 1 (SIREN)" field.

Type the SIREN — spaces and formatting are tolerated: "938 582 186" is accepted and cleaned automatically.
The lookup fires on its own once 9 valid digits are typed (configurable), or manually via the magnifying-glass button.
The module fills: company name, acronym as alias, head-office address, zip code, town, head-office SIRET (Prof. id 2), APE code (Prof. id 3), legal form and the computed intra-community VAT number.
For a sole trader whose legal name is the personal name, the INSEE trade name feeds the card's alternative name.
A message under the field confirms the retrieval and shows the e-invoicing directory verdict.

4. Completing an existing card

The module also works on the edit form, without overwriting your work.

On edit, only empty fields are completed: what you already typed is preserved.
A setting ("Overwrite fields on edit") lets the INSEE data replace existing values instead.
The magnifying-glass button remains available at any time to re-run the lookup.

5. The e-invoicing directory verdict

On every lookup, the module checks whether the company is reachable for electronic invoicing — the question everyone will ask with the French reform.

Native check of the central Peppol directory (SML/SMP), the official machine-facing channel of the reform, covering every approved platform: registered or not, declared reception platform, Factur-X acceptance.
If the EInvoicing module is enabled and bound to an approved platform, its standardized directory service (AFNOR XP Z12-013) is also queried, and the third party's routing address is prefilled on the creation form.
A single verdict is shown: when the two sources disagree, the positive answer wins (a platform may ignore a company that is actually registered).
If the company is not reachable, saving the card asks for a confirmation — a simple guardrail, which can be disabled in the setup.

6. The periodic card check

A card that was correct on creation day can silently go stale: relocation, legal form change, business closure. The module watches without imposing anything.

When a third-party card is opened, its data is compared with the Sirene register and the e-invoicing directory.
When differences exist, a banner lists them precisely, field by field (card value versus INSEE value).
"Update the card with the INSEE data" applies the corrections in one click; "Validate the card as is" keeps your values.
A compliant or validated card is left alone for 90 days (configurable); the check can be disabled entirely.

7. Warnings and special cases

The module flags without blocking: you always decide.

Administratively closed company: a warning is shown, the card can still be created (useful for history or litigation).
Company under restricted dissemination in the Sirene register: the module tells you; some data may be missing.
Unusual SIREN check digit: a simple warning, input is never blocked (perfectly legitimate numbers break the rule — La Poste, for instance).
SIREN unknown to the register: a clear message, nothing is filled.

8. Module settings

Everything is driven from the setup page, without touching any code.

INSEE API key, with a "Test the connection" button and a built-in creation guide.
Automatic lookup on typing: enabled by default, can be disabled (the magnifying-glass button remains).
Overwrite fields on edit: disabled by default.
E-invoicing directory check: enabled by default.
Confirmation on save when the company is not reachable: enabled by default.
Periodic card check and validity duration (90 days by default).
Restrict checks to French third parties: enabled by default — for foreign companies, Dolibarr's native VIES VAT check remains the right tool.

9. Links with Dolibarr

The module does not work in isolation: it integrates with the native building blocks of Dolibarr.

Third parties : The module works directly inside the native third-party creation and edit form: no parallel screen, the filled data is the standard Dolibarr card's.
Professional identifiers : The native Prof. id 1 (SIREN), Prof. id 2 (SIRET) and Prof. id 3 (APE) fields are used as is, along with the card's legal form and intra-community VAT number.
EInvoicing module (electronic invoicing) : When EInvoicing is enabled and bound to an approved platform, its standardized directory is queried on top of the central Peppol directory, and the third party's e-invoicing routing address is prefilled. Without EInvoicing, the module works fully through the native Peppol channel.
Native VIES VAT check : For non-French companies, Dolibarr's native VIES check button, next to the intra-community VAT field, remains the reference tool — the module does not replace it.
User permissions : The lookup is restricted to authenticated users with third-party read permission; no data is reachable without logging in.