Skip to content
FonteumThe Graph

By use case

Exclusion & monitoring (self-serve)Free roster screen — no accountExclusion & sanctions screeningCredentialing & provider-data enrichmentAudit evidence & defensible programsProvider data for AI / RAGM&A & network diligence

By buyer

Compliance & riskJournalists & newsroomsDevelopers & AI teams

By industry

HealthcareProviders & facilitiesSanctionsOFAC / EU / UK / UN / OIG / SAMFederal contractingSAM · USASpending · FAPIIS

The capability layer

APIREST + bulk accessFor AI agentsModel Context Protocol serverFHIR R4 APIBulk exportAudit packSigned report artifacts; source facts remain separately citedReconciliationSource-vs-source diffsAI answers with sourcesHow records link upHistoryRetained versions for named sources

The differentiator

Coverage & sourcesThe catalogFreshnessMethodologyCare CompareFacility qualityAI answers, comparedBrowse all datasets →
Research

The dev on-ramp

DocsAPI referenceConnect your AI agent (MCP)One-paste installFHIR sandboxLive API surfaceQuickstartStatusChangelogSDKs & integrations
Pricing
Sign inFree roster screen →Get a signed certificate →

Solutions

Exclusion & monitoring (self-serve)Exclusion & sanctions screeningCredentialing & provider-data enrichmentAudit evidence & defensible programsProvider data for AI / RAGM&A & network diligenceCompliance & riskJournalists & newsroomsDevelopers & AI teamsHealthcareSanctionsFederal contracting

Platform

APIFor AI agentsFHIR R4 APIBulk exportAudit packReconciliationAI answers with sourcesHow records link upHistory

Data

Coverage & sourcesFreshnessMethodologyCare CompareAI answers, comparedBrowse all datasets →
Research

Developers

DocsAPI referenceConnect your AI agent (MCP)FHIR sandboxQuickstartStatusChangelogSDKs & integrations
Pricing
Sign inFree roster screen →Get a signed certificate →
  1. Fonteum
  2. /
  3. Glossary
  4. /
  5. SIREN vs SIRET
Fonteum Data GlossaryData Standards

SIREN vs SIRET: what is the difference?

SIREN is the nine-digit French identifier for a legal unit, such as a company or association. SIRET is the 14-digit identifier for a specific establishment: the same nine-digit SIREN plus a five-digit NIC establishment code. One legal unit can therefore have multiple SIRET numbers across locations.

Full name: French SIREN Number Compared with SIRET Number

Short explanation

INSEE's Sirene register assigns SIREN numbers to legal units and SIRET numbers to establishments. The SIRET embeds the SIREN of the legal unit and adds the NIC, an internal classification number for the establishment. For cross-border entity resolution, SIREN identifies the legal entity, while SIRET identifies the operating site or location-level establishment.

Related platform: Entity graph - resolved organization records

Last updated: 2026-07-11Reviewed by: Fonteum data standards desk — Source-provenance editorial review. Definitions checked against primary federal sources.

How it’s used

  • French company lookup: SIREN gives the durable legal-unit identifier, while SIRET identifies each establishment tied to that legal unit.
  • Location matching: a business with several offices can share one SIREN but have separate SIRET values for each establishment.
  • Fonteum keeps SIREN and SIRET at different identity levels so legal-entity facts do not collapse into establishment-level location facts.

Frequently asked questions

How many digits are in a SIREN number?
A SIREN number has nine digits and identifies a French legal unit.
How many digits are in a SIRET number?
A SIRET number has 14 digits: the nine-digit SIREN plus a five-digit NIC code for the establishment.
Can one SIREN have several SIRET numbers?
Yes. One legal unit can operate several establishments, each with its own SIRET under the same SIREN.

Related terms

  • Entity Resolution
  • ABN vs ACN
  • UEI
  • CAGE Code
  • Provenance
  • Due Diligence

Explore in Fonteum

How Fonteum sources, resolves, and publishes data tied to this term.

  • PlatformEntity graph - resolved organization records
  • PlatformProvider and organization data API
  • PlatformSource provenance model

Authoritative sources

  • INSEE: SIREN number↗
  • INSEE: SIRET number↗
  • INSEE: Sirene business register↗
← All glossary terms

What’s on file, by the numbers

Platform snapshot · 2026-07-15

13.4Mproviders & companiesProviders, organizations, owners, and facilities on file
26.2Msource-linked factsSource-linked field facts in the dated platform snapshot
—sources liveCrosswalk-resolved sources with a proved content transition in the preceding 45 days
111sources integratedActive registry rows; integration does not establish a load
13state Medicaid jurisdictionsDistinct states represented in the state-exclusions serving table

Built on the authoritative federal record

The primary sources, named on every page.

These are the federal agencies whose public datasets Fonteum ingests and attributes — the issuing authorities, not customers or partners. Every figure on the site links back to one of them.

  • CMS
  • HHS-OIG
  • HRSA
  • FDA
  • NLM
  • NUCC
  • Census
  • BLS
  • BEA

See the full source registry, with license and refresh cadence for each →

Reproducible by design

Published figures name their source and date.

Source and date

Published research identifies its government file and observation date. Source-file SHA-256 coverage is disclosed separately; facts do not currently link deterministically to signatures.

Reproducible SQL

Each study ships the exact query behind its figures, run against the same dated copy of the federal file we used. Re-run it yourself.

Daily observations

The platform records table row counts daily. Those observations detect local drift; they do not imply that an upstream publisher released or Fonteum ingested new data that day.

Named medical review

Reviewed by Jennifer Montecillo, MD, medical reviewer. Non-practicing medical reviewer.

Read the full provenance and attestation methodology →

Fonteum
Platform
Platform overviewAPIFor AI agents (MCP)FHIR R4 APIBulk exportAudit packReconciliationAI answers with sourcesHow records link upHistory
Solutions
All solutionsExclusion & sanctions screeningCredentialing & enrichmentAudit evidenceProvider data for AI / RAGUse casesM&A & network diligenceCompliance & riskJournalists & newsroomsDevelopers & AI teams
Data & sources
Coverage & sourcesBrowse all datasetsState Medicaid exclusionsFreshnessMethodologyCare CompareNursing homesRecall recordsSanctions screeningOIG LEIE listOwnershipStaffingDeficienciesSpecial Focus Facilities
Federal contracting
OverviewAwards during active exclusionFederal debarment scorecardProcurement questionsContractor lookup8(a) certification guide
Developers
Developer hubDocsAPI referenceQuickstartStatusChangelogSDKs & integrationsWebhooks
Research & guides
Research hubLearnHow it worksGuidesHealthcare provider dataExclusion & sanctions screeningProvider credentialing dataHealthcare data for AIHospital margin gapProvider access gapsGlossaryComparisonsSourced data vs plain LLM answersCitationsManifestoWhy Fonteum
Company
AboutPressCustomersPricingContactEditorial policyCorrections
Trust & legal
TrustTrust markQualitySecurityPrivacy policyTerms of serviceAPI termsMedical disclaimer

Reviewed by Jennifer Montecillo, MD, medical reviewer. Non-practicing medical reviewer.

© 2026 Fonteum LLC. All rights reserved.

·hello@fonteum.com

A public-records graph that exposes source and observation metadata where supplied.

Fonteum's provenance ledger contained 26.2M source-linked facts on July 12, 2026. All but 14 carried a source-file SHA-256; 0 linked deterministically to a signature. Inspect a supplied snapshot id at fonteum.com/verify · source-mark coverage and limitations.
Request access→