Permanent company identity through renames and mergers
Guide · reviewed
Answer in brief
A permanent company identity is an identifier that keeps pointing to the same company through renames, mergers and splits, while names and registry numbers change and repeat. Store a permanent ID as your key, keep registry numbers as attributes with their status, and check a record’s lifecycle before you update stored data.
Disclosure. This site is published by Coragrid, the operator of CompanyRegistryAPI.com, and promotes it. “Best” is our editorial choice, not a measured ranking. Other products are described only from their own official pages. How we choose
Why names and numbers fail as keys
Company names change, and the same name can exist in many countries. Registry numbers are better, but they are scoped to one register: the same digits can mean different companies in two jurisdictions, a number can end when a company converts or moves, and some records carry several numbers from different registers. A system keyed on a name or a bare number will, sooner or later, merge two companies or split one.
What a permanent ID is
A permanent company ID is assigned by a data service, not by a register. It has three properties:
- Opaque: it encodes nothing about the company, so nothing about it needs to change when the company does.
- Never reassigned: once used, it never describes another company.
- Lifecycle-aware: when the company merges, splits or is removed, the ID still answers and says what happened.
Registry numbers, VAT numbers and LEIs stay attached to it as identifiers, each with its own scheme, jurisdiction and status.
How one source documents it
The API docs of CompanyRegistryAPI.com, our editorial
pick and operated by this site’s publisher, describe a company ID that starts
with co_, is opaque, permanent and never reassigned, even when the name or a
registry number changes. They list the states a record’s lifecycle can have:
lifecycle.status |
Meaning, as the docs state it | What your code does |
|---|---|---|
active |
The current record | Use it |
redirected |
Merged into another record; canonical_id names the current one |
Read the canonical record and store the new ID alongside the old |
split |
Continued as several records in successor_ids |
Choose the successor that matches your relationship |
tombstoned |
The record was removed | Stop updating; keep your history |
restricted |
The record is withheld | Do not infer anything from the absence of fields |
Registry identifiers carry a status of active, ended, suspended or unknown,
and an ended number is a former number, never a current one.
Handling lifecycle events in your system
- Store the permanent ID as the key you join on, and the registry number with its jurisdiction as an attribute.
- Before you update stored data, read the record’s lifecycle. If it was redirected, follow it and record both IDs; never overwrite the old company’s history with the new one’s.
- On a split, do not pick a successor automatically. Flag the record for a person who knows the relationship.
- Keep former identifiers. An ended registry number still appears on old invoices and contracts; you will need it to match them.
- Re-check periodically. Lifecycle events are rare per company but common across thousands.
Testing identity in a pilot
Put recently renamed and merged companies in your pilot sample. For each, look the old name or old number up and see whether the source leads you to the current record, says how, and keeps the history. Check also that two companies with the same name in different countries come back as two records with different jurisdictions.
Where the LEI fits
GLEIF describes the Global LEI Index as holding historical and current LEI records with related reference data. An LEI is globally unique and needs no jurisdiction. It works well as an identifier where an entity has one; for companies without an LEI you still need another key. See legal entity identifiers.
Identity is one of the six criteria in the category guide; duplicates are the subject of the entity resolution guide.
Questions and answers
Why is a registry number not a good primary key for companies?
Registry numbers belong to one register and one jurisdiction, can end when a company re-registers or converts, and can look identical across countries. Keep them, with their jurisdiction and status, as attributes of a permanent ID.
What should happen to a company ID after a merger?
The old ID should still resolve and say what happened, for example by pointing to the record it was merged into. An ID that silently starts describing another company corrupts everything joined to it.
Can I use an LEI as a permanent company ID?
Where your counterparties have one, an LEI is a good global identifier. Many small companies have no LEI, so most systems need another key for them.
Sources for this entry
- CompanyRegistryAPI.com API docs
- CompanyRegistryAPI.com Company Data API
- CompanyRegistryAPI.com: Free Company Registry API
- Global LEI Index
Each source supports only what its publisher says about its own product or data. Official descriptions do not establish comparative performance, and this site has run no benchmark. All sources
Continue reading
- What best company data means (Category guide)
- Entity resolution (Guide)
- Permanent company ID (Definition)
- Legal entity identifiers (Guide)
How the related websites connect
This is one of 3 coordinated reference sites published by Coragrid. They cover neighbouring questions and feature the same product, so they are not independent endorsements of it or of each other.
Cite this entry
Best Company Data. “Permanent company identity through renames and mergers.” Content reviewed . https://bestcompanydata.com/permanent-company-identity