First action
Identify the exact entity and transaction, then rank the material claims to test. Use stable identifiers before linking people, proceedings or companies.

Topic pathway
Verify entities and roles, interpret public allegations and reviews, and define decision conditions.
Identify the exact entity and transaction, then rank the material claims to test. Use stable identifiers before linking people, proceedings or companies.
A documented identity check, contextual risk findings, missing documents and explicit conditions for proceeding or deferring.
An allegation is not a ruling; a shared address is not ownership; a negative review is not automatically manipulation. Retain dates, outcomes and plausible alternative explanations.







Record the fact being checked, the material reviewed, what remains unknown, the person responsible and the next review trigger. A result is useful when another reader can understand why an action was chosen and what would change it.
| Situation | Check | Record to keep |
|---|---|---|
| Partner existence | Connect trading name and legal identifier in the relevant register. | Exact entity, documents and dates; existence separate from solvency. |
| Director or representative | Verify published role and authority for the transaction. | Role source and mandate confirmation. |
| Public allegation | Find origin, updates and the entity’s response. | Facts separate from accusations; namesakes excluded. |
| Sanctions candidate | Compare identifiers and current lists for relevant regimes. | Candidate, list, date, contradictions and compliance referral if unresolved. |
Rank unknowns that could change the decision. A material contradiction warrants a targeted request. Repeated articles with a shared origin cannot compensate for a missing decisive document.
Registration establishes administrative information. It validates neither the offer, payment nor correspondent’s authority.
Describe established facts, hypotheses, unknowns and pre-decision conditions. Date the note and specify what triggers another review.
Reading technical evidence
An RDAP response pairs an event type with a date. Retain both fields together.
| Observed item | What it means |
|---|---|
| eventAction: registration | Registration event for the object; it does not date the website’s first publication. |
| eventAction: last changed | A change to the registered object; it does not prove a change of owner. |
| eventDate | Read the date with its UTC offset and the response consultation date. |
Record the exact domain and queried service. Corroborate the operator’s identity and publication history separately.
Fictional learning scenario
A partner search surfaces an article about a person with the same name. It contains no identifier supporting a reliable match.
A shared name is observed. Connection to the reviewed entity is unproven; the allegation and any outcome require context.
Compare roles, periods, jurisdictions and relevant public identifiers. Seek the primary source and any update before repeating the claim.
An identity mismatch requires removing the connection. If identity remains uncertain, mark the issue unresolved and specify which document could change the decision.
A shared name, registered-office address or similar photograph is insufficient to attribute proceedings to someone.
Further reading
ANNUAIRE ENTREPRISES FRANCE · Français
French practical guidance on distinguishing SIREN, SIRET, establishment address and activity code, with checks against the official register.