The research question
Several subsidiaries send documents bearing the same group logo and website address. A broad matching rule could combine their invoices, contacts and contractual commitments into one account. That would obscure which entity placed an order and which entity is responsible for an agreement, even though the documents clearly belong to the same wider commercial group. Entity-resolution research separates selecting candidate pairs from deciding whether they identify the same object. That distinction makes the evidence and reversibility of a CRM identity decision central to this design question.
A concrete design choice
The proposed CRM should offer a parent-group relationship independently from identity merging. Each subsidiary retains its registration details, source documents and obligations. A group view may gather related activity, but totals and timelines need an explicit scope so users know whether they are viewing one party or several. A logo or domain can suggest a relationship to review without proving the precise corporate structure.
A consolidated view should preserve the entity behind every item even when the group heading is prominent. Users can then move from a group-wide question to a specific agreement without losing context. The same principle helps explain missing information: a group relationship does not imply that the organization possesses documents for every subsidiary or is authorized to reveal them to every viewer.
What would demonstrate usefulness
Evaluate a group with two subsidiaries, a reseller using the same branding and an unrelated business with a similar name. The desired result preserves supported relationships while preventing obligations and balances from moving between parties merely because their presentation looks alike.