- Working definition: Account Hierarchy needs a published definition, population, evidence source, owner, operating consequence, effective date, and review condition.
- Business purpose: Account Hierarchy makes one corporate-structure decision inspectable instead of allowing the current assignment or loudest stakeholder to become the rule.
- Mechanics: Publish the covered population, evidence standard, decision owner, approver, effective timing, exception path, and review cadence in advance.
- Operating context: Use Account Hierarchy during planning, scenario review, activation, and material in-year changes while keeping current and proposed states separate.
- Practical test: Apply Account Hierarchy to one disputed account and distinguish a data correction, a policy exception, and a proposed change to the standard.
- BoogieBoard doctrine: Publish the Account Hierarchy standard before reviewing assignments so its tradeoffs remain visible and the approved sequence cannot be reverse-engineered from preferred outcomes.
What is Account Hierarchy?
An Account Hierarchy represents governed relationships among parent companies, subsidiaries, branches, brands, locations, portfolio companies, and other related account records, with the definition, owner, evidence, and review timing published before assignments are approved. It becomes operational when the population, source evidence, owner, and consequence are explicit enough for another reviewer to reproduce.
Start Account Hierarchy with a precise statement of the decision it governs. In the corporate structures context, that decision should translate legal and commercial relationships into account hierarchies and coverage rules without confusing ownership with selling responsibility. Its definition should exclude adjacent decisions that use different evidence, owners, or consequences.
A complete Account Hierarchy definition names the covered population, evidence standard, decision owner, approver, effective timing, exception criteria, expiration or review condition, and the operating consequence of the decision.
Review Rules of Engagement, Account Definition, Credit Allocation, Data Dispute with Account Hierarchy. Those concepts may supply inputs, constrain the decision, or consume its output, but none should silently inherit the same definition.
What Account Hierarchy includes
Start with legal entities, ultimate parents, operating parents, locations, brands, contracts, buying authority, and local relationship evidence. Record the field or policy owner, source date, transformation, comparison population, and correction path. If any required input is unavailable, mark the limitation rather than filling it with an undocumented proxy. That preserves the difference between observed evidence and planning judgment.
This policy defines how the company handles account reassignment when a merger or acquisition affects account hierarchy.
Apply Account Hierarchy to the complete affected population before reviewing individual preferred outcomes. Preserve the current state, classify each challenge as a correction, exception, or policy proposal, and record the approved future treatment with its effective date and decision history.
The decision record for Account Hierarchy should retain the request, governed evidence, policy result, reviewer, approver, effective date, and any expiration or reconsideration condition. Report corrections, exceptions, and policy changes separately. Combining them in one exception count hides whether the underlying problem is data quality, inconsistent administration, or an outdated standard. Before approval, ask a reviewer outside the original design team to reproduce the Account Hierarchy result or decision from that retained evidence.
A practical Account Hierarchy example
Consider a corporate family with an ultimate parent, several operating companies, and local buying locations. The planning team maps the legal relationships first, then documents how Account Hierarchy changes commercial coordination, local ownership, named-account treatment, and credit without assuming that every related record belongs to one seller.
Reviewers identify where contracts are signed, where buying authority sits, which relationships are global or local, and which records share a provider identifier. They preserve the hierarchy evidence separately from the coverage rule so a corrected parent relationship does not silently rewrite sales policy.
The future scenario shows both the family-level view and each account-level assignment. An approved exception names its reason and approver. The model is activated only when managers can explain why the hierarchy is represented one way and why responsibility may follow a different, explicitly governed path.
How Account Hierarchy relates to territory planning
Account Hierarchy may vary by segment, role, customer motion, geography, product, and planning stage when the business reason is published. Each population still needs an internally consistent standard and a clear explanation of why its treatment differs.
Test the rule against ordinary cases, edge cases, vacancies, and material in-year changes. Review both the summary outcome and underlying account roster. The standard should remain usable when the original planner is no longer present to explain it.
Review Escalation Path, DACI, Project Hub, Global vs Local Ownership alongside Account Hierarchy. Preserve their distinct definitions and show the dependency between them so a correction to evidence does not quietly become a policy exception or assignment preference.
Account Hierarchy operating rules and pitfalls
The primary Account Hierarchy failure is forcing every parent, subsidiary, branch, or portfolio company into one ownership rule merely because the records are related. Prevent it by publishing the definition and decision sequence before individual assignments are reviewed, then evaluate proposed changes across the full affected population.
Another failure is confusing a correction with an exception under Account Hierarchy. A correction changes governed evidence; an exception accepts the evidence but authorizes different treatment for a documented reason, approver, and period.
Review Account Hierarchy on the formal policy cadence and after material exceptions. Monitor unresolved requests, recurring exception reasons, expired approvals, and differences between the approved and live states; repeated exceptions may indicate that the published standard needs revision.
In practice with BoogieBoard
For Account Hierarchy, the relevant BoogieBoard workflow preserves the decision, evidence, approver, effective state, and later audit trail. BoogieBoard records scenario decisions, comments, and territory changes so teams can understand who changed the model, when it changed, and what evidence supported the decision. Reviewers can compare the approved scenario with the current state, classify feedback as a correction or exception, and preserve the account-level result before activation. That history matters when a seller, manager, or operator later asks why an account moved or why a policy was applied differently in a documented case.
