Salesforce Account Hierarchy is the parent-child relationship structure that links subsidiary and regional accounts to their parent organisations in the CRM – enabling enterprise sales teams to manage complex corporate structures where a single global company has dozens of subsidiaries, business units, and regional entities that each represent separate buying centres. Without a properly configured account hierarchy, Salesforce data becomes fragmented: total account revenue is scattered across disconnected records, global account team coordination is impossible, and enterprise rollup reporting produces misleading numbers. This guide covers how account hierarchy works in Salesforce, how to set it up correctly, and how to use it for enterprise account management and reporting.
The best guide is the one that makes complex account relationships easier to understand.
A practical explanation should help the reader see where hierarchy improves control.
That means the guide should connect the data model to practical account management.
For many organisations, the value is in seeing the full account picture rather than isolated records.
It should also show how hierarchy helps teams manage ownership, reporting, and relationship context.
A good guide should explain why connected account structures matter and how they support visibility across the business.
That makes hierarchy setup an important part of enterprise account management.
Salesforce account hierarchy is useful because many businesses sell into organisations that have parent companies, subsidiaries, and related entities. A simple flat account list cannot always show those relationships clearly.
The best guide is the one that makes complex account relationships easier to understand.
A practical explanation should help the reader see where hierarchy improves control.
That means the guide should connect the data model to practical account management.
For many organisations, the value is in seeing the full account picture rather than isolated records.
It should also show how hierarchy helps teams manage ownership, reporting, and relationship context.
A good guide should explain why connected account structures matter and how they support visibility across the business.
That makes hierarchy setup an important part of enterprise account management.
Salesforce account hierarchy is useful because many businesses sell into organisations that have parent companies, subsidiaries, and related entities. A simple flat account list cannot always show those relationships clearly.
The best guide is the one that makes complex account relationships easier to understand.
A practical explanation should help the reader see where hierarchy improves control.
That means the guide should connect the data model to practical account management.
For many organisations, the value is in seeing the full account picture rather than isolated records.
It should also show how hierarchy helps teams manage ownership, reporting, and relationship context.
A good guide should explain why connected account structures matter and how they support visibility across the business.
That makes hierarchy setup an important part of enterprise account management.
Salesforce account hierarchy is useful because many businesses sell into organisations that have parent companies, subsidiaries, and related entities. A simple flat account list cannot always show those relationships clearly.
The best guide is the one that makes complex account relationships easier to understand.
A practical explanation should help the reader see where hierarchy improves control.
That means the guide should connect the data model to practical account management.
For many organisations, the value is in seeing the full account picture rather than isolated records.
It should also show how hierarchy helps teams manage ownership, reporting, and relationship context.
A good guide should explain why connected account structures matter and how they support visibility across the business.
That makes hierarchy setup an important part of enterprise account management.
Salesforce account hierarchy is useful because many businesses sell into organisations that have parent companies, subsidiaries, and related entities. A simple flat account list cannot always show those relationships clearly.
What Is Salesforce Account Hierarchy?
The Salesforce Account Hierarchy is built using the standard Parent Account lookup field on the Account object. Every Account record can have one Parent Account – linking it to the Account record that represents the parent company, headquarters, or controlling entity. This creates a tree structure: a Global Ultimate Parent at the top, with Domestic Ultimate Parents or Regional Entities below it, and individual Operating Companies or Business Units at the leaf level.
Example hierarchy for a multinational corporation:
- Acme Corporation Global (Parent) – the ultimate parent entity
- Acme North America (child of Global) – regional headquarters
- Acme US Operations (child of North America) – operating company
- Acme Canada (child of North America) – operating company
- Acme Europe (child of Global) – regional headquarters
- Acme UK (child of Europe) – operating company
- Acme Germany (child of Europe) – operating company
Salesforce’s Account Hierarchy view (accessible from any Account record via the “View Account Hierarchy” button) displays this tree structure – letting account managers navigate between related entities and understand the full corporate family.
Why Account Hierarchy Matters for Enterprise Sales
- Total account revenue visibility: Enterprise account managers need to see the total revenue across all subsidiary accounts, not just the entity they are assigned to. Without hierarchy, an account manager assigned to “Acme US Operations” has no visibility into the $2M in contracts held by “Acme Canada” under the same parent
- Cross-sell and expansion identification: A consolidated view of which Acme subsidiaries already use your product and which don’t is the foundation of a strategic expansion plan. Account hierarchy makes this visible
- Avoiding competitive displacement within the hierarchy: Multiple sales reps from the same company pursuing different subsidiaries of the same parent can conflict – hierarchy visibility enables deliberate account strategy rather than accidental internal competition
- Global agreement management: Enterprise pricing agreements, master service agreements, and global contracts are negotiated with the parent entity and applied to subsidiaries. Managing these at the parent Account level with hierarchy linking all subsidiary accounts maintains contractual context
- Rollup reporting: Salesforce reports can aggregate Opportunities, revenue, and activity across all accounts in a hierarchy – total pipeline and closed revenue by corporate family rather than by individual subsidiary
Setting Up Account Hierarchy in Salesforce
Step 1: Enable the Parent Account Field and Hierarchy View
The Parent Account lookup field is a standard field on the Account object – it exists in all Salesforce editions and does not require configuration to be enabled. To make the hierarchy view accessible:
- In Setup ? Object Manager ? Account ? Page Layouts, add the “View Account Hierarchy” button to the Account page layout’s button bar
- Verify the “Parent Account” field is on the page layout so account managers can see and edit the parent relationship from the Account record
Step 2: Define Your Account Hierarchy Naming Convention
Before populating hierarchy data, define naming conventions that make parent-child relationships clear at a glance in list views and reports:
- Global parent: “Acme Corporation” (no suffix)
- Regional entities: “Acme – North America”, “Acme – Europe EMEA”
- Operating companies: “Acme – United States”, “Acme – United Kingdom”
Consistent naming prevents the ambiguity of having five “Acme” records with no indication of which is the parent and which are subsidiaries.
Step 3: Create Parent Account Records First
When building hierarchy, always create parent records before child records – you cannot set a parent on a record that doesn’t exist yet. For enterprise account hierarchies being built from scratch:
- Create the Global Ultimate Parent Account record
- Create Regional Entity records with the Global Parent set as their Parent Account
- Create Operating Company records with the appropriate Regional Entity set as their Parent Account
Step 4: Populate Parent Account Field at Scale (Data Import)
For accounts already in Salesforce that need to be linked into a hierarchy – import updates via Data Loader:
- Export the existing Account records with their Salesforce IDs
- Build a CSV with two columns: the child Account’s Salesforce ID, and the parent Account’s Salesforce ID in the ParentId field
- Use Data Loader to Update the child Account records, setting the ParentId field
- Verify in Salesforce that the hierarchy view shows the correct structure after import
Step 5: Configure Roll-Up Summary Fields (Optional)
Standard Salesforce Roll-Up Summary fields only work on master-detail relationships – the Parent Account / Child Account relationship is a lookup (not master-detail), which means standard Roll-Up Summary fields cannot aggregate child Account data to the parent automatically.
Workarounds for parent-level rollup reporting:
- Custom rollup via Flow: A scheduled or record-triggered Flow queries all child Account records under a parent and calculates the sum of a field (total ARR, total pipeline) and writes it to a custom field on the parent Account. Requires admin configuration but achieves a real-time rollup without code
- DLRS (Declarative Lookup Rollup Summaries): A popular free AppExchange tool that adds rollup summary functionality to lookup relationships – enabling Roll-Up Summary fields on the Parent Account over child Accounts without code
- Salesforce Reports with grouping: Build a report that includes both parent and child Account records with the Parent Account field as a grouping column – aggregating totals by corporate family without modifying the data model
- CRM Analytics: Einstein CRM Analytics can traverse account hierarchy relationships in datasets – appropriate for enterprise-scale hierarchy reporting with multiple levels
Account Hierarchy and Territory Management
In enterprise sales organisations with formal Territory Management (available on Enterprise and above), account hierarchy intersects with territory assignment. Configuration decisions to make:
- Global accounts with a dedicated global account manager: The parent Account and all child Accounts are assigned to the global account manager’s territory – ensuring coordinated coverage. Territory Management rules can automatically assign all child Accounts to the same territory as the parent
- Regional coverage teams: Regional subsidiaries are covered by the regional territory rep, with the global account manager as the Account Team member for coordination. The parent Account sits in the global account manager’s territory; child Accounts are distributed across regional territories
D&B and ZoomInfo Account Hierarchy Data
For organisations managing hundreds of enterprise accounts, manually building accurate account hierarchies is impractical. Third-party data enrichment tools provide corporate hierarchy data from authoritative sources:
- Dun & Bradstreet (D&B Direct for Salesforce): D&B’s DUNS number system tracks corporate family relationships globally. D&B Direct for Salesforce can automatically populate the Parent Account field and create missing parent entity records based on D&B’s corporate hierarchy data – the most comprehensive source for multinational corporate structures
- ZoomInfo for Salesforce: ZoomInfo enrichment populates company hierarchy data including subsidiary relationships, primary parent company, and ultimate parent – enabling automatic hierarchy population for existing Account records
- Clearbit Enrich: Provides parent company data for enriching Account records, though with less global coverage depth than D&B for complex multinational hierarchies
The best hierarchy setup is the one that reflects how the company is actually structured. If the relationships are unclear, the CRM becomes harder to manage.
The best hierarchy setup is the one that reflects how the company is actually structured. If the relationships are unclear, the CRM becomes harder to manage.
The best hierarchy setup is the one that reflects how the company is actually structured. If the relationships are unclear, the CRM becomes harder to manage.
The best hierarchy setup is the one that reflects how the company is actually structured. If the relationships are unclear, the CRM becomes harder to manage.
Common Account Hierarchy Mistakes
- Multiple records for the same entity: Creating a new Account for “Acme UK” when “Acme United Kingdom” already exists – breaking the hierarchy by duplicating the leaf node. Deduplication before hierarchy building is essential
- Circular references: Salesforce prevents direct circular references (Account A is parent of Account B, Account B is parent of Account A) but multi-level circular references can occur if hierarchy data is imported without validation
- Using Account Hierarchy for non-corporate relationships: Account Hierarchy is designed for corporate parent-subsidiary structures. Partner relationships, referral networks, and customer-reseller relationships should use custom relationship objects or the Partner Account relationship type – not the Parent Account field
- Not updating hierarchy when acquisitions occur: When a prospect account is acquired by an existing customer account, the acquired company’s Salesforce Account should be linked as a child of the acquiring customer’s parent Account – failing to update hierarchy after M&A activity creates broken hierarchy data over time
Salesforce Account Hierarchy: Advanced Configuration for Enterprise Accounts
Fix: Rolling Up Opportunity Revenue Across Account Hierarchies
One of the most valuable aspects of account hierarchies is the ability to report on total pipeline or revenue across an entire corporate family. Salesforce does not roll up opportunity revenue through account hierarchies automatically, but this can be achieved through custom reports using the “Accounts in Hierarchy” report type available in some editions, or through Roll-Up Summary Fields on custom parent account relationships. For complex multi-level hierarchies, reporting formulas or custom code solutions provide the most flexibility.
Fix: Structuring Account Teams Across Parent and Child Accounts
When an enterprise account has a global account manager and regional account managers for subsidiaries, determining who owns which relationships becomes complex. Salesforce Account Teams allow multiple users to be associated with an account in different roles (Account Manager, Technical Advisor, Support Lead), each with customized read/write access. By assigning account team members at both the parent and child account levels and configuring appropriate sharing rules, large account teams can maintain clear ownership while ensuring visibility across the entire account hierarchy.
How do you set up account hierarchy in Salesforce?
Account hierarchy in Salesforce is created by populating the Parent Account field on child account records. Navigate to a subsidiary company’s account record, click Edit, find the Parent Account field, and use the lookup to select the parent company. Repeat this process for all subsidiary accounts. There is no separate configuration step; the hierarchy view automatically generates based on these parent-child relationships. For bulk setup, you can use Data Loader to mass-update the ParentId field on account records using a CSV file.
Can Salesforce account hierarchy go multiple levels deep?
Yes, Salesforce account hierarchies can go multiple levels deep, supporting complex multi-tier corporate structures such as Global Parent > Regional Holding > Country Entity > Business Unit > Department. The Account Hierarchy view displays the complete tree regardless of depth. However, rollup reports and Roll-Up Summary Fields only aggregate one level at a time natively, so reporting across deeply nested hierarchies may require custom reports, formulas, or Apex-based solutions for accurate multi-level aggregation.
What is the difference between account hierarchy and contact hierarchy?
Account Hierarchy represents corporate ownership relationships between companies (parent and subsidiary accounts). Contact Hierarchy (or contact reporting structure) represents the management hierarchy between individual people within a company, typically managed through the Reports To field on the Contact object. A good enterprise account strategy uses both: Account Hierarchy to model the corporate structure and contact reporting relationships to understand who reports to whom within each account, enabling more effective multi-threaded sales strategies.
Challenge: Managing Complex Enterprise Accounts with Multiple Subsidiaries
Global enterprise accounts often consist of dozens of subsidiary companies, each with its own purchasing authority, CRM relationships, and revenue potential. Without a proper account hierarchy, your Salesforce data has no way to represent these parent-child relationships, making it impossible to understand total enterprise revenue across a family of companies. Salesforce’s built-in Account Hierarchy feature, accessed through the Parent Account field, allows you to build multi-level trees representing global ultimate parent, domestic ultimate parent, and individual subsidiaries.