Prospect research

How to Map Parent Companies in a B2B Prospect List

Learn when to merge, link or keep B2B accounts separate. Use legal identity and parent evidence to distinguish subsidiaries, branches and buying locations.

Expandia · · 10 min read

A branching arrangement of miniature office and factory buildings on a lilac background.

Three prospects share a logo. One runs a factory outside Bologna, another sells replacement parts from Rotterdam, and the third signs the group’s purchasing agreements from Vienna. If you merge them into a single account, the factory’s maintenance enquiry could land with a lawyer at headquarters. If you treat every name as independent, three salespeople might introduce themselves to the same procurement director on Monday morning. The useful answer is often to keep separate records and document how they connect.

The examples in this guide are fictional. The method is designed for a researcher cleaning a B2B prospect list before a campaign, territory handover or CRM import. It distinguishes three questions: which legal entity exists, how it relates to other entities, and where a particular buying decision happens. Each needs different evidence.

Define what one row is supposed to represent

Ask the person using the list what they will do with it. A distributor assigning warranty obligations may need the precise contracting entity. A field engineer planning a route needs operating sites. A strategic account director negotiating a framework might need a view across the whole group. All three can use the same underlying information, provided the records retain their identities and relationships.

Write a short example before designing columns. “One account per legal entity, with separate site records for physical locations and an optional parent relationship” is workable. “One row per company” leaves researchers guessing whether a division, brand or franchise qualifies. Document the decision in the handover so the next import uses the same unit.

Permit one organisation to play several roles. A distribution subsidiary can be the invoice recipient for a machine delivered to its customer. A shared services centre can run supplier onboarding for several entities. A workshop can influence technical specifications while a purchasing company signs the order. Keep roles on the transaction or buying context where possible. A permanent label saying “buyer” tells colleagues little about who buys what.

Collect enough identity evidence to distinguish close matches

Start with the name the organisation uses in a legal context, its jurisdiction and any registration number published by the relevant register. Retain the trading name exactly as customers see it. Record both the source and the date checked. A company website footer can suggest an identity; a registry entry can help establish the registered name. A group website covering several countries may give the identity of the website operator alone.

Where an organisation has a Legal Entity Identifier, GLEIF’s Level 1 reference data gives researchers an additional identity check. It includes the legal name, registered address and country of formation. Compare those attributes with your candidate rather than accepting the first search hit. Preserve the identifier as issued. A registered office can differ from a factory, showroom or distribution centre. See GLEIF’s description of Level 1 data.

Look carefully at familiar names. “Meridian Process Systems” could be a trademark used by a manufacturer, a national distributor and a servicing subsidiary. A suffix such as GmbH or BV offers a clue, but stripping it for display can conceal the distinction you need to investigate. Keep the full original string, a separate simplified search form and an internal identifier. Normalisation should help find candidates for review without erasing the evidence used to separate them.

Record the relationship the source actually establishes

GLEIF describes its Level 2 parent data in terms of direct and ultimate accounting consolidation. A direct consolidating parent and the highest consolidating parent can be different entities. Record the relationship type alongside its source. The result can help a researcher group subsidiaries, but it does not identify the employee authorised to approve a purchase or the contracting party for tomorrow’s order. Read GLEIF’s guide to Level 2 relationships.

Keep the direction explicit. In a fictional example, Meridian Instruments BV reports to Meridian Europe Holdings, which in turn is consolidated by Meridian Group. Attach the immediate relationship to the first pair. If you also maintain an ultimate-parent field, put Meridian Group there with its own evidence. Entering the group in both fields because it is the best-known name makes the hierarchy harder to verify later.

An absent parent identifier deserves a documented reason when one is available. GLEIF publishes reporting exceptions that include situations in which the parent lacks an LEI or the relationship falls within an accepted exception. A blank search result alone gives you no basis for declaring a company independent. Store the observed gap and leave the commercial conclusion open. Review GLEIF’s reporting exceptions.

Walk a confusing pair through the checks

Suppose a trade-show badge says “Meridian Packaging North,” the exhibitor directory lists meridian.example and an invoice supplied by your own finance team says “Meridian Equipment Services BV.” The exhibition stand establishes a brand presence. The invoice documents a past transaction with a named entity. Neither item alone proves that every employee using the group domain belongs to the invoiced subsidiary.

Follow the links on the regional site to its contact and company-information pages. Read the address and registration details. Compare them with the invoice and the official register where available. If the registered office matches but the operating address differs, add the operating site separately. If the registration numbers conflict, pause the proposed merge and investigate whether one document belongs to a sibling company, an earlier legal name or a previous supplier arrangement.

Now test the commercial role. The contact might say that service contracts go through the Rotterdam office while purchases of new machines go through Vienna. Record that scope beside the role, with the date and its source. A colleague selling spare parts has a different next step from one proposing a capital purchase. One consolidated account view can support both paths if the underlying entities remain accessible.

Decide when to merge, link or leave a case open

Merge duplicate records when affirmative evidence identifies the same entity and you have reviewed dependent information. Matching jurisdiction and registration number is a strong starting point. Check whether either candidate is deliberately stored as a site, billing account or historic record. The same legal identity can appear in those records for legitimate operational reasons.

