Match a company across US, A-share, and Hong Kong disclosures
Match cross-market disclosures through legal entity relationships, not translated names or similar logos. Build a map with three layers: the reporting entity, the market-specific security, and the particular report. Only combine evidence after you know which layer each document describes.
The SEC API documentation provides filer metadata, while HKEXnews and CNINFO offer market-specific disclosure entry points. These sources help locate records. None of their entry pages proves that two securities or two similarly named entities are economically or legally equivalent.
Draw relationships before joining documents
Start with the legal name printed on each report. Preserve the original-language name, market identifier, and local filing reference. Then find explicit text connecting the entities: a parent-subsidiary description, listing explanation, security description, or another directly relevant disclosure. Label each connection with the document and passage supporting it.
A useful relationship map allows both “same issuer, different security” and “related entities, different issuers.” Do not force every match into one company row. If a US report belongs to a holding company and a local announcement belongs to an operating subsidiary, keep their identities separate even when the group brand is shared.
Hypothetical example: a group with several reporting objects
Assume fictional Summit Transit has a holding company, a locally listed subsidiary, and a depositary security described in its documents. This is a made-up organizational scenario.
| Object | Record separately | Evidence needed for a connection |
|---|---|---|
| Holding-company registrant | Legal name and filer identifier | Report cover and organization text |
| Local listed subsidiary | Local legal name and code | Subsidiary and ownership disclosure |
| Market security | Exchange, class, instrument description | Cover or security terms |
| Annual report | Entity, period, scope, language | Actual report |
| Event notice | Event entity and date | Notice text |
If the subsidiary announces a facility agreement, do not immediately write that the holding company signed it. The group relationship may be relevant, but the party named in the agreement is a separate factual question. Your map should keep that difference visible.
Test comparability at the document level
After resolving identity, compare report periods and reporting perimeters. Two reports can concern the same group but cover different dates or scopes. Record those differences before joining passages. A shared fiscal-year label does not prove identical consolidation, translation, or disclosure content.
Write an evidence sentence for each join: “these documents refer to the same registrant because…” or “these documents concern related entities because…,” followed by a source locator. If you cannot finish that sentence with evidence, keep the connection provisional. A provisional link is useful for further searching but should not support a merged factual statement.
Verification and boundaries
Start from a selected market security and trace your map to the legal reporting entity and one source document. Then reverse direction from the report to the security. Verify that neither route depends solely on a brand translation. For historical materials, repeat the check using identity relationships relevant to that period rather than current structure alone.
This identity exercise does not establish conversion rights, ownership equivalence, or investment suitability. Those require the actual instrument terms and other evidence. Nor does finding the same announcement in several markets create independent confirmation: it may be one issuer message distributed through several routes.
Common mistakes include dropping suffixes from legal names, confusing a depositary with the issuer, and merging parent and subsidiary announcements. Another is citing the English version of a local report while attributing it to a different US registrant. Keep entity, security, and document identifiers as separate fields.
FAQ
Can one issuer have multiple market codes?
Yes, but verify the connection and preserve the security distinctions. A common issuer does not establish identical rights for each instrument.
Is a translated company name enough for matching?
No. Use it to discover candidates, then check legal names, identifiers, and explicit relationship disclosures before merging research evidence.