Use the CIK to resolve a filer, then verify the security
Use a CIK as an anchor for the SEC filer, then separately verify the security you intend to study. A filing entity and a traded share class are related objects, not interchangeable identifiers. This distinction matters when names, tickers, corporate structures, or market listings change.
The SEC submissions API documentation describes company filing history keyed by CIK and metadata such as names, tickers, and exchanges. Its existence makes identity checks easier; it does not make a ticker a permanent substitute for the registrant’s identity. The card below is an original research convention.
Build two identity layers
The first layer identifies who reports. Record the legal name, CIK, source page, and date of your check. Add former names only when supported by the source, preserving the period or context in which a name was used. A renamed entity should not disappear from your archive merely because the current brand is different.
The second layer identifies what is traded. Record market, ticker or code, share class, and any relevant security description from the filing cover or other authoritative document. If more than one security belongs to a registrant, make separate security rows linked to the same entity row.
Do not try to resolve every corporate relationship in one label. A parent, subsidiary, predecessor, and depositary can appear in related materials without being the same reporting entity. Where the relationship is unclear, create a pending relationship field and find the document that describes it.
Hypothetical case: a changed brand and two classes
Assume fictional Riverlight Corporation previously used a different name and has two hypothetical share classes. You encounter an old filing under the earlier name and a recent quote page under the new brand. None of these details refers to a real issuer.
| Layer | Field | Hypothetical handling |
|---|---|---|
| Entity | CIK | Compare on official filer record and filing |
| Entity | Earlier name | Keep as a sourced alias |
| Security | Class A | Own market and ticker row |
| Security | Class B | Separate row; do not merge rights |
| Relationship | Brand to registrant | Verify rather than infer from logo |
If the CIK and filing identity match, the old name can remain searchable without creating a second company dossier. But the two classes still need separate security descriptions. Shared reporting does not prove identical rights, liquidity, or market treatment.
Verify a historical match carefully
Open the old report and compare its cover, registrant identifier, and any stated name change with the current filer record. Record both publication context and current identity. A current metadata page may not tell you the exact date when an old ticker was valid. Do not assign a precise historical validity interval unless the relevant documents support it.
Then run a reverse test: start with the security row and follow the link to the reporting entity and a specific filing. If the trail jumps through an unverified brand assumption, mark that link incomplete. An identity card should expose ambiguity before claims enter your research archive.
Limits and common mistakes
This procedure does not determine beneficial ownership, economic exposure, or whether two instruments have equivalent rights. Those are separate questions. It also should not be used to assume that every filing mentioning a company was filed by that company. Inspect the filer and the role the company plays in the document.
Frequent errors include storing the ticker as the only archive key, calling the CIK a stock identifier, and copying a similarly named entity’s filings into the same folder. Another is treating a current ticker mapping as a complete corporate history. Keep dates and evidence next to aliases, and allow an unresolved relationship rather than inventing continuity.
FAQ
Can two share classes connect to one filing entity?
They can. Preserve the entity link while giving each security its own identity row and source-backed description.
Does a matching company name establish a matching filer?
No. Compare the official identifier and document context. Names can be similar, abbreviated, translated, or changed, so they are useful search labels rather than sufficient identity proof.