Products & Services · IDFinder
Resolve entity ambiguity in seconds. Provide a legal name and a jurisdiction; receive the exact registry ID, tax number and issuing authority. One identifier, resolved once, used everywhere downstream.
IDFinder normalises the legal name, queries the registry index for the selected jurisdiction, scores every candidate entity and returns the single verified identifier.
The problem
Legal names collide, drift and translate. Every downstream system, screening, onboarding, monitoring, needs the one thing a name cannot give it: a stable registry identifier.
A group parent, its holding company and a dozen operating subsidiaries share almost the same string. Screening the name alone returns the wrong entity, or all of them.
Companies rename, merge, transliterate and file under abbreviations. The name your client gave you is rarely the name on the register today.
Free-text names cannot be joined, deduplicated or monitored. Every hand-off between systems reintroduces the same ambiguity.
The exchange
As filed, as commonly known, or as your client wrote it. Transliteration and legal-form suffixes are handled.
A two-letter country code. Sub-national registers are selected automatically where they apply.
No internal reference, no LEI, no prior identifier required.
Returned as JSON over the API, in the web application, or in bulk for batch resolution.
Identifier formats
IDFinder returns the identifier in the form the issuing authority uses, validated against that authority's structure. A selection of the 148 jurisdictions supported.
Downstream
The identifier IDFinder returns is the key every other Revolutio service takes. No re-matching, no human in the loop, 100% straight-through processing.
One call turns a name and a country into a verified registry identifier.
The identifier is passed straight into a Revolutio company search, no re-matching.
Certified extracts, filings and ownership data return against that same key.
The identifier anchors ongoing monitoring, so changes map to the right entity forever.
{ "legal_name": "Petrobras", "jurisdiction": "BR" } → 200 OK { "official_name": "Petróleo Brasileiro S.A.", "identifier": "33.000.167/0001-01", "identifier_type": "CNPJ", "authority": "Receita Federal", "status": "active" }
In practice
Turn whatever the client typed into a verified identifier before the file is ever opened, so no case starts against the wrong entity.
Resolve a legacy portfolio of free-text names in bulk, then reconcile duplicates that were never visible as duplicates.
Give CRM, screening and core banking the same registry identifier, and the joins between them stop failing.
Talk to our team about IDFinder, batch resolution, and how it fits into your onboarding and screening workflow.