What is account hierarchy?
Big organizations are not single accounts - they are parents, subsidiaries, and divisions that relate to each other.
Account hierarchy models that structure, so you can both work each entity and see the whole enterprise's revenue and relationships together.
Short answer
Account hierarchy is the parent-child structure that links related company records, such as a corporate parent with its subsidiaries, divisions, or regional offices. It lets you see the whole organization and roll up deals and revenue across it, while still working each entity separately. Hierarchy is essential for selling into large, multi-entity companies.
Key takeaways
- Links related company records in a parent-child structure.
- Models corporate parents, subsidiaries, divisions, and offices.
- Lets you roll up deals and revenue across the whole organization.
- Essential for selling into large, multi-entity accounts.
Why it matters
Without hierarchy, a global customer looks like a dozen disconnected accounts, hiding the true size and structure of the relationship. Hierarchy reveals the whole organization, enabling enterprise account planning and accurate revenue rollups across every entity.
How Ardovo handles it
Ardovo supports account hierarchies, linking parents to subsidiaries and rolling up deals and revenue across the tree. Rook keeps the structure accurate and distinguishes true hierarchy relationships from duplicates, so large accounts are seen whole rather than fragmented.
Frequently asked questions
Why is account hierarchy important?
Because large customers are multi-entity organizations - parents, subsidiaries, divisions. Without hierarchy they appear as disconnected accounts, hiding the relationship's true size. Hierarchy lets you see the whole organization and roll up deals and revenue across it for real enterprise account planning.
What is a parent-child account relationship?
A link where one account (the parent) sits above related accounts (the children), such as a corporate headquarters over its regional offices or subsidiaries. The children remain separate workable records, but the hierarchy connects them so you can view and report on the whole tree.
How is hierarchy different from a duplicate?
A hierarchy links distinct but related entities that should stay separate; duplicates are two records for the same entity that should merge. Confusing them is a costly mistake - merging a subsidiary into its parent destroys a real relationship. Confirm which case you have before acting.