Account hierarchies in Dynamics 365

By Emil Björk · Microsoft business apps consultant, Gothenburg

How Dynamics 365 models corporate parent-subsidiary relationships — account hierarchy field, hierarchy charts, security, and reporting roll-up.

Reviewed August 20262 min read · 554 wordsPublished Updated
On this page (9)

For B2B sellers, the account is rarely flat — customers are organisations with parent companies, subsidiaries, divisions, regional offices, and operating units. Dynamics 365 models these relationships through account hierarchies, with reporting, security, and visualisation that respects the corporate structure.

The hierarchy field

Each Account record carries a Parent Account lookup. Setting Parent Account on a subsidiary creates the hierarchy edge — Subsidiary → Parent. Parent accounts can themselves have parents, building a tree of arbitrary depth.

Hierarchy charts

Dynamics 365 ships built-in hierarchy visualisation for any record type with a hierarchical relationship. On an account form, the hierarchy chart shows the current account in context — parents above, children below, with key fields displayed per node. Clicking a node navigates to that record. This is the standard way sellers see "who else in this organisation are we engaged with".

Roll-up reporting

Several aggregation patterns operate over the hierarchy:

  • Roll-up rollup columnsDataverse rollup columns can compute across the hierarchy. A "Total opportunity revenue from this account and all descendants" column gives executives a single number per top-level account, summed from every child.
  • Aggregate views — saved views can include child records, e.g. "All open opportunities for this account family".
  • Forecasting — sales forecasting can aggregate by account hierarchy, so a Global Account Director sees pipeline across every subsidiary they touch.

Security through hierarchy

Hierarchy security is an additional scope dimension on Dataverse security roles:

  • Manager hierarchy security — managers see records owned by their direct or indirect reports.
  • Position hierarchy security — uses configured position hierarchies for the same purpose.

Account hierarchy itself doesn't drive security directly (unlike manager hierarchy); accounts under different owners remain owner-scoped. But custom security configurations can route access based on account hierarchy if business logic demands.

Sales motions

Account hierarchies enable several sales motions:

  • Global account management. Strategic accounts with global reach get a single Global Account Director who sees every subsidiary's opportunities, contracts, cases, and service. Subsidiary-level sellers continue managing day-to-day; the GAD coordinates at the parent level.
  • Cross-sell and up-sell. Knowing the full corporate footprint reveals expansion opportunities — three subsidiaries already buy Product A; the fourth subsidiary hasn't, suggesting a target.
  • Risk view. A case escalation at one subsidiary surfaces to the global account team to manage the relationship beyond the local context.

Marketing implications

Marketing campaigns can target by hierarchy — campaign to all subsidiaries of strategic parent accounts. Customer Insights – Journeys segments respect the hierarchy.

Customer Service implications

Cases on subsidiaries can roll up to a parent-level account view, so a parent account manager sees aggregated service issues across the family — useful for QBRs and account-health reviews.

Limits

Account hierarchies are simple parent-child trees. Complex matrix organisations (a subsidiary belongs to two parents through different functions) are awkward; companies that need this typically use custom relationship modelling — a Connected Accounts custom table or related-record approach — alongside the standard hierarchy.

Common pitfalls.

  • Incomplete data — only some subsidiaries have Parent Account set. Hierarchy views misrepresent the truth.
  • Wrong direction — parent and child reversed; reports show wrong totals.
  • Mergers and acquisitions — when a parent acquires another company, hierarchy needs updating; often forgotten.
  • Over-deep hierarchies — 10-level deep trees become hard to navigate. Flatten where business logic doesn't require depth.

Operational reality

A clean account hierarchy is a leverage point — the same data drives sales reporting, marketing segmentation, service routing, and finance reporting. Invest in keeping it current.

Related guides

Browse every guide in Customer Engagement or just Dataverse platform.

Was this helpful?

Signals which guides land and which need work. No account, no comment box — corrections go through the contact page.

Spot something wrong or want a topic covered? Send a correction or a topic request — both are welcome.