Key Steps for Conducting a Post-Acquisition Finance Integration

A post-acquisition finance integration determines how quickly a newly combined insurance business can produce reliable reports, control cash, meet regulatory obligations and support profitable decisions. The work extends well beyond transferring ledgers. It involves aligning accounting policies, systems, data, people, controls, tax treatment and performance measures while the business continues serving policyholders.

For Australian insurers and insurance service organisations, the task has a distinct local context. A group may need to reconcile APRA reporting with statutory accounts, apply AASB 17 requirements consistently, manage GST and payroll tax obligations across states, and coordinate teams working between Sydney, Melbourne, Brisbane and regional offices. A structured approach reduces disruption and creates a dependable financial operating model.

Set The Integration Direction Early

The first step is to define what the combined finance function must achieve and when. A 30-, 60- and 90-day plan can separate urgent stabilisation from longer-term transformation. Immediate priorities may include preserving payment capability, maintaining month-end close, protecting payroll and confirming access to banking, tax and regulatory portals.

The integration team should establish a clear target operating model before choosing software or redesigning processes. This model should describe decision rights, reporting lines, shared services, local finance responsibilities and the future chart of accounts. It should also identify which activities must remain close to the business, such as claims finance or product profitability analysis, and which can be standardised.

Leadership alignment is essential. The CFO, chief risk officer, technology leaders and business unit executives should agree on success measures such as close-cycle duration, reconciliation backlogs, reporting accuracy, control exceptions and integration costs. Clear ownership prevents a common failure pattern in which every team assumes another group is responsible for the difficult decisions.

Build A Reliable Financial Baseline

Before migration begins, finance teams need a verified picture of the acquired organisation. This baseline should cover the general ledger, subledgers, bank accounts, investments, premium receivables, claims liabilities, reinsurance balances, fixed assets, tax accounts and intercompany positions. Historical trial balances should be reconciled to audited financial statements and management reports.

Data quality problems often become visible only when two businesses attempt to compare results. Different definitions of earned premium, acquisition costs, loss ratios and operating expenses can make a profitable portfolio appear underperforming. Finance should create a mapping between legacy accounts and the target chart of accounts, documenting assumptions and preserving enough detail for trend analysis.

Australian reporting requirements make this exercise particularly important. The acquired entity may have prepared information for APRA returns, ASIC obligations and AASB 17 disclosures using different interpretations or levels of granularity. Finance should catalogue the source, owner, frequency and regulatory purpose of every critical data set before deciding whether to convert, archive or recreate it.

Align Accounting Policies And Controls

A finance integration should produce one agreed policy framework for revenue recognition, insurance contract measurement, expense allocation, reserving, reinsurance, investment valuation, foreign currency and impairment. Where policies differ, the integration committee should assess materiality, audit implications and the effort required to restate or bridge information.

AASB 17 deserves focused attention because assumptions, actuarial models and finance processes are closely connected. Teams need a shared approach to contract boundaries, coverage units, risk adjustment, onerous contracts and the treatment of acquisition cash flows. Actuaries and accountants should review the same data lineage, rather than operating separate models that produce unexplained variances.

Internal controls must be redesigned around the future organisation. This includes segregation of duties, approval thresholds, journal controls, access reviews, vendor onboarding, payment authorisation and balance sheet reconciliations. ASIC expectations around governance and accurate financial information should be reflected in documented controls, while APRA-regulated organisations should connect the integration plan to risk management and prudential oversight.

Integrate Systems And Data Flows

Technology decisions should follow process and information requirements. A finance team may be working with separate enterprise resource planning platforms, policy administration systems, claims applications, data warehouses and reporting tools. Attempting to connect everything at once can create unstable interfaces and obscure the source of errors.

Start by mapping the critical data flows from quotation and policy issuance through premium billing, collections, claims, recoveries, commissions, reinsurance and the general ledger. Define authoritative sources for policy status, customer identity, transaction amounts and accounting treatment. A carefully governed master data model can prevent duplicate customers, inconsistent product codes and unreliable management reporting.

Customer administration deserves particular attention because policy lifecycle events drive many downstream finance entries. The practical relationship between policy records, billing, endorsements, cancellations and renewals is explored in customer administration systems, which can help integration leaders assess where operational data must connect with financial controls.

Testing should occur in stages: unit testing for interfaces, system integration testing, user acceptance testing and parallel reporting. Include realistic scenarios such as mid-term adjustments, backdated cancellations, large-loss claims, premium refunds, catastrophe events and reinsurance recoveries. A controlled cutover with rollback procedures is safer than a rushed “big bang” migration.

