Multiple Hierarchies — Legal View vs. Management View in Consolidation
Every large group with more than a handful of subsidiaries eventually runs into a structural problem that spreadsheets and single-tree ERP setups cannot resolve. The statutory legal entity structure that governs how you file with the Registrar of Companies or report under IndAS 110 rarely matches how the business is actually managed. Supporting multiple hierarchies legal vs management within a single consolidation platform is what separates a workable reporting infrastructure from one that forces your team into reconciliation loops every quarter.
This is not a theoretical concern. When your CFO needs a consolidated P&L by business vertical for a board presentation on Monday, and your statutory team needs a legal entity consolidation for the same period by Wednesday, the underlying data is identical. The reporting lens is different. If your consolidation system forces you to maintain separate data sets or manually regroup numbers for each view, you are spending senior analyst hours on structural rework rather than on analysis.
Why One Hierarchy Is Never Enough
Consider a diversified Indian conglomerate with 40 subsidiaries, 8 joint ventures, and operations across 12 countries. The Companies Act, 2013 and IndAS 110 require consolidation based on control relationships, legal ownership percentages, and parent-subsidiary chains. This is the legal entity hierarchy, and it is non-negotiable for statutory filings with the MCA and for audit sign-off.
The same conglomerate, however, is managed internally along four business verticals: industrial products, financial services, consumer goods, and infrastructure. Each vertical has its own P&L owner, its own capital allocation process, and its own set of KPIs. The managing director and the board do not review performance by legal entity. They review it by vertical.
This creates three structural challenges that most finance teams at regulated enterprises face repeatedly. First, the same entity may contribute to multiple management views. A subsidiary that manufactures industrial components and also sells consumer products needs to appear in two verticals, with revenue and costs split accordingly. Second, joint ventures and associates that are equity-accounted in the legal view may need to be proportionally consolidated in the management view for a more complete picture of operational performance. Third, geographic groupings for transfer pricing analysis or regional performance reviews require yet another slicing of the same data.
When a consolidation tool supports only one tree structure, the finance team ends up maintaining parallel workbooks, manual mapping sheets, and reconciliation trackers to produce each view. Every quarter, this process consumes days of effort and introduces the risk of mismatched totals between the statutory and management reports.
The Legal Entity View
The legal entity hierarchy is the foundation of any consolidation exercise. It mirrors the ownership structure as recorded in shareholding agreements, board resolutions, and filings with regulatory bodies like the MCA, SEBI, or the RBI (for banking and NBFC groups). Each node in this tree represents a legal entity, and the edges represent ownership or control relationships with defined holding percentages.
Under IndAS 110, consolidation follows control, which means the hierarchy must accurately capture which entities are subsidiaries (controlled), which are joint ventures (joint control under IndAS 111), and which are associates (significant influence under IndAS 28). The holding percentages at each level drive the elimination of intercompany transactions, the computation of non-controlling interest (NCI), and the application of equity method accounting for associates.
For a group like a large public sector bank or a listed NBFC holding company, the legal hierarchy can run six or seven levels deep. Intermediate holding companies, step-down subsidiaries, and special purpose vehicles all need to be placed correctly in the tree. An error in hierarchy placement, say classifying a step-down subsidiary under the wrong intermediate holding company, cascades through the elimination and NCI calculations and produces a consolidated balance sheet that will not survive audit scrutiny.
The legal entity view also needs to accommodate changes over time. Acquisitions, divestments, mergers under Section 230-232 of the Companies Act, and changes in holding percentages all alter the tree structure. A consolidation system that supports defining and modifying consolidation hierarchies with drag-and-drop flexibility allows the finance team to reflect these changes in minutes rather than rebuilding reports from scratch.
What the Legal View Must Capture
| Element | Purpose | Regulatory Reference |
|---|---|---|
| Parent-subsidiary chain | Full consolidation with NCI | IndAS 110 / IFRS 10 |
| Joint ventures | Equity method (or proportionate for management) | IndAS 111 / IFRS 11 |
| Associates | Equity method accounting | IndAS 28 / IAS 28 |
| Holding percentages | NCI computation, elimination logic | IndAS 110, Schedule III |
| Intermediate holding companies | Step-down consolidation | Section 129(3), Companies Act 2013 |
The Management or Business Unit View
The management hierarchy reorganizes the same set of entities (and sometimes sub-entity segments) along lines that reflect how the business is actually run. For a group like Godrej or Kirloskar, this might mean grouping entities by product category, by customer segment, or by strategic business unit.
What makes this hierarchy distinct from the legal view is that it often cuts across ownership boundaries. A single legal entity may house three different business lines, each of which belongs to a different management vertical. The management view needs the ability to split that entity’s trial balance data across verticals, either through segment tagging at the account level or through allocation rules defined in the consolidation system.
Consider a scenario where a listed Indian auto components manufacturer has a subsidiary in Germany. In the legal view, this subsidiary sits under an intermediate European holding company. In the management view, the subsidiary’s OEM supply business rolls up under the “Automotive” vertical, while its aftermarket distribution business rolls up under the “Aftermarket” vertical. The same trial balance, the same underlying numbers, viewed through a completely different lens.
This is where the concept of multiple hierarchies legal vs management becomes operationally critical. The finance team should not need to re-import data, create duplicate entities, or maintain separate consolidation files. The system should allow one data set to be viewed through multiple tree structures, each producing its own consolidated outputs. eMerge supports exactly this architecture, allowing finance teams to define parallel hierarchies that draw from the same imported trial balances and produce distinct consolidated reports for each view.
Management reporting requirements also differ from statutory ones in granularity and format. While statutory and management reporting share a common data foundation, management reports often need additional KPIs, non-financial metrics (production volumes, headcount, capacity utilization), and custom groupings that do not appear in Schedule III or IndAS disclosure formats. A consolidation platform that supports statistical entries alongside financial data enables the management view to be richer and more decision-relevant.
The Geographic View
Geographic hierarchies group entities by country, region, or regulatory jurisdiction. For Indian multinationals with operations in Southeast Asia, Europe, and the Americas, this view answers questions that neither the legal nor the management hierarchy can address on its own. How much revenue does the group earn from APAC? What is the EBITDA margin for European operations? What is the net asset exposure in countries with volatile currencies?
Transfer pricing compliance under Section 92 of the Income Tax Act and OECD guidelines adds another dimension. Country-by-country reporting (CbCR) requires data organized by tax jurisdiction, which may not align with either the legal or management hierarchy. An entity incorporated in Singapore but managed from Mumbai, with revenues sourced from customers in Thailand, touches three geographic nodes depending on which question you are answering.
The geographic view also intersects with currency translation. When entities are grouped by region, the consolidated report for that region needs currency translation from each entity’s functional currency to the group’s presentation currency, with Foreign Currency Translation Reserve (FCTR) computed and tracked at the regional sub-consolidation level. eMerge handles multi-currency translation with configurable rate types (closing, average, historical) and automatic FCTR computation, which makes geographic sub-consolidations accurate without manual intervention.
Typical Geographic Hierarchy for an Indian Multinational
| Level | Example Nodes |
|---|---|
| Group (Global) | XYZ Group — INR presentation |
| Region | India, Europe, APAC, Americas |
| Country | India, Germany, UK, Thailand, Singapore, USA, Brazil |
| Entity | Individual legal entities within each country |
A finance controller reviewing the APAC region’s performance can drill down from the regional consolidated P&L to the Thailand subsidiary’s stand-alone numbers, all within the same system, without switching between workbooks or requesting data from a local team.
The Segment-Based View
IndAS 108 (Operating Segments) requires listed companies to disclose segment information based on the internal reports that the Chief Operating Decision Maker (CODM) regularly reviews. This means the segment view is not a discretionary MIS exercise. It is a mandatory disclosure that must reconcile with the consolidated financial statements.
Segment reporting creates unique consolidation challenges. Segment revenue, segment profit, segment assets, and segment liabilities must be reported with inter-segment eliminations. If Entity A sells goods to Entity B, and both entities belong to the same operating segment, that transaction must be eliminated within the segment. If they belong to different segments, the inter-segment revenue must be disclosed and then eliminated at the group level.
For groups where segments cut across legal entities, the consolidation system needs to tag data at the account or transaction level with segment identifiers, and then consolidate within each segment before producing the group-level elimination. eMerge supports segment-level P&L, segment assets, and segment liabilities with inter-segment adjustments, enabling finance teams to produce IndAS 108 compliant disclosures directly from the consolidation process rather than assembling them manually after the fact.
The segment view also feeds into MIS, budgeting, and performance analysis workflows. When budgets are set by segment, variance analysis against actuals requires the consolidation system to produce segment-level actuals that match the segment-level budgets. Consistency in hierarchy and account grouping between the budgeting module and the actuals consolidation is essential for meaningful variance reporting.
How eMerge Supports Multiple Tree Structures
The practical challenge with maintaining multiple hierarchies is avoiding data duplication and reconciliation overhead. If each hierarchy requires a separate data import, a separate set of mapping rules, and a separate consolidation run, the effort multiplies with each additional view, and the risk of discrepancies between views increases proportionally.
eMerge addresses this by allowing multiple tree structures to be defined over a single data layer. The trial balance for each entity is imported once, in the entity’s local currency, and mapped once to the common chart of accounts. Each hierarchy then references the same underlying data, with its own consolidation rules, elimination logic, and output reports.
How This Works in Practice
The Hierarchy Manager in eMerge allows administrators to define N-level deep tree structures using a drag-and-drop interface. A legal hierarchy with the parent company at the top, intermediate holding companies at the next level, and operating subsidiaries below can coexist with a management hierarchy that groups the same entities by business vertical. Adding a new entity to the group, whether through acquisition or incorporation, requires placing it in each relevant hierarchy, a task that takes minutes rather than hours.
Holding percentages can differ between hierarchies where the reporting logic requires it. In the legal view, a 60% subsidiary is fully consolidated with 40% NCI. In a management view designed for operational performance analysis, the same entity might be shown at 100% contribution to its vertical, with NCI treated as a below-the-line adjustment. The system accommodates these differences without requiring duplicate data entry.
The corporate lock feature ensures that once data for a period is finalized for consolidation, no entity can modify its trial balance or journal entries without administrator authorization. This lock applies across all hierarchies, ensuring that the legal view and the management view are always based on the same frozen data set. Any post-lock adjustment is tracked with a complete audit trail, maintaining integrity across all views simultaneously.
Comparison of Hierarchy Types Supported
| Hierarchy Type | Primary Use Case | Typical User | Regulatory Driver |
|---|---|---|---|
| Legal Entity | Statutory consolidation, audit, regulatory filing | Statutory reporting team, auditors | IndAS 110, Companies Act 2013, SEBI LODR |
| Management / Business Unit | Internal performance review, capital allocation | CFO, business unit heads, board | Internal governance |
| Geographic | Regional performance, CbCR, currency exposure | Tax team, treasury, regional heads | OECD CbCR, transfer pricing rules |
| Segment | IndAS 108 disclosures, CODM reporting | Statutory team, CODM | IndAS 108 / IFRS 8 |
The ad-hoc report generator within eMerge further extends this flexibility. Once hierarchies are defined and data is consolidated, custom reports can pull figures across hierarchies, enabling cross-cutting analyses such as “revenue by segment within APAC” or “operating margin by business vertical for Indian entities only.” These reports are designed by the finance team directly, without IT involvement, which keeps the turnaround time for new analytical requirements in hours rather than weeks.
Getting the Architecture Right from Day One
The decision to support multiple hierarchies is best made at the time of initial implementation rather than retrofitted after the first statutory cycle. During implementation, the finance team works with eMerge’s team of chartered accountants and technical specialists to define all required hierarchies, map the common chart of accounts, and validate that each hierarchy produces outputs matching previously published reports. This validation, done to the last penny against prior period published numbers, ensures that every hierarchy is structurally sound before going live.
Groups that are in the process of evaluating their consolidation infrastructure, or those finding that their current setup cannot accommodate the multiple views that the board, auditors, and regulators each require, would benefit from seeing how multiple hierarchies work in practice within eMerge. A structured walkthrough using your own group structure and a past period’s data is the most efficient way to assess fit. You can schedule a discussion with the eMerge team here to explore how parallel hierarchies can be configured for your specific group structure and reporting requirements.
