Account Hierarchy Management: Parent-Child Organizations in CRM

A sales rep closes a deal with the Houston office of a Fortune 500 company. Three months later, a different sales rep pursues the same company's Dallas office as a brand-new prospect, unaware of the existing relationship. The Houston deal's pricing, terms, and lessons learned are invisible. The company looks disorganized, the sales effort is duplicated, and the customer loses confidence.

This happens every day in B2B companies that manage accounts as flat contact lists instead of hierarchical organizations. In enterprise B2B, the customer is not a person or even a single company --- it is an organizational structure with parent companies, subsidiaries, divisions, and locations, each with their own contacts, requirements, and ordering patterns.

Key Takeaways

• B2B accounts are organizational hierarchies, not flat contacts --- your CRM must model parent-child relationships accurately
• Consolidated billing at the parent level while maintaining separate ordering at the subsidiary level is the most common multi-entity requirement
• Territory assignment should follow the account hierarchy, not individual contacts, to prevent duplicate coverage
• Account health scoring at the parent level aggregates subsidiary data to give a true picture of the total relationship

---

Understanding Account Hierarchies

B2B Organization Structures

B2B customers come in several structural patterns, each requiring different CRM modeling.

| Structure | Example | Complexity | |-----------|---------|------------| | Single entity | Local manufacturer, one location | Low | | Multi-location | Regional distributor, 5 warehouses | Medium | | Parent-subsidiary | Holding company with 3 operating companies | Medium-High | | Franchise | Franchisor with 200 franchisees | High | | Conglomerate | Multi-industry corporation with divisions | Very High | | Joint venture | Two companies, shared entity | Special case |

Example: Account Hierarchy

Consider a mid-market manufacturing conglomerate.

| Level | Entity | Role | Location | |-------|--------|------|----------| | L0 (Ultimate Parent) | Apex Industries Holdings | Corporate HQ, master terms | New York | | L1 (Subsidiary) | Apex Chemicals Inc. | Chemical manufacturing division | Houston | | L1 (Subsidiary) | Apex Plastics Corp. | Plastics manufacturing division | Detroit | | L1 (Subsidiary) | Apex Distribution LLC | Distribution and logistics | Chicago | | L2 (Branch) | Apex Chemicals - Gulf Plant | Production facility | Beaumont, TX | | L2 (Branch) | Apex Chemicals - East Plant | Production facility | Charlotte, NC | | L2 (Branch) | Apex Plastics - Plant 1 | Production facility | Detroit | | L2 (Branch) | Apex Distribution - West DC | Distribution center | Phoenix | | L2 (Branch) | Apex Distribution - East DC | Distribution center | Atlanta |

In this structure, pricing might be negotiated at the L0 level, orders placed at the L1 level, and shipments delivered to L2 locations. The CRM must model all of these relationships and support different workflows at each level.

---

Modeling Hierarchies in Odoo

Parent Company Configuration

Odoo's Contacts module natively supports parent-child company relationships through the "Company" field on contact records. A contact can be linked to a parent company, creating a hierarchical structure.

Configuration steps:

1. Create the parent company as a Company-type contact with all master data (credit terms, pricelist, payment terms)
2. Create subsidiaries as Company-type contacts with the parent company in the "Company" field
3. Create contacts as Individual-type contacts linked to their respective company
4. Configure inheritance --- decide which fields (pricing, terms, credit) inherit from parent vs. are set independently

Field Inheritance Strategy

Not every field should inherit from the parent. Define your inheritance policy explicitly.

| Field | Inherit from Parent? | Rationale | |-------|---------------------|-----------| | Pricelist | Yes (default) | Negotiated at corporate level | | Payment terms | Yes (default) | Agreed at corporate level | | Credit limit | No (set per entity) | Risk varies by subsidiary | | Shipping addresses | No (entity-specific) | Each location has own addresses | | Contacts | No (entity-specific) | Different people at each entity | | Tax settings | No (entity-specific) | Tax jurisdiction varies | | Currency | No (entity-specific) | International subsidiaries | | Sales rep assignment | Configurable | Depends on territory model |

Multi-Entity Contact Management

Each entity in the hierarchy has its own contacts with distinct roles.

| Entity | Contact | Role | Portal Access | |--------|---------|------|---------------| | Apex Holdings | Sarah Chen | VP Procurement | Admin (all entities) | | Apex Holdings | James Wright | CFO | Invoice viewer (all entities) | | Apex Chemicals | Mike Torres | Plant Manager | Buyer (Chemicals only) | | Apex Chemicals | Lisa Park | Purchasing Agent | Buyer (Chemicals only) | | Apex Plastics | Dan Brown | Operations Director | Buyer (Plastics only) | | Apex Distribution | Amy Liu | Logistics Manager | Viewer (Distribution only) |

---

Consolidated vs. Distributed Billing

Billing Models

The billing model defines who receives invoices and how they are organized.

| Model | Invoice To | Payment By | Use Case | |-------|-----------|------------|----------| | Consolidated | Parent company | Parent company | Centralized AP department | | Distributed | Each subsidiary | Each subsidiary | Independent divisions | | Consolidated with detail | Parent company (summary) | Parent company | Centralized with subsidiary breakdown | | Split | Varies by order type | Varies | Hybrid organizations |

Implementing Consolidated Billing in Odoo

Consolidated billing in Odoo requires configuring the "Invoice Address" on sales orders to point to the parent company while the "Delivery Address" points to the subsidiary or branch location. This creates invoices addressed to the parent with delivery details for the actual receiving location.

For a holding company with 3 subsidiaries each placing 20 orders per month, consolidated billing reduces invoice volume from 60 invoices to a single consolidated statement, dramatically simplifying accounts payable on both sides.