Manage People, Roles And Working Practices

Finance integration affects careers, authority and daily routines, so workforce planning should begin early. Map critical skills across both organisations, including statutory reporting, insurance accounting, actuarial finance, tax, treasury, data engineering and business partnering. Identify single points of failure and retain specialists who understand historical portfolios and legacy systems.

The future team structure should be communicated in plain language. Employees need to know which activities will be centralised, which roles will change and how decisions will be made during the transition. Clear communication is especially important where teams are distributed across Australian offices and operate under different local management traditions.

Training should combine technical instruction with process rehearsal. A new close calendar, approval workflow or reporting platform will not become effective because a manual has been published. Teams should practise end-to-end scenarios, review sample exceptions and understand how their work affects claims operations, customer service and regulatory reporting.

Working practices also need to account for Australian rhythms. EOFY planning, public holidays, school holiday periods and peak renewal cycles can affect availability and delivery dates. A transition scheduled around 30 June may place unnecessary pressure on statutory reporting teams, auditors and tax advisers, while a release during a major renewal period can increase operational risk.

Prioritise Practical Integration Actions

A focused set of actions helps executives turn the integration strategy into controlled workstreams:

These actions should be prioritised according to risk and dependency rather than divided evenly between departments. For example, an unresolved policy-product mapping issue may affect billing, revenue, claims analytics and regulatory returns at the same time. A dependency register can show which decisions must be completed before systems, reporting or process changes proceed.

Regular integration forums should focus on decisions, exceptions and evidence. Long status meetings with no accountable owners create the appearance of progress without reducing risk. A concise dashboard showing milestones, unresolved defects, control gaps, budget usage and readiness indicators gives the executive team a usable view of the transition.

Strengthen Assurance And Performance Reporting

An acquired business should not be considered financially integrated when the first consolidated report is produced. Sustainable integration requires repeatable close procedures, reconciliations, management reporting and control monitoring. The finance function should track whether improvements continue after the project team reduces its involvement.

Useful measures include days to close, manual journals, aged reconciling items, unreconciled cash, claims data exceptions, premium allocation errors, late reporting submissions and the number of spreadsheets supporting key controls. Measure quality as well as speed. A faster close that relies on unsupported estimates or unresolved data issues creates future audit and regulatory exposure.

Internal audit, external audit, risk teams and business users should be involved at appropriate points. Independent review can test whether controls operate as designed and whether management has addressed material findings. For APRA-regulated entities, the integration should also be considered alongside obligations relating to operational risk, information security and business continuity.

Performance reporting should connect financial outcomes with insurance drivers. Executives need to see how integration affects loss ratios, expense ratios, retention, claims settlement, acquisition costs, customer service and capital usage. A consistent dashboard helps leadership distinguish genuine portfolio performance from temporary effects caused by conversion, allocation or accounting changes.

Make The Conference Part Of The Learning Cycle

Integration leaders benefit from comparing their approach with peers, technology providers and specialist advisers. Insurance finance is changing through automation, advanced analytics, cloud platforms and more connected policy administration, so internal experience may not reveal every available option. External learning can challenge assumptions before they become expensive design decisions.

The IASA Conference provides a setting for insurance executives, finance and accounting professionals, operations teams and emerging leaders to examine accounting, technology, risk, tax and customer administration. Sessions and conversations with exhibitors can help teams test ideas about implementation sequencing, reporting controls, system architecture and workforce capability.

The value of an event is greatest when the integration team arrives with specific issues. Prepare a short list of questions about AASB 17 operating models, data governance, close automation, policy lifecycle integration and regulatory evidence. After the event, record relevant practices, assign owners and assess each idea against the target operating model rather than adopting solutions because they appear popular.

A learning cycle should continue after go-live. Schedule reviews at 30, 90 and 180 days to examine control performance, user feedback, reporting reliability and benefits realisation. This creates a disciplined opportunity to remove temporary workarounds, improve automation and refine the finance service provided to underwriting, claims and customer teams.

A successful post-acquisition finance integration is built through disciplined sequencing. Begin with a verified financial baseline, establish common policies, protect critical operations, connect systems through governed data flows and support people through practical training. Keep regulatory obligations visible throughout the programme, particularly where AASB 17, APRA reporting, ASIC governance, tax and privacy requirements intersect.

For Australian insurance organisations, the objective is a finance function that can close confidently, explain performance clearly and respond quickly to policyholder, regulator and executive needs. Use the priorities above to create an accountable integration roadmap, assign owners and review progress through each reporting cycle.