Key takeaway
Preserve the entity and relationship type. A direct or ultimate accounting consolidating parent is not automatically the ownership evidence required for another review.
Name the question before choosing the field
A diligence request asks for the proposed recipient’s beneficial owners. The response contains a Legal Entity Identifier and an ultimate-parent record. That may help identify the company and a group relationship, but the response needs to be read according to what those fields actually mean.
GLEIF describes the LEI as a unique twenty-character alphanumeric identifier connected to legal-entity reference information. Its Level 1 information addresses entity identity. Its Level 2 data describes direct and ultimate accounting consolidating parents. The word ultimate in that specific relationship should not be silently expanded into every kind of ultimate ownership question.
Complete an identity-to-question map
Hypothetical example: fictional entities Harbor Operations and Harbor Research use one group brand. A proposed license names Harbor Research, while an invoice setup request names Harbor Operations. The supplied reference material associates both with accounting parent Group H. No actual LEIs, companies or registry lookups are represented.
The owner needs to reconcile the contracting entity and payer, and separately obtain the ownership evidence requested by its responsible reviewer. The table keeps useful supplied information without treating it as the answer to a different question.
| Question in the fictional review | Supplied evidence | Supported next decision |
|---|---|---|
| Which legal entity is proposed? | Reference record identifies Harbor Research | Match to the actual agreement; reconcile Operations as payer |
| What accounting group is reported? | Direct/ultimate accounting-parent relationship to H | Retain the typed relationship and observation date |
| Who are the relevant beneficial owners? | No evidence supplied for that requested test | Unresolved; ask for evidence appropriate to the applicable review |
| May this person bind Research? | Contact uses the group brand | Authority remains a separate question |
| Is the transaction permitted? | Identity and parent records only | No sanctions, rights or other clearance inferred |
Keep the relationship type through the export
An export column called parent can lose the distinction between an accounting consolidating parent, a reported shareholder, a brand owner and a contractual guarantor. Preserve the source’s exact relationship type, entity identifiers, observation date and relevant reporting status or exception information when available.
GLEIF’s Level 2 description specifies the accounting-parent relationships and explains how parent LEIs are published when parents have obtained them. A missing relationship or identifier should remain an identified gap under the source’s reporting framework. Do not replace it with zero ownership or an assertion that the company has no parent.
For the fictional entities, sharing Group H is a useful lead for a concentration review. It does not prove that H guarantees either contract, that receipts will move together or that the two operating entities may use each other’s licensed data. Each of those is another factual or contractual question.
Separate a record match from authority to act
Matching a proposed recipient to its legal-entity reference helps avoid confusing similar names. It does not authenticate the person submitting a request or establish that a contact may sign, change payment instructions or receive a package. Keep those controls attached to the relevant operation.
For Harbor Research, the completed issue is concrete: the agreement and intended recipient agree on Research, but the different payer needs documented reconciliation before the payment workflow is accepted. The named contact’s authority remains unresolved. The team does not widen a data grant to the entire group merely to make the names line up.
If a later version of the company record changes a name or relationship, retain the earlier observation used for the original decision and review the changed fact. Do not rewrite historical diligence as though today’s record had been observed at the earlier date.
Ask for the evidence that the actual review requires
The final fictional output contains an identified proposed entity, a typed accounting-parent relationship and specific open questions about payer, authority and required ownership evidence. It avoids both discarding useful registry information and declaring a completed ownership review from an unsuitable field.
Use due diligence to assemble those questions and offer comparison to retain the actual contracting entity and permitted users. VOID’s permissioned introduction is to a named recipient using approved metadata. A registry identifier neither extends that permission nor establishes that a receiving program has enrolled or accepted the company.