Statutory vs. Management Reporting: Handling Both in One System
Every group finance function operates under a dual mandate. On one side, regulators like SEBI, the MCA, and tax authorities demand statutory reporting in prescribed formats, with defined timelines and zero tolerance for deviation. On the other side, the board and executive leadership need management reporting that reflects how the business actually operates, often cutting across legal entity boundaries. The challenge of statutory vs management reporting is not conceptual. It is structural, and it compounds with every subsidiary added to the group.
For finance controllers managing consolidation across 15, 40, or 100 entities, the question is never whether both views are necessary. The question is whether the underlying infrastructure can produce both from a single data set, without manual rework, without reconciliation gaps, and without maintaining parallel workstreams that inevitably diverge.
What Is Statutory Reporting
Statutory reporting refers to the preparation and submission of financial statements mandated by law or regulation. In India, this means compliance with the Companies Act 2013, Indian Accounting Standards (IndAS), SEBI’s Listing Obligations and Disclosure Requirements (LODR), and the specific schedules prescribed under Schedule III of the Companies Act. For banking entities, RBI guidelines add another layer. For insurance companies, IRDAI norms apply.
The defining characteristics of statutory reporting are rigidity and precision. The format is prescribed. The disclosure requirements are specific. The timelines are non-negotiable. A listed company filing consolidated financial statements must follow IndAS 110 on Consolidated Financial Statements, IndAS 28 on Associates, and IndAS 111 on Joint Arrangements, among others. There is no room for interpretation in how numbers are classified or presented.
Statutory reporting also carries audit requirements. External auditors need to trace every consolidated number back to its source, verify elimination entries, confirm minority interest computations, and validate foreign currency translation reserves. The reporting structure must therefore be auditable at every level, from the individual trial balance to the final consolidated balance sheet.
Entities That Drive Statutory Complexity
Consider a group headquartered in India with manufacturing subsidiaries in Germany and Thailand, a trading subsidiary in Dubai, and a joint venture in the United States. The Indian parent reports under IndAS. The German subsidiary prepares local statutory accounts under HGB (German GAAP) and also provides an IndAS-compliant reporting package to the parent. The Thai entity follows TFRS. Each jurisdiction has its own statutory requirements, and the parent company must consolidate all of these into a single IndAS-compliant set of financial statements for filing with the Registrar of Companies and SEBI.
This creates multiple layers of statutory obligation. Local statutory filings for each subsidiary in their respective jurisdiction. A consolidated statutory filing for the Indian parent. And potentially, if the parent is also listed on an overseas exchange, an IFRS-compliant set as well. Each layer requires its own report format, its own classification logic, and its own set of disclosures.
What Is Management Reporting
Management reporting serves an entirely different purpose. It provides the executive team and the board with information structured around how the business is managed, rather than how it is legally organized. A conglomerate with interests in chemicals, real estate, and financial services may have its legal entities organized by jurisdiction, with holding companies in Singapore and Mauritius for tax efficiency. The management view, however, cuts across these legal structures to show performance by business vertical, by product line, by geography, or by customer segment.
Management reports are not constrained by Schedule III or any accounting standard. They can include non-GAAP metrics, operational KPIs, contribution margins by segment, EBITDA by business unit, return on capital employed by division, or any other measure that the leadership team finds useful for decision-making. The format is flexible. The content is determined by what the business needs to understand about itself.
Where Management Reporting Becomes Complex in Groups
The complexity arises when management reporting must draw from the same underlying financial data as statutory reporting. A division-level P&L for the chemicals business might include revenue and costs from three different legal entities across two countries. The transfer pricing between these entities affects the statutory view (where intercompany transactions must be eliminated) differently from the management view (where the divisional head wants to see the full revenue pipeline including intercompany sales, before elimination).
Finance teams that maintain separate workstreams for statutory vs management reporting often find themselves reconciling two sets of numbers that should, in theory, tie back to the same source. The reconciliation itself becomes a time-consuming exercise, and discrepancies erode confidence in both outputs.
Why Both Are Needed Simultaneously
Regulated enterprises operating at scale cannot afford to treat statutory and management reporting as sequential activities. The board meets quarterly. SEBI filing deadlines are fixed. The CFO needs both the statutory consolidated financial statements and the management performance deck prepared from the same closing cycle, often within days of each other.
There are three structural reasons why simultaneity matters.
First, the data freshness window is narrow. Once a period is closed and trial balances are locked, the finance team has a limited window to produce all outputs before the next period’s activity begins. Any sequential approach, where statutory is completed first and management reporting follows, compresses the time available for analysis and decision-making.
Second, reconciliation between the two views is only credible when both are produced from the same data set in the same period. If management reports are produced from a slightly different cut of data, or if adjustments made during statutory finalization are not reflected in the management view, the two outputs will diverge. This divergence becomes a governance risk when audit committees ask why the management discussion section of the annual report tells a different story from the financial statements.
Third, regulators themselves are moving toward requiring greater alignment. SEBI’s LODR requirements around segment reporting under IndAS 108 require that operating segments be identified based on how the Chief Operating Decision Maker (CODM) reviews performance. This means the management view is itself a regulatory input. The distinction between statutory and management reporting is not always clean.
Different Hierarchies for Different Views: The Structural Solution
The most effective way to handle statutory vs management reporting from a single data set is to maintain multiple organizational hierarchies. A single hierarchy, typically the legal entity structure, is insufficient for groups where management accountability does not follow legal ownership lines.
Legal Entity Hierarchy
This is the hierarchy that mirrors the corporate structure as filed with the Registrar of Companies. Parent company at the top. Subsidiaries, joint ventures, and associates arranged by ownership percentage. This hierarchy drives the statutory consolidation, including minority interest computation, goodwill recognition, and elimination of intercompany balances.
Management Hierarchy
This hierarchy reflects how the business is actually managed. It might group entities by business vertical (chemicals, real estate, financial services), by geography (India, EMEA, Americas), or by function (manufacturing, distribution, shared services). A single legal entity might appear in multiple management hierarchies if its operations span more than one segment.
For a group like the Kalyani Group or Dalmia Group, where the corporate structure involves multiple holding layers and cross-holdings, the ability to define and maintain separate hierarchies for different reporting purposes is not a convenience. It is a structural requirement for producing meaningful management information without distorting the statutory consolidation.
How eMerge Handles Multiple Hierarchies
eMerge allows finance teams to define N-level deep tree structures with drag-and-drop hierarchy management. Multiple hierarchies can coexist within the same system, each serving a different reporting purpose. The underlying trial balance data is entered once. The system then consolidates along whichever hierarchy is selected, applying the appropriate consolidation rules (full consolidation, proportionate consolidation, equity method) based on the relationships defined in each tree.
This means the statutory consolidation follows the legal entity hierarchy with prescribed elimination and NCI rules, while the management view follows a business-unit hierarchy with different aggregation logic. Both outputs trace back to the same source data, eliminating reconciliation gaps.
Custom Report Generator: Producing Both Views Without IT Dependency
A common bottleneck in producing management reports is the dependency on IT teams or external consultants to build new report formats. When the CFO asks for a new cut of data, say EBITDA by geography excluding one-time restructuring costs, the finance team should not need to raise a change request ticket and wait two weeks.
eMerge includes an ad-hoc report generator that allows finance users (not IT staff) to design custom reports by pulling figures from any report already defined in the system. This means a finance controller can create a new management report format, map it to the appropriate line items, and generate the report immediately. No coding. No external support. The report can reference figures from the statutory balance sheet, the consolidated P&L, segment reports, or any combination thereof.
For MIS and performance analysis across the group, this capability transforms the speed at which finance teams can respond to leadership requests. A new segment view, a revised KPI dashboard, a board-ready comparison of actuals against budget, all of these become same-day deliverables rather than multi-week projects.
How eMerge Supports Both Statutory and Management Reporting
The architecture of eMerge is designed around the premise that statutory and management reporting are two outputs from a single consolidation infrastructure. The following table summarizes how specific capabilities map to each reporting requirement.
| Capability | Statutory Reporting | Management Reporting |
|---|---|---|
| Multiple Hierarchies | Legal entity structure for IndAS/IFRS consolidation | Business unit, geography, or segment-based structures |
| Multiple GAAP Formats | IndAS, IFRS, Local GAAP as required by jurisdiction | Custom formats aligned to internal KPIs |
| Common Report Format | Schedule III compliant balance sheet and P&L | Division-level or segment-level P&L in any format |
| Intercompany Elimination | Full elimination per IndAS 110 | Selective elimination or gross-up views as needed |
| Currency Translation | FCTR computation per IndAS 21 | Management rate or budget rate translation for variance analysis |
| NCI Computation | Automated per ownership percentage | Optional, depending on management view requirements |
| Notes to Accounts (Noteify) | Columnar and textual notes per disclosure requirements | Custom commentary and analysis notes |
| Ad-hoc Report Generator | Audit-ready schedules and disclosure formats | Any custom format designed by finance team |
| Budget vs. Actual | Not typically required for statutory filing | Variance analysis at entity, segment, or cost center level |
| Statistical/Non-Financial Data | Required for certain disclosures (e.g., employee count) | Operational KPIs, volumes, capacity utilization |
Multi-GAAP as a Bridge Between Statutory and Management Views
For groups reporting under multiple frameworks, eMerge’s multi-GAAP capability serves as a natural bridge. A subsidiary that prepares local statutory accounts under Thai GAAP and also submits an IndAS reporting package to the Indian parent does not need to maintain two separate systems or two separate data entry processes. The mapping layer within eMerge handles the translation from local chart of accounts to group chart of accounts, and from local GAAP classification to IndAS classification.
This same mapping infrastructure supports management reporting. If the management view requires a different classification, say grouping R&D costs separately from general overheads even though the statutory format does not require this split, the mapping can accommodate it without altering the underlying trial balance data.
Corporate Lock and Data Integrity Across Both Views
One concern that finance controllers rightly raise is data integrity. If both statutory and management reports are produced from the same system, how do you ensure that a management adjustment does not inadvertently affect the statutory consolidation?
eMerge addresses this through its corporate lock mechanism and role-based access controls. Once the administrator locks company data for a period, no changes can be made without explicit authorization. Journal entries and regrouping entries are tagged to specific reporting purposes, ensuring that a management reclassification does not flow through to the statutory view unless explicitly directed to do so. The full audit trail captures every entry, every change, and every user action, providing the traceability that external auditors require.
The Practical Outcome for Finance Teams
When statutory vs management reporting is handled within a single system, the finance team’s workflow changes fundamentally. The quarter-end process moves from “close the books, produce statutory reports, then spend another week rebuilding the same data into management formats” to “close the books, run both outputs simultaneously, spend the time on analysis instead of reconciliation.”
For a group with 30 entities across five countries, this can mean the difference between a 15-day close cycle and an 8-day close cycle. The reconciliation effort between statutory and management views drops to near zero because both are derived from the same locked data set. Audit queries are answered faster because drill-downs trace from consolidated numbers to individual trial balance lines. And when the board asks for a new cut of data mid-quarter, the finance team can deliver it the same day.
This is the infrastructure that eMerge provides. If your organization is managing statutory and management reporting through parallel workstreams, separate spreadsheets, or manual reconciliation processes, it may be worth evaluating whether a unified consolidation platform can reduce that overhead. You can schedule a walkthrough here to see how both reporting views work from a single data set within eMerge.
