Why Finance Teams (Not IT) Should Own the Consolidation Tool
In most large Indian enterprises, the finance team prepares consolidated financial statements, yet the tool they use to do it is controlled by someone else. IT departments manage the infrastructure, approve change requests, schedule upgrades, and decide when a new report format can be added. This disconnect, where the people accountable for consolidation outcomes have limited control over the consolidation tool, is one of the most persistent sources of delay and frustration in group reporting. The case for letting finance teams own the consolidation tool is grounded in operational logic, not organizational politics.
This post examines why that ownership shift matters, what it changes in practice, and how software like eMerge is specifically architected to make finance ownership viable without placing a technology burden on the team.
The Traditional IT Dependency Problem in Financial Consolidation
Consider a diversified Indian conglomerate with 30 subsidiaries, a few joint ventures, and associate companies spread across India, the Middle East, and Southeast Asia. The group finance team at the holding company is responsible for producing consolidated financial statements under Ind AS 110, Ind AS 111, and Ind AS 28, with quarterly filings to SEBI and the stock exchanges. Every quarter, this team depends on IT for tasks ranging from data imports and report modifications to user access changes and server availability.
This dependency creates three structural problems that compound with every reporting cycle.
First, there is a timing mismatch. IT teams operate on ticketing systems with SLAs designed for general enterprise requests. A finance team’s request to modify an elimination template or adjust a currency translation rule sits in the same queue as a password reset or a CRM bug fix. During quarter-close, when the finance team operates on a compressed timeline dictated by regulatory deadlines, this queue becomes a serious constraint.
Second, there is a translation loss. Finance professionals think in terms of trial balances, GAAP adjustments, intercompany eliminations, and minority interest computations. IT professionals think in terms of database queries, server configurations, and application patches. Every request from finance must be translated into IT language, executed, and then verified by finance. This back-and-forth introduces errors and delays that are entirely avoidable.
Third, there is an accountability gap. When the consolidated balance sheet has a casting difference, or when FCTR does not reconcile, or when a subsidiary’s data is missing, the CFO’s office is answerable to the auditors and the board. Yet the team that controls the tool, and by extension the data pipeline, reports to a different function. Accountability without authority is a well-known organizational dysfunction, and it plays out visibly in consolidation processes.
Finance Understands the Data Better Than Anyone Else
Financial consolidation is not a data processing exercise. It is an accounting exercise that happens to require software. The distinction matters because it determines who should configure, operate, and control the tool.
When a subsidiary in Germany reports revenue in EUR and the Indian holding company consolidates in INR, the choice between closing rate and average rate for translating the profit and loss statement is not a technical decision. It is an accounting policy decision governed by Ind AS 21. When the resulting translation difference flows into Other Comprehensive Income, the classification and presentation are finance decisions. When a new subsidiary is acquired mid-year and the group must account for goodwill under Ind AS 103, the entries, the purchase price allocation, and the NCI computation all require accounting judgment.
No IT team, however skilled, can make these decisions. They can only execute instructions. And every time finance must write those instructions as formal change requests, wait for execution, and then verify the output, the process adds days to the close cycle without adding any value.
A consolidation tool that finance teams own and operate directly eliminates this intermediary layer. The team that understands the accounting standards, the group structure, the holding percentages, and the elimination logic is the same team that configures and runs the system. This is how financial consolidation responsibility should be structured in practice.
Speed of Decision-Making During Quarter Close
The quarter-close window for listed Indian companies is tight. SEBI’s Listing Obligations and Disclosure Requirements (LODR) mandate that quarterly financial results be submitted within 45 days of the quarter end, and annual results within 60 days. For companies with complex group structures, the internal deadline is usually much earlier because the auditors need time to review, the audit committee must approve, and the board must sign off.
Within this compressed window, the finance team frequently encounters situations that require immediate action on the consolidation tool. A subsidiary may restate its trial balance after an internal review. An intercompany balance may not match, requiring investigation and adjustment. A new associate may need to be added to the hierarchy mid-cycle. The auditors may request a specific disclosure format that the current report template does not cover.
Each of these situations, if handled through IT intermediation, introduces a delay of hours to days. When the finance team owns the tool, the response is immediate. The team lead can adjust the hierarchy, re-import a trial balance, modify an elimination entry, or create a new report format within the same working session. This speed is not about convenience. It is about meeting regulatory deadlines with accurate numbers, which is the core obligation of the group finance function.
eMerge is designed with this urgency in mind. Its approach to accelerating the financial close is rooted in giving the finance team direct control over every step, from TB import to final consolidated report generation, without requiring a single IT intervention.
Reduced Bottlenecks Across Distributed Teams
Large Indian groups often have subsidiaries with their own finance teams operating in different cities and time zones. A Tata or Godrej group company might have entities in Pune, Mumbai, Chennai, London, and Singapore, each with its own chart of accounts, its own accounting system, and its own fiscal calendar. The coordination required to bring all these entities into a single consolidated view is already complex.
Adding IT as a gatekeeper to the consolidation tool multiplies this complexity. If a subsidiary finance team in Singapore needs to upload its trial balance and the system requires an IT-managed credential reset, the Singapore team waits for the IT team in India to come online. If the holding company’s finance team in Mumbai wants to check the dashboard to see which entities have uploaded data and which have frozen their intercompany eliminations, and the dashboard requires a configuration change, another ticket goes to IT.
When the finance team owns the consolidation tool, it manages user access, monitors upload status through dashboards, and follows up with subsidiary teams directly within the system. The tool becomes a collaborative workspace for the finance function across the group, rather than an IT-managed application that finance teams use as guests.
eMerge’s dashboard view, for instance, gives the group finance administrator a composite status of every entity: which trial balances have been uploaded, which intercompany eliminations are frozen, and which entities are pending. This is not an IT monitoring screen. It is a finance coordination tool, and it belongs in the hands of the finance team.
The Simple UI Requirement: Finance Teams Own the Consolidation Tool When They Can Operate It
Ownership is only meaningful if the team can actually operate the tool without specialized technical training. This is where many enterprise consolidation platforms fall short. They offer extensive functionality wrapped in interfaces designed for technical users, requiring SQL knowledge for custom reports, developer involvement for hierarchy changes, or scripting for data transformations.
Finance professionals are experts in accounting, not in application development. A consolidation tool meant for finance ownership must reflect this reality in its design.
The following table illustrates the contrast between a technically dependent consolidation tool and one designed for finance ownership:
| Task | IT-Dependent Tool | Finance-Owned Tool |
|---|---|---|
| Add a new subsidiary to the group hierarchy | IT configures database tables, maps relationships, tests | Finance team drags and drops entity into hierarchy tree |
| Change holding percentage after partial divestiture | IT modifies backend parameters, finance verifies output | Finance updates percentage directly, NCI recalculates automatically |
| Map subsidiary’s chart of accounts to group reporting structure | IT builds mapping rules, finance reviews mapping output | Finance maps accounts through a visual interface during TB import |
| Create a new disclosure report for auditors | IT develops report, finance tests, requests revisions | Finance uses built-in report generator to pull figures from existing reports |
| Post a consolidation journal entry (e.g., goodwill adjustment) | Finance prepares entry, IT posts or enables posting | Finance posts entry directly in journal voucher format with full audit trail |
| Grant a new subsidiary user access to upload TB | IT creates user, assigns role, communicates credentials | Finance administrator creates user and assigns role-based access |
eMerge was built from the ground up by a team of Chartered Accountants and technology specialists working together. This dual expertise is evident in the interface: hierarchies are managed through drag-and-drop, journal entries look like journal vouchers, report structures mirror the format finance teams already think in (Ind AS, IFRS, US GAAP schedules), and the ad-hoc report generator requires zero coding knowledge. The implementation methodology reinforces this design philosophy, with finance teams trained and operating independently within two cycles.
How eMerge Is Designed for Finance Ownership
eMerge’s architecture reflects a fundamental design principle: every function that a finance team needs during consolidation should be accessible to the finance team without IT involvement. This is not a partial claim limited to data entry. It extends across the entire consolidation lifecycle.
Data Import and Mapping
eMerge works trial balance upwards, accepting TB data from any accounting system, whether SAP, Oracle Financials, Tally, QuickBooks, Microsoft Dynamics, or home-grown ERP systems. Each subsidiary can run a different accounting system. The finance team at each entity imports its own TB and maps local account codes to the group’s common reporting structure. Once mapped, reports are available at the click of a button upon TB upload. No data transformation scripts, no ETL pipelines, no IT involvement.
Group Structure Management
The Hierarchy Manager allows the group finance team to define and modify the entire corporate structure, parent-child relationships, holding percentages, subsidiaries, joint ventures, divisions, and associates. N-level deep structures are supported. Adding a newly acquired entity or removing a divested one takes minutes. Multiple hierarchy views (legal entity, geographic, business unit) can coexist for different reporting needs.
Multi-GAAP Reporting
Regulated enterprises reporting under multiple frameworks simultaneously (for example, Ind AS for Indian statutory filings and IFRS for reporting to a foreign parent) can maintain multiple report structures within the same system. The finance team configures these structures. The same underlying data populates different GAAP-specific reports without duplication or re-entry.
Intercompany Eliminations
The elimination workflow is collaborative. The finance team at Company A enters its figures for transactions with Company B. The finance team at Company B verifies and confirms. Discrepancies are identified and resolved within the system before the consolidation lock is applied. This workflow-based approach, managed entirely by finance teams across entities, replaces the spreadsheet-based reconciliation that most groups still rely on.
Audit Trail and Corporate Lock
Every entry, modification, and approval is logged with timestamps and user identification. The administrator can lock all company data before consolidation begins, ensuring no changes occur during the consolidation process without explicit authorization. Auditors, whether internal teams or statutory auditors appointed under the Companies Act, 2013, can trace any consolidated figure back to its source entity and original trial balance. This drill-down capability, extending to the general ledger level, is available directly to the finance team without database-level access from IT.
Notes to Accounts and Report Assembly
eMerge’s Noteify module allows the finance team to prepare columnar and textual notes to accounts, with numbers linked directly to the underlying reports. Placeholders for prior period comparatives are populated automatically. The entire output, consolidated and standalone balance sheets, profit and loss statements, cash flow statements, and notes, can be assembled and exported to Excel with proper formatting and page breaks. The finance team produces the complete annual report package from within the system.
The Organizational Case for Finance Ownership
The argument for finance teams owning the consolidation tool is ultimately an argument about aligning authority with accountability. The group CFO, the financial controller, and the consolidation team are answerable to regulators (SEBI, MCA, RBI for financial institutions), to auditors, to the audit committee, and to the board. They sign off on the numbers. They present the consolidated results. They respond to queries.
Giving this team direct ownership of the tool they use to produce those numbers is not a luxury or a preference. It is an operational necessity for any regulated enterprise with a complex group structure. The consolidation tool is not an IT asset that finance happens to use. It is a finance asset that happens to run on IT infrastructure.
When that distinction is recognized and acted upon, the results are measurable: faster close cycles, fewer reconciliation errors, reduced audit queries, and a finance team that can respond to changing group structures and regulatory requirements without waiting in an IT queue.
Conclusion
If your organization’s consolidation process still routes through IT for tasks that are fundamentally accounting decisions, the inefficiency is structural, and it will compound as the group grows. The path forward is a consolidation tool that your finance team can configure, operate, and control independently, one that treats them as owners rather than end users.
eMerge was built for exactly this model of finance ownership, with implementations completed in six to eight weeks and finance teams operating independently after two cycles. If you are evaluating how to give your consolidation team the control they need, schedule a walkthrough with the eMerge team to see how the system works with your specific group structure and reporting requirements.