Statement Reconciliation

When billing is consolidated, the parent company's AP team needs a statement that maps each charge to the originating subsidiary. Odoo's customer statement can be configured to group transactions by subsidiary, showing:

• Subsidiary name and reference
• Order numbers and dates
• Line items and amounts
• Payments received and applied
• Outstanding balance per subsidiary
• Total outstanding balance

This gives the parent company the detail they need for internal cost allocation while providing a single payment point for efficiency.

---

Territory Assignment and Account Teams

Territory Models

Territory assignment determines which sales and support resources cover which accounts. In a hierarchical account structure, territories can be assigned at different levels.

| Territory Model | Assignment Level | Pros | Cons | |----------------|-----------------|------|------| | Geographic | Branch/location level | Clear boundaries, local presence | Same customer, different reps | | Account-based | Parent company level | Consistent relationship | May span geographies | | Hybrid | Parent + geographic overlay | Best of both | Complex, potential conflicts | | Industry vertical | Parent company level | Domain expertise | Geographic gaps |

Account Team Roles

Large B2B accounts require a team, not a single sales rep. Define clear roles for the account team.

| Role | Scope | Responsibilities | |------|-------|-----------------| | Strategic Account Manager | Parent company | Overall relationship, executive contact, contract negotiation | | Territory Sales Rep | Subsidiary/region | Day-to-day orders, local relationships, issue resolution | | Technical Specialist | Product-specific | Technical support, product recommendations, training | | Customer Success Manager | Parent company | Onboarding, adoption, satisfaction, retention | | Credit Analyst | Parent company | Credit assessment, limit management, collection | | Inside Sales | All levels | Order processing, quote generation, routine inquiries |

In Odoo, account team assignment can be managed through the Sales Team feature, with team members linked to specific accounts at the appropriate hierarchy level.

---

Account Health Scoring

Parent-Level Health Aggregation

Individual subsidiary metrics can be misleading. A subsidiary might have declining orders while the overall account is growing because another subsidiary is ramping up. Account health should be scored at the parent level, aggregating data from all subsidiaries.

Health Score Components

| Component | Weight | Data Source | Scoring | |-----------|--------|-------------|---------| | Revenue trend | 25% | Sales orders (12-month trend) | Growing = 10, Flat = 6, Declining = 2 | | Payment behavior | 20% | AR aging, DSO | On time = 10, Slightly late = 6, Chronic late = 2 | | Engagement | 15% | Portal logins, support tickets, meetings | High = 10, Medium = 6, Low = 2 | | Contract status | 15% | Contract dates, renewal pipeline | Renewed = 10, Upcoming = 6, At risk = 2 | | Product breadth | 10% | Distinct product categories ordered | Broad = 10, Moderate = 6, Narrow = 2 | | Support satisfaction | 10% | CSAT scores, NPS | High = 10, Medium = 6, Low = 2 | | Reference willingness | 5% | Explicit feedback | Willing = 10, Neutral = 6, Unwilling = 2 |

A score below 5.0 should trigger an account review. A score below 4.0 should escalate to management. A score below 3.0 is a churn risk requiring immediate intervention.

Practical Example

| Subsidiary | Revenue Trend | Payment | Engagement | Score | |-----------|--------------|---------|------------|-------| | Apex Chemicals | Growing (10) | On time (10) | High (10) | 10.0 | | Apex Plastics | Declining (2) | Slightly late (6) | Medium (6) | 4.7 | | Apex Distribution | Flat (6) | On time (10) | Low (2) | 6.0 | | Apex Holdings (Aggregate) | | | | 6.9 |

The aggregate score of 6.9 masks the Apex Plastics problem. The health dashboard should surface both the aggregate score and individual subsidiary scores, flagging entities below the threshold for attention.

For managing the pricing aspects of multi-entity accounts, see our guide on customer-specific pricing and tiered discounts.

For the complete B2B eCommerce strategy, see our pillar guide: The B2B eCommerce Playbook.

---

Frequently Asked Questions

How do we handle a customer that is both a buyer and a supplier?

Odoo supports dual-role contacts natively. A single company record can have both customer and vendor properties. The key is ensuring that the account hierarchy for buying and selling are modeled correctly. If Apex Chemicals buys raw materials from you and you buy specialty chemicals from them, both relationships exist on the same contact record with separate AR and AP balances.

What happens when a subsidiary changes ownership?

When a subsidiary is acquired by another company or spun off, the CRM records must be updated. In Odoo, change the parent company field on the subsidiary contact. This preserves the order history and contact data while reflecting the new ownership. Contract terms may need renegotiation, pricing may change based on the new parent's terms, and territory assignment may shift. Treat this as a managed transition with a checklist, not a simple field update.

How do we prevent duplicate accounts for the same organization?

Duplicate prevention starts at account creation. Before creating a new company record, search for existing records by company name, tax ID, domain name, and key contact names. Odoo's duplicate detection can be configured to flag potential matches during contact creation. For large organizations with many variations of their name (Apex Industries, Apex Industries Inc., Apex Industries Holdings LLC), maintain a list of known aliases on the parent record.

---

What Is Next

Account hierarchy management is the foundation of enterprise B2B relationships. Without it, every interaction is disconnected, every insight is siloed, and every opportunity to leverage the total relationship is missed.

ECOSIRE's Odoo CRM implementation includes account hierarchy configuration, territory design, and health scoring dashboards. We help B2B companies build CRM structures that reflect how their customers actually operate.

Contact us to discuss your account management challenges and see how Odoo can model your most complex customer relationships.

---

Published by ECOSIRE --- helping businesses scale with AI-powered solutions across Odoo ERP, Shopify eCommerce, and OpenClaw AI.