Captive Insurance
An insurer owned by the businesses it covers, the forms it takes, and what separates a captive from simply retaining the risk.
The money paid out above what the claim should have cost, why it is measured by file review, and what separates it from fraud.
Claims leakage is the avoidable cost an insurer incurs when a claim is handled less accurately or efficiently than it reasonably could have been. It can include excess payments, unnecessary handling expenses, and recoveries that are missed because of a preventable error or delay.
The term concerns the difference between the actual outcome and a properly handled claim. An expensive claim can be handled correctly, while a small claim can contain a duplicate payment or another avoidable cost.
Insurers use different definitions depending on the purpose of a review. A narrow definition focuses on excess claim payments. A broader definition also includes avoidable operational costs and missed opportunities to recover money.
For that reason, a leakage figure needs a clear scope. A review of settlement payments cannot be compared directly with a review that also includes legal bills, administration, and recoveries. The Lab Consulting, for example, includes overpayments, excess defense costs, and repeated processing among potential sources of leakage. The Lab Consulting’s explanation of claims leakage.
Three categories help explain the differences:
| Category | What it concerns | Illustrative example |
|---|---|---|
| Payment leakage | More paid than the appropriate amount under the claim’s circumstances | The same repair invoice is paid twice |
| Expense leakage | Avoidable costs of handling the claim | A duplicate inspection is ordered because the first report was overlooked |
| Recovery leakage | A recoverable amount lost through an avoidable failure | Evidence needed for a viable recovery is not retained |
Each example requires investigation. A second inspection may be necessary because the damage has changed. A recovery may be uneconomic to pursue or unsupported by the evidence. The reviewer needs to establish what could reasonably have been done differently.
A handler may not receive the correct policy version, a relevant endorsement, or an earlier payment record. Decisions made from incomplete information can produce payment errors and unnecessary work.
A clear first notice of loss helps establish the initial facts, but the claim record also needs to incorporate later documents and decisions.
Examples include a duplicated invoice, an incorrectly applied deductible, or an arithmetic error in a settlement calculation. Similar-looking documents can make duplication difficult to spot when payments are handled in separate systems.
The control needs to consider the actual claim arrangement. A deductible already collected elsewhere should not be deducted again simply because one screen does not show the earlier transaction.
A claim may wait for an assignment, move between teams, or reach a specialist after an important decision has already been made. Delay can sometimes increase costs, although the existence of a delay alone does not establish a financial loss.
EY’s assessment of casualty and litigated claims identifies weaknesses in evaluation, investigation, litigation handling, and prevention as sources of leakage. Its discussion emphasizes understanding the facts needed to reach an appropriate outcome. EY’s analysis of financial leakage in litigated claims.
Some claims offer opportunities to recover money through subrogation, salvage, or another applicable arrangement. A missed referral or lost document can reduce the amount ultimately recovered.
The estimated opportunity should reflect the evidence, costs, and likelihood of recovery. Treating every possible recovery as fully collectible would exaggerate leakage.
A claims review usually begins by defining the population and the costs included. Reviewers then examine files, identify avoidable differences, and document the evidence behind each finding.
An illustrative measure is:
Leakage rate = identified avoidable cost ÷ reviewed claim cost × 100
This is a measurement convention, rather than a universal accounting formula. The numerator and denominator must use a compatible basis. If the review measures payment leakage only, its denominator should describe the corresponding payments reviewed.
Consider a fictional review of 100 closed claims with $1 million in claim payments. Reviewers identify $25,000 in duplicate payments and calculation errors, with no overlap between the findings.
Payment leakage rate = $25,000 ÷ $1,000,000 × 100 = 2.5%
Suppose they also identify $8,000 in avoidable handling expense. That amount should be reported separately until the review defines a broader cost measure and an appropriate denominator.
The 2.5% figure describes this fictional review. It is not an industry benchmark.
A sample of disputed, high-value claims will answer a different question from a representative sample of all closed claims. Targeted reviews are useful for identifying problems, but their results should not automatically be applied to the entire portfolio.
Reviewers also need to separate a handling error from a financial consequence. A missing document may be a process weakness without having changed the payment. Counting every procedural exception as monetary leakage would overstate the result.
Hindsight requires care. The assessment should consider the information available when the decision was made. A reasonable settlement does not become a handling failure simply because later information suggests another outcome might have been possible.
Fraud can contribute to leakage when avoidable weaknesses allow an improper payment. Leakage also arises from ordinary errors, incomplete records, and inefficient work. The terms describe different problems and should not be used interchangeably.
A reserve increase is different again. A claim may become more expensive because an injury is more serious than first understood. Updating the estimate to reflect new evidence does not, by itself, indicate leakage.
Likewise, an insurer cannot establish leakage merely by comparing its final settlement with the claimant’s initial demand. The relevant question is what an appropriate, properly handled outcome would have cost.
Useful controls address a specific cause: checking for duplicate invoices before payment, making the applicable policy documents accessible, assigning specialist work promptly, and recording potential recoveries with a responsible owner.
File reviews can then test whether those controls improve outcomes. Findings should feed into procedures and training, rather than remain isolated audit observations.
Automation needs the same scrutiny. Deloitte describes how incorrectly designed claims algorithms can produce repeated underpayments or overpayments, making human oversight and review of automated results important. Deloitte’s research on claims transformation.
Lower payments alone do not demonstrate an improvement. A useful assessment also considers payment accuracy, complaints, rework, and whether customers receive the benefits due under their policies. Claims leakage reduction means removing avoidable cost while handling claims correctly.

An insurer owned by the businesses it covers, the forms it takes, and what separates a captive from simply retaining the risk.

What a case reserve represents, how the first estimate is set, and why it moves every time new information reaches the file.

How insurers sort incoming claims by complexity and route them, and what separates a rules-based assessment from a predictive one.
Book a live, personalized demo with our product team - tell us your use case and see the platform work with your data. No commitment.