> For the complete documentation index, see [llms.txt](https://help.delpha.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.delpha.io/use-cases/ultimate-parent/what-it-does-and-when-to-use-it.md). # What it does & when to use it ## What it does An **Ultimate Parent Account** is the highest company in a corporate hierarchy that owns all subsidiaries beneath it. It provides a unified view of complex corporate structures, especially for large, multinational organizations. Standard CRM account hierarchies often rely on **manual relationships** and **legal entity structures**, which can result in **orphaned accounts**, incomplete hierarchies, or missed **cross-border ownership links**. This makes it difficult to accurately understand true corporate relationships, global rollups, and group-level insights. Delpha resolves this hierarchy using deterministic company identity: it anchors each entity to its validated website, reconciles the hierarchy against trusted external sources, and returns a verdict with evidence and a confidence score — the same result through Salesforce, MCP, and API. ## When to use it * **Territory assignment & lead routing** — subsidiary inquiries reach the owner of the group relationship instead of being treated as unrelated SMB accounts. * **Account planning & ABM** — one coordinated motion per corporate group, with no cold outreach into a group you are already negotiating with. * **White-space analysis** — a corrected group view exposes the subsidiaries you have not penetrated yet. * **Pipeline & reporting rollups** — group-level revenue views that stay correct through reorganizations. * **Commission integrity** — a subsidiary of an existing customer is not a new logo. * **M\&A monitoring** — when a customer acquires a company, re-parenting surfaces the cross-sell opportunity. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.delpha.io/use-cases/ultimate-parent/what-it-does-and-when-to-use-it.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.