France Sirene + RNE — post-canonicalisation API guide
As of 2023, France's Registre National des Entreprises (RNE) became the single authoritative source for commercial data, consolidating multiple prior registries. The RNE and INSEE Sirene remain separate APIs, with Sirene offering free establishment-level data and RNE providing statutory and ownership information. While significant progress has been made, gaps remain in public access to beneficial ownership and historical financial data.
- ▪The RNE, managed by INPI, unified the RCS, RM, RSAC, and RSEIRL registries into one national database starting January 2023.
- ▪INSEE Sirene provides free, programmatic access to establishment data such as SIREN/SIRET, address, and headcount, with updates daily.
- ▪Beneficial ownership data is restricted post-CJEU C-37/20, requiring a legitimate interest justification for public access.
- ▪The Annuaire des Entreprises serves as a user-friendly, no-authentication aggregator of Sirene, RNE, and Bodacc data.
- ▪K-bis extracts and older financial statements remain paywalled through Infogreffe and the Tribunaux de Commerce.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3887433) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } OpenRegistry Posted on Apr 29 France Sirene + RNE — post-canonicalisation API guide #api #kyc #ai #compliance Until 2023, the canonical French company register was a four-way fragmented mess: INSEE Sirene held the identification layer (SIREN, SIRET, name, address, headcount, NAF activity code), the regional Greffes held statutory acts (incorporation deeds, capital changes, director appointments), the Tribunaux de Commerce shared partial data through Infogreffe (paid), and the Bodacc…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
