Enrichment & Validation

Extracted.
Then Verified.

Every extracted address is checked against the national address base; every company identifier against the official registry. Each field comes back with a verdict, not just a value.

Schedule Demo

A Perfect Read
of a Fake Address.

Extraction gives you what the document says, not whether it is true. A confidently extracted address that doesn't exist, or a company number that was never registered, passes silently through most pipelines.

Checked at the Source.
Verdicts on Every Field.

Extracted fields are verified against the authoritative French registries: addresses against the national address base, company details against the official company register. Not a lookalike database, the sources the administration itself publishes.

Each enriched field carries its own status: verified, not found, or unchecked. The status is attached to the field itself, right next to the extracted value, so your integration reads one answer per field instead of one vague score per document.

Verified fields come back with their canonical form alongside the original text: normalized addresses, registered company details. You store the clean value and keep what the document actually said.

Official sources
data.gouv.fr
INPI

A SIREN goes in.
The company record comes back.

Extracted from the document
552 100 554
SIREN
Origami Entreprises
Compagnie Générale d'Électricité
Active
Registered name
Compagnie Générale d'Électricité
Legal form
SA à conseil d'administration
Head office
Tour Carpe Diem, 92400 Courbevoie
Head office SIRET
552 100 554 03035
Activity
NAF 26.30Z
Officers
Directors and beneficial owners

Company data is served by Origami Entreprises, our own registry built from the official French sources and refreshed daily. Explore it on origami-entreprises.fr

Enriched once.
Checked everywhere.

Verification is not the end of the pipeline, it is what your dossier rules run on. Every enriched value becomes a fact a rule can compare: what the document says, what the applicant declared, and what the official registry answers.

That is how fraud and business checks stop being guesses. A company name on a KBIS is compared to the registered denomination, an address on a utility bill to the declared address in normalized form, a SIREN on a document to the one the dossier claims. A mismatch is a verdict on the dossier, attached to the exact rule and the exact documents that disagree.

The KBIS company name matches the registered denomination
kbis.companyname = registre.denomination
Passed
The company is active in the registry, not struck off
registre.statut = actif
Passed
The address on the proof matches the declared address, in normalized form
facture.adresse = dossier.adresse
Passed
The SIREN on the KBIS is the one declared on the dossier
Failed: the document belongs to another company
Blocking

A failing check blocks the dossier or flags it for review, your configuration decides. Either way the reviewer sees which rule failed, on which documents, with both values side by side.

Verdicts,Not Guesses.

Three outcomes, never a score. Each one is attached to the field it judges, next to the value that was read, so the next step is always obvious.

Address
12 rue de la paix, paris 2eme
verified
Exists in the source. The normalized form comes back with it: 12 Rue de la Paix 75002 Paris
SIREN
384 209 771
not found
No match in the source. Your workflow decides what that means: review, reject, or ask for another document.
Head office SIRET
552 100 554 03035
unchecked
The source was unavailable, so no opinion is given. An outage never blocks your pipeline and never fakes a verdict.

One Call, Values and Verification.

Enrichment verdicts ship in the same API response as the extraction itself: one call, values and verification together.

Read the Enrichment API docs →
Enrichment & Validation

See enrichment verdicts on your own documents.

Sandbox environment
Free API credits
Holofin