Link distinct records when evidence supports a group, branch, franchise or distribution relationship. Give each link its proper meaning. A reseller carrying a manufacturer’s logo may have an entirely separate ownership structure. A licensed franchise can trade under the same name as neighbouring locations while another company operates each outlet. A subsidiary belonging to the group can still use an unrelated brand after an acquisition.

Leave a candidate open when the signals are weak or contradictory. Two businesses sharing a serviced office, telephone answering service and generic industry description may have no relationship. Set down the missing fact that would settle the question. “Need local registration number from the contracting terms” gives the next researcher a bounded task. Assign a review date only if fresh evidence is reasonably expected.

Protect the history attached to each record

Before combining confirmed duplicates, inventory what points at them. Look for open opportunities, quote versions, service cases, order history, territory assignments, suppression instructions and account-specific pricing. Choose a surviving internal identifier deliberately. A cleaner display name offers little consolation if the merge disconnects a renewal reminder from its contract.

Imagine record A contains a dormant opportunity and an instruction to contact procurement only through the supplier portal. Record B contains a newer trading name and an active representative. Preserve the restriction when reconciling them. Have the account owner inspect the result before any automated sequence restarts. If different departments maintain different systems, agree which one originates the identity and which receives it downstream.

Test the proposed transformation on a small copy. Compare counts before and after, inspect several accepted matches and examine the records deliberately kept separate. Record the old identifiers and how they map to the surviving record. A colleague investigating a historical invoice should be able to follow its original reference. Retaining this crosswalk also allows a mistaken consolidation to be investigated without relying on someone’s memory.

Investigate groups that changed shape

Acquisitions and reorganisations introduce dates. An announcement that a group intends to acquire a company carries a different meaning from a notice confirming completion. A change of ownership may leave the subsidiary’s registered identity intact. A legal merger can affect which entity survives. Capture the event described, its effective date where stated and the document supporting it. Route uncertain contractual consequences to the person responsible for the agreement.

Suppose a group has sold a repair division but continues supporting former customers for six months. A corporate relationship diagram can be accurate and still give the wrong service contact. Preserve the dated support arrangement with the relevant product line. The marketing team can remove the former division from a group campaign while the customer service team keeps a temporary escalation route.

Use the same care with a rebrand. A new website, fresh logo or shortened name can look like an entirely new prospect to a list builder. Check the registration details and trading history. If the entity is continuous, retain the older label as a searchable alias and update the display name. If the brand transferred to another operator, document when that happened and investigate outstanding commercial relationships individually.

Build an account brief a salesperson can actually use

A useful brief for Meridian would show the contracting company, operating site, group relationship, decision role, evidence date and remaining doubt. Keep direct observations distinct from working assumptions. “Vienna issued the last framework agreement” describes a document. “Vienna controls all spending across Europe” is a broader conclusion that still requires confirmation.

Add a short approach note. “For maintenance consumables, ask the Bologna site who selects approved replacements. Check the central agreement before quoting.” That instruction supports a relevant conversation. A family tree without a decision note may encourage a representative to start at the most senior address simply because it sits at the top of the diagram.

Include a route for correcting the brief. A local manager may know that budgets have moved to a regional office. Ask which product category changed, when the new arrangement began and how it can be confirmed. Preserve the older observation with its date. Conflicting reports from different sites can both be accurate when categories, contracts or purchasing thresholds differ.

Count the audience at the level your campaign needs

Suppose a trial list contains twelve operating sites belonging to five legal entities within two groups. For a training tour, twelve locations may be the relevant denominator. For a supplier registration exercise, five entities might be closer. For an executive introduction, two coordinated approaches might be enough. Report the unit beside the count. “Twelve accounts reached” would leave the reader unable to judge coverage.

Assign ownership at the same level as the action. A group account director might coordinate messaging while local representatives manage site visits. Share enough context to prevent overlapping approaches. An invitation to one divisional procurement meeting should not automatically close every opportunity attached to another division, especially when the two teams buy different categories.

Look at exclusions with equal care. A restriction applying across an entire customer group has a different scope from a request relating to one local contact. Preserve the recorded scope and ask the responsible owner about ambiguity. A deduplication job should never quietly expand an entitlement or erase a documented preference. A short manual review of sensitive records is usually cheaper than reconstructing a damaged relationship.

Run a ten-record handover test

Select a mix that includes a resolved duplicate, a branch, a subsidiary, an unrelated company with a similar name and an unresolved relationship. Give the records to a colleague who did not create them. Ask that colleague to identify the entity you would quote, the site you would visit and the organisation you would approach about a group agreement. Every answer should point to a piece of evidence or a clearly named gap.

If the colleague cannot answer, fix the representation before buying another list or expanding into another territory. A missing source date may be the problem. Perhaps the CRM hides the relationship type on its default screen. Sometimes two researchers simply interpreted “head office” differently. Change the field, example or instruction that caused the misunderstanding and repeat the exercise with different records.

Expandia’s prospect finding service asks teams to define the market, roles and required fields before research begins. Add one more decision to that brief: what makes two records the same for this particular sales motion? A defensible answer preserves local opportunities, coordinates group-level contact and lets the next person reproduce the research.