CFO Strategy — India & Global
Modernizing Finance in Indian Enterprise Groups
The group CFO of a ₹2,500 crore Indian conglomerate — 14 entities across manufacturing, trading, real estate, and financial services — described his finance function as “fourteen independent countries that happen to share a flag.” Entity A runs SAP. Entity B runs Tally. Entity C just migrated to Oracle. Entities D through H use a mix of QuickBooks and spreadsheets. The chart of accounts differs across every entity. Intercompany reconciliation is a 3-week manual exercise involving email chains between entity controllers who disagree on balances. Consolidated reporting takes 22 days. The statutory auditors spend an additional month reconciling differences. The group CFO has been in the role for two years and has spent most of that time firefighting rather than transforming. He has the budget for modernization. He has the mandate from the board. What he lacks is a starting point that does not require boiling the ocean. Every consulting firm that has pitched him proposes a 3-year, ₹15 crore ERP unification project. He does not need all 14 entities on SAP. He needs all 14 entities speaking the same financial language.
Indian enterprise group finance modernization is not an ERP project. It is an architecture project. The priorities: unified chart of accounts across all entities (regardless of which ERP they use), standardized intercompany protocols (so consolidation becomes automated rather than investigative), continuous compliance workflows (so GST, TDS, and MCA deadlines are met without monthly sprints), and a coordinated close calendar that treats consolidation as a managed project. These four changes produce more improvement than any ERP migration — and can be implemented in 6 to 12 months for the first wave of entities.
How to modernize finance operations in Indian enterprise groups with multiple entities, mixed ERPs, and overlapping regulatory requirements — without a multi-year ERP unification project.
Group CFOs at Indian enterprise groups (₹500 crore to ₹10,000 crore) managing 5 to 30 entities across states and sometimes countries. Also relevant for PE-backed platforms building through acquisition.
Indian enterprise groups are underserved by global modernization frameworks that assume a single ERP, simple regulatory environments, and clean entity structures. The India-specific playbook requires different priorities, different sequencing, and different measures of success.
What Makes This India-Specific
Entity proliferation. Indian groups often have 10 to 30 entities created for historical tax planning, licensing requirements, state-level operations, or family allocation. Each entity is a separate compliance unit with its own GST registrations, MCA filings, tax returns, and statutory audit. The entity count creates exponential coordination complexity as described in multi-entity architecture.
Regulatory density. GST (monthly), TDS (quarterly), advance tax (quarterly), MCA (annual), transfer pricing (annual), statutory audit (annual), tax audit (annual), and sector-specific compliance (SEBI for listed entities, RBI for entities with foreign transactions, IRDA for insurance, etc.). Each regulatory requirement has its own deadlines, data requirements, and penalty structures.
Technology heterogeneity. Entities within the same group often run different ERPs — acquired at different times, for different reasons, with different levels of implementation quality. The manufacturing entity might run SAP. The trading entity might run Tally. The newer entity might run Zoho Books. Consolidation across these platforms is manual by default.
Family governance. Many Indian enterprise groups retain family promoter involvement in operational financial decisions. This creates informal authority structures that coexist with formal hierarchies. Modernization must work within these structures rather than against them.
Architecture First, Technology Second
The consulting pitch for a ₹15 crore ERP unification assumes that technology homogeneity is the prerequisite for operational improvement. Across 915 implementations we analyzed, this assumption is wrong. The prerequisite is architectural consistency: common chart of accounts, common processes, common data standards. These can be achieved across heterogeneous ERP platforms faster, cheaper, and with less disruption than ERP migration.
An operating system that sits above the ERPs provides the coordination layer. The ERPs handle transactions. The operating system handles workflows, consolidation, compliance coordination, and group reporting. When the operating system is designed, the ERP underneath becomes less critical — the entity on Tally and the entity on SAP both produce outputs that the operating system can consume because the chart of accounts, the data formats, and the process standards are unified.
The Unified Chart of Accounts
The single highest-impact modernization initiative. Design a group-level chart of accounts that every entity adopts, with entity-specific segments for local reporting needs. This enables: automated consolidation (no manual account mapping), consistent cross-entity comparison (the same account means the same thing across entities), and group-level reporting that aggregates cleanly.
The implementation approach for existing groups: audit all entity-level charts, design the group structure, create a mapping from each entity’s current COA to the group COA, and migrate entity by entity over 3 to 6 months. Start with the entities that drive the most intercompany transactions — the COA alignment immediately improves intercompany reconciliation for those entities.
For Indian groups with Ind AS consolidation requirements, the unified COA should embed the segment reporting structure (business segments, geographic segments) at the chart level rather than adding it during consolidation. This eliminates the annual scramble to allocate balances to segments during the Ind AS consolidation process.
Intercompany Architecture
With 14 entities, the group has 91 potential intercompany relationships. Even if only 20 are active, the reconciliation burden is substantial. The architecture solution: standardized intercompany recording protocols (same day, same rate, same reference), weekly automated matching (not monthly manual reconciliation), and a central intercompany coordinator who owns group-level intercompany integrity.
For transfer pricing compliance under Section 92: maintain arm’s length pricing documentation as part of the intercompany protocol, not as a separate annual exercise. When every intercompany transaction is priced according to the transfer pricing policy at the point of recording, the annual compliance becomes a documentation compilation rather than a retrospective analysis.
Continuous Compliance Design
Indian enterprise groups with 14 entities and multiple state GSTINs can have 40+ monthly GST returns, 14 quarterly TDS returns, 14 annual MCA filings, and dozens of other compliance obligations. Managing these as individual deadline-driven tasks is operationally unsustainable.
The continuous compliance approach: centralize compliance monitoring (one dashboard showing all obligations across all entities with days-to-deadline tracking), standardize the preparation workflow (same process for GST preparation across all entities, adapted for entity-specific data), and automate data extraction from ERPs (build the data pipeline once, run it monthly across all entities).
For AI-assisted compliance, the prerequisite is standardized data: consistent chart of accounts, consistent transaction coding, and consistent documentation. Groups that standardize their data across entities can deploy AI tools across the group simultaneously. Groups with inconsistent data must customize AI tools entity by entity — a cost multiplication that eliminates the benefit.
Group vs. Entity Governance
The group CFO and entity-level finance heads must have clear, explicit boundaries. Without them, either the group CFO micromanages (creating bottlenecks) or entity heads operate independently (creating inconsistency that breaks consolidation).
The governance model that works: Group CFO owns architecture: unified COA, standard processes, technology strategy, group reporting framework, consolidated compliance monitoring, and intercompany protocols. Entity finance heads own execution: daily transactions, entity-level close, local compliance filing, and entity-specific stakeholder management. The group CFO sets the standards. Entity heads operate within them.
For family-governed groups, the group CFO must also navigate promoter involvement. The practical approach: establish a finance committee (group CFO plus senior entity finance heads) that meets monthly to review group-level metrics, discuss architectural decisions, and surface cross-entity issues. The promoter participates in the finance committee for strategic decisions but does not bypass the architecture for operational decisions. This is easier to design than to implement — but impossible to implement without designing.
Phased Sequencing
Phase 1 (Month 1-6): Foundation. Unified COA design and pilot implementation across 3 to 4 high-impact entities. Standardized intercompany protocols for the top 10 intercompany relationships. Compliance dashboard showing all obligations across all entities.
Phase 2 (Month 7-12): Expansion. COA migration for remaining entities. Coordinated close calendar across all entities. Weekly intercompany reconciliation operational. Workflow visibility for the group-level close.
Phase 3 (Month 13-18): Optimization. Continuous compliance workflows operational. Group reporting automated. AI tools deployed for reconciliation and anomaly detection. Technology rationalization decisions made based on operational data (now you know which ERPs to keep and which to migrate — based on evidence, not vendor pitches).
Each phase delivers standalone value. The group does not wait 18 months for the first improvement. By month 6, the pilot entities have a unified COA, clean intercompany, and compliance visibility. The board sees measurable improvement. The mandate for continued investment is earned through results, not promised through proposals.
Key Takeaways
Unified chart of accounts, standard processes, and consistent data standards deliver more improvement than ERP migration — faster, cheaper, and with less disruption.
Standardize protocols, reconcile weekly, assign central ownership. With 14 entities and 91 potential relationships, intercompany discipline determines close speed.
40+ monthly returns across entities require centralized monitoring, standardized preparation, and automated data extraction. Sprint-based compliance is operationally unsustainable.
Start with 3-4 pilot entities. Show results in 6 months. Earn the mandate for continued investment through demonstrated improvement.
The Bottom Line
The fourteen independent countries that happen to share a flag is not a technology problem. It is a design problem. The ₹15 crore ERP unification project addresses the technology while ignoring the architecture. The alternative — unified chart of accounts, standardized processes, continuous compliance, and coordinated close — addresses the architecture while working with the technology that exists. The group CFO who starts with architecture produces measurable improvement in 6 months and builds the foundation that makes future technology decisions evidence-based rather than vendor-driven. Indian enterprise groups do not need more software. They need designed systems that make the software they already have work together coherently. That design is the modernization.
Frequently Asked Questions
What makes Indian enterprise modernization unique?
Entity proliferation, regulatory density (GST, TDS, MCA, etc.), technology heterogeneity across entities, and family governance traditions that create informal authority structures.
Should all entities use the same ERP?
Not necessarily. A unified chart of accounts and standardized processes across heterogeneous ERPs deliver more improvement than forced ERP migration.
How do groups handle multi-state GST at scale?
Centralized monitoring, standardized preparation workflows, and automated data extraction. Groups that centralize spend 40-60% less than those that manage at the entity level.
What is the group CFO's role versus entity finance heads?
Group CFO owns architecture (standards, technology, group reporting). Entity heads own execution (transactions, local compliance, entity close).
How long does modernization take?
18-36 months for full transformation. First tangible results in 6 months with a phased approach starting with 3-4 pilot entities.