Effective communication between underwriting and finance teams

Clear communication between underwriting and finance is an operating discipline, not a courtesy. Underwriters judge appetite, exposure, terms and evidence; finance tests price, reserving, cost, capital and return. When each side works from a different version of the truth, a policy can pass risk review while weakening portfolio value. Shared decisions require shared facts, assumptions and accountability.

Australian insurers face a demanding operating context. Many teams are distributed between Sydney and Melbourne, where office routines mix whiteboard reviews, instant messages, email and spreadsheet analysis. APRA prudential supervision and ASIC-administered corporate and financial-reporting obligations raise the cost of weak controls. At the same time, Australian property and motor books carry concentrated exposure to bushfires, floods, cyclones and hailstorms, while AASB 17 reporting requires assumptions to be traceable and consistent.

These local realities do not require heavy governance. They require a common operating rhythm: agreed definitions, short recurring reviews and a clear route for exceptions. Underwriting evidence should reach finance with enough context to be useful, while financial results should return in a form that changes underwriting choices. The strongest relationship is built when both functions can explain not just what happened, but which assumption or action drove it.

IASA Conference offers a practical setting for that exchange, bringing together leaders across insurance accounting, finance, operations, technology and risk. Its sessions, exhibit hall and professional networking can help delegates compare approaches, challenge assumptions and build relationships that continue after the event. The central standard is simple: every material decision should have a visible owner, an evidence trail and a way to measure its outcome.

Shared language for risk and value

Underwriting evidence often arrives as a narrative: the hazard, the controls, the loss history, the requested limit and the reason for unusual terms. Finance needs those inputs in a comparable financial form. A joint data dictionary should define exposure units, policy periods, event definitions, limits, deductibles, earned premium, expected claims, acquisition costs, reinsurance and capital consumption. Without shared definitions, even accurate data can produce conflicting conclusions.

The language should extend to portfolio thresholds. An underwriter may regard a commercial property account in a flood-exposed part of Brisbane as acceptable in isolation; finance may reveal that several accepted risks share the same catchment and accumulation. The response is not to assign blame, but to compare the account’s terms with the aggregate view. Changes such as deductibles, sublimits, exclusions or capacity allocation can then reflect the combined view of risk and value.

This translation also protects future decisions. When a policy is renewed or a claim emerges, both teams need to recover the original assumptions and see which evidence changed them. A concise decision record containing the risk facts, financial view, conditions applied and approving authority turns isolated judgement into reusable institutional knowledge.

Reporting that connects decisions to results

The operating scorecard should connect choices made before bind with outcomes that appear later. Leading indicators can include quote turnaround, referral rates, risk-quality exceptions, deductible changes and mix by product, distribution channel and territory. Lagging indicators can include earned premium, claims frequency and severity, acquisition expense, reinsurance cost, profit and capital use. Both sets matter: leading indicators reveal pressure early, while lagging indicators test whether the original judgement was sound.

Small portfolios need care. A sharp move in claims frequency may reflect a handful of large events rather than a broad deterioration, while favourable results can hide weak pricing in a newly written cohort. The joint review should show claim counts and severity separately, compare actuals with the assumptions used at pricing, and distinguish rate, terms, mix and expense effects. Premium, claims, expenses, reinsurance and capital figures should reconcile to the general ledger and the controls supporting AASB 17 reporting.

Close the loop with a monthly operating review and a quarterly portfolio review. Underwriters need to see the financial consequences of their decisions; finance needs to understand why a result occurred. Capturing actions, owners and expected outcomes in the same scorecard ensures that the next pricing or appetite decision reflects evidence rather than anecdote.

Clear ownership across the insurance lifecycle

Clear ownership prevents consultation from becoming delay. Underwriting should lead risk selection and policy terms, finance should lead financial measurement and capital interpretation, and the two should jointly govern changes that cross both domains. Pricing exceptions, reserve concerns, reinsurance decisions, catastrophe accumulation and shifts in portfolio appetite all need named decision rights, required evidence and a defined escalation threshold.

Set a predictable cadence. A weekly pipeline review can address major quotes and appetite questions; a monthly performance review can examine portfolio results; a quarterly forum can reset strategy and assumptions. Keep the rhythm even when teams are working across Sydney and Melbourne or when a major event disrupts normal routines. Version-controlled files, recorded approvals and a single action log make the process resilient to absence, turnover and urgent workload.

A recurring bottleneck may point to a process gap rather than a behavioural one. When teams need better data integration, workflow controls or reporting, they can compare relevant capabilities among the conference sponsors and exhibitors. The right solution should then be tested against agreed requirements, security obligations and the decisions it must improve, rather than adopted because it offers an attractive dashboard.

Technology as a coordination layer

Shared numbers begin with shared data. Policy administration, claims, exposure, reinsurance, general ledger, customer and broker data may live in different systems, with spreadsheets adding another layer. Leaders should agree on a source for each critical measure, document lineage and resolve changes through controlled definitions. APIs, data marts and dashboards can distribute consistent inputs, but they cannot repair an ambiguous definition or an unreliable source.

Automation is most valuable when it highlights exceptions that need judgement. It can flag an exposure that changed after a quote, a claims pattern that breaches an agreed tolerance, or a portfolio movement with a material capital effect. Underwriters and finance specialists should jointly define the threshold, the response and the audit trail. Access controls, privacy safeguards and model governance remain essential, especially when customer information is connected across platforms.

Digital access does not replace professional conversation. It gives both teams the same evidence at the same time, leaving meetings to resolve trade-offs rather than reconcile numbers. External team challenges, including the Lake Powell Challenge, can also support shared learning by practising how assumptions and decisions interact under pressure. The lesson for an insurer is to simulate the decisions that matter in its own portfolio, then use the results to refine rules, roles and reporting.

Practical recommendations for stronger team alignment

The following practices convert good intentions into routine behaviour. They work across portfolios of different sizes and can be introduced without replacing every established system at once. Each measure should have an owner, a review date and an agreed definition of success.

Begin with the decisions that repeatedly cause friction, then use the following measures to make those decisions visible and accountable:

Start with a portfolio where both teams can see the result, then measure forecast accuracy, rework, decision cycle time and the proportion of actions completed on time. A small but reliable operating rhythm is more useful than a comprehensive framework that remains unused.

Turning insight into action at IASA Conference

IASA Conference brings insurance executives, finance and accounting professionals, operations teams, emerging leaders and solution providers into one multi-day environment. Sessions across insurance accounting, finance, technology, insurtech, risk management, tax and customer administration allow delegates to examine both the technical content of a decision and the operating model around it. Finance leaders can hear how underwriting controls affect financial outcomes, while underwriters can test assumptions against reserving, capital and technology perspectives.

The exhibit hall adds a practical channel for evaluating workflow, data and software options, and the professional networking programme creates space to compare experiences with peers and vendors. Delegates gain most when they bring a live issue, such as inconsistent profitability reporting or slow portfolio approvals, and use the programme to define a peer, a solution and a next step. Emerging leaders can observe how experienced professionals frame trade-offs, assign accountability and connect present decisions with future results.

Turn the next underwriting and finance issue into a working session at IASA Conference. Use the educational programme to test assumptions, the exhibit hall to compare practical solutions and the dedicated vendor connect to identify organisations suited to your requirements.

Register for IASA Conference and make the next underwriting-finance decision a shared one, supported by clear definitions, accountable ownership and reporting both teams trust.