As parallel reporting demands converge, insurers need a governed foundation that connects finance, actuarial data, disclosures and audit evidence.
India's insurance sector is approaching a major change in financial reporting. The transition to Ind AS, with Ind AS 117 at its core, is far more than a compliance exercise. Based on IFRS 17 issued by the IASB, Ind AS 117 introduces new measurement, disclosure, and reporting requirements that reshape the way insurers assess and communicate financial performance. Consequently, insurers will need to transform how they close their books, prepare disclosures and engage with boards, auditors and regulators.
The challenge is that several demands converge on the same finance calendar at a time when insurers have only a limited window to prepare for the transition. While continuing to comply with existing IGAAP, statutory and regulatory reporting requirements, insurers must simultaneously implement Ind AS 117 and its new measurement, reporting and disclosure framework. Key Ind AS 117 measurements originate in actuarial systems and must be reconciled, governed and explained by finance, while disclosures require levels of detail that traditional general ledgers were not designed to capture. The combination of significant business change and compressed implementation timelines makes early preparation essential.
Together, these demands make the transition to Ind AS 117 an enterprise-wide transformation program rather than a limited accounting project. With significant changes required across processes, systems, data and governance, and only a limited timeframe available for implementation, insurers need to mobilise well beyond the finance function.
What challenges does Ind AS 117 create for Indian insurers?
Ind AS 117 introduces new measurement approaches, disclosure requirements and reporting processes that require insurers to rethink how actuarial results, financial reporting and disclosures connect across the reporting cycle.
For most insurers, IGAAP and Ind AS reporting will draw on the same underlying transactions, within the same reporting window and often with the same teams. Many insurers need a controlled reporting process that bridges existing accounting records and Ind AS reporting requirements.
Ind AS 117 journals arrive from the actuarial engine according to an actuarial timetable. Adjustments relating to Ind AS 109, Ind AS 116 and deferred tax require controlled and auditable treatment. The reconciliation between IGAAP and Ind AS therefore becomes a recurring deliverable, not a one-time transition exercise.
Under Ind AS 117, reporting is no longer limited to producing financial statements. Insurers must deliver a broad set of disclosures, reconciliations, roll-forwards, sensitivity analyses and analysis of change reports that explain how value and profitability evolve over time. The result is a more demanding reporting landscape, with multiple stakeholders, data requirements and deadlines to manage simultaneously.
Why do spreadsheets become difficult to govern during Ind AS 117 reporting?
As insurance reporting requirements become more complex, spreadsheet-led processes can make transparency, traceability and governance more difficult to maintain.
It may be tempting to manage this complexity with additional workbooks, reviewers and close-week effort. That approach becomes increasingly difficult to govern as reporting requirements multiply.
The issue is not that finance teams are careless. File volumes, dependencies and review steps grow faster than manual processes can reliably absorb. A figure in a disclosure note can become difficult to trace through the adjustments that created it. Version control can obscure which file is current. Preparers and reviewers can struggle to work concurrently, while a presentation change may need to be repeated across multiple linked workbooks.
These limitations create a practical control problem. Maker-checker reviews may exist as a process but not as system evidence. Reversals can be duplicated or omitted. Institutional knowledge can remain concentrated with a small number of people. Disclosures are often assembled late in the close while source numbers may still be changing.
The result is a finance function that spends too much time producing and reconciling numbers, and too little time explaining what those numbers mean.
What is the cost of waiting?
The risks of inaction often remain hidden until reporting pressure is at its highest. If the reporting build slips, the first Ind AS period may arrive while the trial balance and disclosure process are still being assembled manually. If the bridge between IGAAP and Ind AS is not evidenced, audit teams may need to reconstruct movements each time they review them.
The operating model also matters. Two regimes managed by one team, on overlapping calendars, can extend the close and increase key-person dependency. Ind AS 117 roll-forwards and sensitivity disclosures cannot be produced from a trial balance alone. They require detailed, governed data that can be traced to the underlying measurement and adjustment process.
These are not only finance-team concerns. They affect reporting confidence, audit readiness, and the quality of information available to management and the board.
What capabilities should a workable reporting foundation provide?
A sustainable approach starts with one shared reporting foundation, with each reporting regime configured on top of it rather than managed through disconnected close processes.
The foundation should connect the chart of accounts, entity structure, trial balance, actuarial journals, controlled manual entries, reversals and allocations. Because actuarial, finance and reporting processes span multiple systems, it should also integrate with existing actuarial, finance and source systems without requiring disruptive changes to the insurer's current architecture. Establishing a single contract data repository helps create a single version of truth for reporting and disclosure requirements, enabling insurers to spend less time reconciling numbers and more time analyzing business performance.
The platform should support the core Ind AS 117 measurement approaches, including the Building Block Approach (BBA), Premium Allocation Approach (PAA) and Variable Fee Approach (VFA). It should also support calculations for liabilities for remaining coverage (LRC), liabilities for incurred claims (LIC), contractual service margin (CSM), risk adjustment and discounting of future cash flows.
The foundation should also provide governed workflow, clear ownership, multi-level approvals, and a record of who prepared, reviewed and approved each adjustment. Audit trails and process-monitoring dashboards can provide visibility into submission, adjustment and consolidation status, helping teams keep contributors aligned and reporting activities on track.
Reconciliation and traceability are equally important. A validated trial balance load can support both regimes, with the Ind AS view assembled from the IGAAP base plus relevant actuarial and standard-specific adjustments. When every adjustment is recorded within a defined audit category, the IGAAP-to-Ind AS bridge becomes an available report rather than a reconstruction exercise.
Technology can enable these capabilities, but it should follow the operating model. Accounting policy, actuarial modelling, data ownership, and process clarity must be established first. The objective is a controlled line of sight from source data to adjustment, approval, financial statement and disclosure.