Company hierarchy enrichment

Company hierarchy enrichment starts with the legal entity that owns the relationship. Build up to the parent chain and top-level owner, then down through subsidiaries. Keep brands, divisions, branches, and affiliates in their proper fields. Hierarchy data maps ownership between legal entities and comes from company registers.^{1, 2} It does not map internal reporting lines.³ Keep ownership paths separate from the way the business operates in the account record.

Start with the legal entity

Choose the entity represented by the account record. Every later relationship depends on this row remaining tied to a registered company.

Use the registered company as the node. A subsidiary is a company whose parent is a majority shareholder.⁴ The parent and subsidiary are separate entities and independent of one another.⁵

Capture the legal name, entity identifier, registration location, and connected account record. If one account represents an umbrella brand, split the underlying legal entities before tracing ownership. This keeps the parent path attached to the company that can sign, buy, or hold the relationship.

Before moving on, check:

• What exact legal entity does this account represent?
• Which entity would appear on the contract or invoice?
• Is this record a company, a brand, a division, or a location?
• Which source confirms the entity identity?

Continue when the record points to one legal company and you can explain why that company belongs in the account set.

Trace upward to the top-level owner

Trace upward before expanding the child side. This path shows who controls the account and where the corporate group ends.

Record the immediate parent first, then follow that parent until you reach the global ultimate. The global ultimate is the top-level parent of the worldwide corporate group and is owned by no other company.⁶ Keep each ownership edge in the record so a rep can see how the account connects to the top of the group.

Use separate fields for immediate parent, higher-level parent, and top-level owner. A single parent field hides the difference between direct control and the end of the ownership chain. If the source gives you a parent name without a clear legal entity, leave the link unresolved and verify the parent before attaching it.

Before you continue, answer:

• Who owns this legal entity directly?
• Is that parent itself owned by another company?
• What entity sits at the top of the chain?
• Which ownership link still needs confirmation?

The path is ready when the account entity connects explicitly to the top-level owner, with unresolved links marked for review.

Expand downward through subsidiaries

With the upward path stable, find the entities below each parent. Work from the parent record and add subsidiaries as separate account nodes while preserving the relationship between them.

Detailed subsidiary information is often difficult to find.⁷ The parent company's annual report or 10-K is often the best source for subsidiary information.⁸ Use the filing to build the first child list, then check for gaps before treating it as complete.

For a public firm, one documented route is to pull the SEC 10-K Exhibit 21, cross-check national business registries, review affiliated pages and annual reports, and confirm the results with a corporate-hierarchy data tool.⁹ Use these sources to resolve entity names and ownership links, not to copy every label into the account hierarchy.

When sources disagree, preserve both the candidate relationship and the reason it remains unresolved. If a parent filing gives you no child record, send the account through another source check before closing the search. A missing entry is a review state, not a clean result.

Check the following:

• Which subsidiaries sit directly below this parent?
• Which entities appear below those subsidiaries?
• Does the child have its own legal identity and account record?
• Does another source confirm the ownership link?

Each child is ready for the hierarchy when it has a legal identity, a parent link, and a source that supports the relationship.

Use a source-specific search when it saves time

A structured company database can speed up discovery once you know which legal entity you are checking. Treat its output as a working map and keep the source trail with the record.

Sabi covers public and private companies.¹⁰ In Sabi, search for the company name, open the company report, and select Ownership data > Subsidiaries > Current subsidiaries from the right menu.¹¹ You can also use Branches as another route to company information.¹²

To screen companies by recorded subsidiary count, choose Ownership Data > Companies owning a subsidiary > No. of subsidiaries, select the range, view the results, choose List format and New format, add Size & group information > No. of recorded subsidiaries, and apply the format.¹³

Use the search result to find accounts worth checking. Confirm the legal entity and ownership path before writing the result into a production account record.

Separate ownership from operating labels

Ownership identifies the legal companies in the hierarchy. Operating labels show how the business presents itself, where it works, or how it groups products.

Keep affiliates in a separate relationship class. An affiliate is related to the parent, but the parent owns less than half and has less control.¹⁴ That relationship can matter for account discovery, yet it should not be stored as a controlled subsidiary.

Keep branch information as a location or operating attribute until a source confirms that it represents a separate legal company. The same rule applies to business units and product brands. For targeting or invoicing, use the legal entity with its own budget.¹⁵

For each record, ask:

• Does this record represent a controlled company or an affiliate?
• Is the name a legal entity or an operating label?
• Does the location need its own account, or does it belong under the legal entity?
• Which entity owns the budget for the relationship?

Every record is ready when its relationship type matches its legal status and operating role.

Normalize the hierarchy before you sync it

Corporate linkage is the vocabulary used for relationships between entities in a corporate group.¹⁶ Define your fields in plain language, then map each provider's labels into those definitions. Store the entity name, entity identifier, immediate parent, top-level owner, child entities, relationship type, source, and review status.

Keep the ownership map separate from employee reporting lines, sales territories, and brand structures. Those views may help account planning, but they answer different questions. A rep should be able to tell whether a record is a legal subsidiary, an affiliate, a branch, or an operating label without opening a second system.

What not to do

• Do not build the family tree from a company website alone. Company web pages can help, yet they are often not explicit about the family tree.¹⁷
• Do not treat relationship labels from different providers as interchangeable. Providers use corporate-linkage terms inconsistently, which makes hierarchy data difficult to compare.¹⁸
• Do not create a separate legal account for every division or brand. A division or brand is a label for the company.¹⁹
• Do not mark a subsidiary as absent because it is missing from the parent filing. Annual reports and 10-K filings may leave subsidiaries unlisted.²⁰