Claims Reserving with AI: Where It Helps and Where It's Dangerous
Claims reserving is where an insurer decides how much money to set aside for claims it knows about but hasn't fully paid, and for claims that have happened but haven't been reported yet. It's one of the most consequential numbers a carrier produces — it drives solvency, pricing, and how profitable the business even looks.
AI is arriving in reserving, and the pitch is seductive: more accurate reserves, faster, updated continuously. Some of that is real and valuable. Some of it is genuinely dangerous. Knowing the difference matters more here than almost anywhere else in insurance AI, because the failure mode isn't an annoyed customer — it's a mis-stated balance sheet.
Where AI genuinely helps reserving
Individual claim reserving. Traditional reserving works on aggregates — triangles of how claim cohorts develop over time. But two claims in the same cohort can be wildly different: a minor fender-bender and a claim that's quietly heading toward litigation. AI can read the specifics of an individual claim — its characteristics, its narrative, its early signals — and set a more accurate case reserve than a one-size-fits-the-cohort figure. This is real, useful, and lower-risk, because a human adjuster reviews it.
Early warning on development. Models can flag claims likely to deteriorate — the ones that look small now but have the hallmarks of becoming large. Surfacing those early improves both reserving and claims handling. Also genuinely valuable.
Faster IBNR signals. "Incurred but not reported" — claims that have happened but you don't know about yet — is estimated from patterns. AI can incorporate more signals and update more frequently than quarterly triangle exercises, giving earlier warning of a shifting trend.
These share a shape: AI informs the reserving process with better granularity and earlier signals, while actuaries and their methods remain in control of the number.
Where it gets dangerous
The danger begins when AI moves from informing the reserve to setting it, autonomously, at the aggregate level that hits your financial statements.
1. Reserves are a regulated, audited number. They're not an operational metric you can tune and observe. They determine solvency and get scrutinised by regulators, auditors, and rating agencies. A number that can't be explained and defended isn't acceptable, however accurate it might be. "The model set it" is not a position you can take to an auditor about your balance sheet.
2. Black-box reserves are unauditable. If your reserve is the output of a model nobody can fully explain, you cannot answer the questions an auditor will ask about it. Reserving demands explainability not as a nicety but as a condition of sign-off.
3. Models trained on the past miss regime changes. Reserving's biggest risk is a shift the historical data doesn't contain — a new litigation trend, a change in claims inflation, a legal ruling that expands liability. An AI extrapolating from history will confidently under-reserve into exactly the environment that hurts you most, precisely because it's never seen it. Actuaries apply judgment about the future; a model applies patterns from the past.
4. The feedback loop is brutally slow. If a reserving model is wrong, you may not find out for years, as claims develop. By then the mis-statement has propagated into pricing and capital decisions. You cannot iterate your way to a good reserving model the way you can with, say, a fraud model that gives feedback in weeks.
The pattern that keeps AI safe here
The right architecture mirrors the governed pattern used everywhere in regulated insurance AI: the model informs; the regulated number stays under human control.
- AI sets granular case reserves that adjusters review — operational, reviewable, valuable.
- AI provides signals and early warnings into the actuarial process.
- Actuaries, using established and defensible methods, set the aggregate reserves that hit the financials — informed by the AI, not replaced by it.
- Every AI contribution is explainable and logged, so the final number can be defended.
This isn't AI-timidity. It's recognising that the reserving number has a different risk profile from a claims-triage decision, and the level of autonomy should match the stakes and the reversibility.
And, underneath it all
Even the safe, valuable applications depend on the same thing everything else does: clean, granular, well-structured claims history. Individual-claim reserving needs individual-claim data — including the narratives and characteristics usually trapped in free text and documents. Feed a reserving model the fragmented, dirty history most insurers actually have, and its granular reserves are granular fiction.
So the sequence, as ever, is foundation first: get the claims data clean and structured, apply AI where it informs and a human reviews, and keep the regulated aggregate number under actuarial control. Do that and reserving gets genuinely better. Skip it — let a black box set the number on dirty data — and you've automated your way to a balance-sheet risk you won't detect until it's expensive.
Reserving is the clearest example of a rule that runs through all of insurance AI: match the AI's autonomy to the cost of being wrong. Here, the cost of being wrong is your solvency. Govern accordingly.
We build the clean, granular claims data foundations that reserving AI depends on. More at IntelliBooks.
Comments
Post a Comment