OSINT Jet · Company relationships

LEI Parent Company Search: What the Relationship Really Says

A supplier says it belongs to a large group. You find the supplier in GLEIF and see a parent-company name. Before drawing an ownership tree, check what that line means: it may describe accounting consolidation, with a date and a reporting limit attached.

Start with the question the record can answer

GLEIF’s Level 2 data identifies direct and ultimate accounting consolidating parents. In plain language, this concerns where a company’s accounts are included in group accounts. It is a narrower question than “who benefits from this business?” or “who authorized this salesperson?” The GLEIF overview of Level 2 data sets out that scope.

Write your question before searching: “Does the available record identify the group above this exact legal entity?” If your real concern is whether a website belongs to the business, use the company identity and website guide as well. A parent relationship cannot establish control of an unrelated domain.

Find the entity before following the relationship

Open GLEIF’s LEI Search. Its search box accepts an LEI, legal name or other data fields. Use the LEI when you have it. If you start with a name, compare the result’s jurisdiction and registration details before treating it as the business you mean. Save the chosen record’s link and identifiers in your notes. A similar name is a candidate, not a match.

Two parent fields do different jobs

In the relationship-record specification, the direct parent is the nearest fully consolidating parent; the ultimate parent is the most distant one in the applicable hierarchy. The direction matters: the child is consolidated by the parent. Neither label should be silently changed to “100% shareholder.”

For your working notes, use one row per reported relationship. Do not force the two fields into a complete chain. If a child names an ultimate parent but its direct parent is unavailable, the record has not supplied every intermediate company.

The status of a relationship and the administration of its record are separate. In particular, GLEIF explains that a Level 2 record marked LAPSED is overdue for renewal; that label does not itself say the relationship ended. Check the actual relationship status and the dates. See GLEIF’s search guidance.

Missing parent data is still something to read

A blank-looking parent section can conceal an important distinction. A reporting exception has a category—direct or ultimate parent—and a reason. Examples include NO_LEI, NON_CONSOLIDATING and NON_PUBLIC. Copy the exact reason rather than replacing it with “independent company.” GLEIF’s reporting-exceptions documentation explains the categories.

That gives you three different notes: a named parent relationship, a recorded exception, or no usable result from the search you performed. Those are different evidence states. Only the first supplies the named relationship; the second supplies a reason for withheld or inapplicable information; the third describes your search coverage. None lets you invent a missing company.

Work through this small evidence packet

Fictional training example. The companies, labels and dates below are invented. S, D and U are teaching labels, not real LEI codes, and this is not a result from a live lookup.

“Stonebridge Parts,” labelled S, claims to be part of “North Quay Group,” labelled U. You are given these cards:

1. S’s identity card matches the entity being checked, including its jurisdiction and registration identifier.
2. S’s direct-parent field has a reporting exception with reason NO_LEI. The packet provides no direct-parent name.
3. S has an ultimate-consolidation relationship to U. Its relationship status is active; the relationship record was last updated on 12 March and became overdue for renewal on 12 September. You read the packet on 20 September.
4. A sales brochure says another business, labelled D, is “our partner.” It gives no consolidation record connecting D to S or U.

Try drawing only the supported connections before reading on. The tempting sketch is S → D → U. It is also unsupported: “partner” does not identify the missing direct parent.

The defensible sketch has one typed connection from S to U, labelled reported ultimate consolidating parent, plus a separate note about the direct-parent exception. Keep the overdue renewal flag beside that connection. D stays outside the accounting hierarchy unless additional evidence places it there.

“The supplied record identifies U as S’s ultimate consolidating parent. The direct-parent name is not supplied in this packet, and the record’s renewal is overdue. The brochure’s partner reference does not establish D as an intermediate parent.”

That finding answers the group question without claiming the chain is complete or current beyond the evidence. It also gives the next researcher an exact task: resolve the missing direct relationship and check whether the group structure has changed.

When another source disagrees

Suppose a more recent annual report names a different group. Keep both observations. Compare the entity identifiers, the reporting period, the type of relationship and the date each source describes. A brochure date, a financial-report period and a database update date can refer to different moments.

Do not average the two names or choose the newer webpage automatically. Write the disagreement as a question: “Did the relationship change, or are these sources describing different entities or periods?” Find the filing or announcement that would resolve that specific gap. A relationship table with one unresolved row is more useful than a polished diagram built from assumptions.

Turn the gap into a useful investigation brief

OSINT Jet’s company research workflow can help structure a case around business clues and the relationships being assessed. For this task, supply the exact entity identifiers, source links and disputed connection. Keep each GLEIF record beside the claim it supports, and make the missing direct-parent link an explicit research question. That gives a reviewer something precise to investigate.

If the missing relationship matters enough to commission further work, use the specialist investigation request to agree on the question and scope. Ask for a supported relationship table with unresolved items, rather than a yes-or-no promise about the company.

Before sharing the result, check one sentence: could a reader mistake “reported parent in this record” for “verified owner of everything connected to this brand”? If so, name the entity, relationship type and evidence date more precisely.