Fiduciary Intelligence
September 21, 2026

What CFOs Miss Below the Stop-Loss Threshold

Abhishek Ghosh

TABLE OF CONTENTS

Healthcare claims leakage below stop-loss thresholds is money a self-funded plan pays out in error on claims too small to reach the stop-loss carrier. Because the employer funds every dollar under the deductible, duplicate payments, coding errors and eligibility mistakes typically escape a stop-loss carrier's review.

KFF's 2025 survey found that 80% of covered workers at larger firms are in self-funded plans, which means their employers pay claims from their own funds. Picture a 600-employee manufacturer with a $150,000 specific stop-loss deductible. A duplicate $9,000 facility payment clears on a Tuesday, and no stop-loss carrier ever sees it. That is healthcare claims leakage, and it sits in the layer most CFOs assume someone else is watching.

Key Takeaways
1. Stop-loss protects against large claims. It does not police small ones.
2. Claims leakage hides in ordinary duplicates, coding gaps, eligibility lapses and pricing mismatches.
3. Sample audits and summary reports describe an error rate. They rarely recover the dollars.
4. ERISA puts the monitoring duty on the plan sponsor.
5. Independent, full-population review turns an invisible cost into a documented recovery.

What Healthcare Claims Leakage Below Stop-Loss Thresholds Actually Means

Healthcare claims leakage is money a self-funded plan pays in error and never gets back. Stop-loss insurance protects an employer from large claims only, so mistakes on everyday claims land entirely on the employer.

Most sponsors assume a stop-loss policy means someone is checking the work. The contract says otherwise. A specific deductible is the per-person amount an employer pays before reimbursement begins, and SHRM explains that the insurer covers eligible claims only above that deductible.

Most claims by count sit beneath that line, and each one is small enough to escape notice. Think of stop-loss as a smoke detector on the top floor. It sounds for a large fire and stays silent about a slow pipe leak two floors below.

Why the Problem Exists

Claims leakage persists because no one in the payment chain is set up to check small claims one at a time. TPAs process claims at high volume with automated edits built for speed, and many lack the tools or contract scope for line-by-line financial review. That is a design limit and not a shortcoming of any one administrator.

Sampling widens the gap. A 300-claim sample from a plan that processes 80,000 claims reviews under 0.4% of activity. Everything outside the sample is assumed to resemble it.

Contracts add friction. Some administrative services agreements limit who may audit, how often and with what notice. Sponsors also assume the TPA or the stop-loss carrier already verifies payments, so nobody asks the question.

The Real Cost of Healthcare Claims Leakage

Unchecked payment errors drain plan funds dollar for dollar because no carrier covers the loss. CMS estimated that 6.55% of Medicare payments for individual healthcare services were improper in fiscal 2025, totaling $28.83 billion. Medicare is different from an employer health plan, and the figure includes underpayments and payments without enough documentation. Still, it shows how common payment errors can be, even in a system with extensive automated checks.

Apply simple arithmetic to your own plan. A self-funded plan that pays $10 million in claims loses $100,000 for every 1% paid in error. At KFF's 2025 average family premium of $26,993, that equals nearly four family policies.

Consequences reach beyond cash. The DOL states that fiduciaries who miss the basic standards of conduct may be personally liable to restore losses to the plan. Overpaid claims can also inflate the claims experience that sets next year's funding rates.

What's Actually Happening Behind the Scenes

Claims leakage traces back to four repeatable failure modes.

Duplicate Payments

A duplicate payment is a second payment for a service already paid. Resubmitted claims and altered dates of service are common triggers.

Coding and Unbundling Gaps

Unbundling means paying separately for parts of a procedure that a single code already covers. CMS designed its National Correct Coding Initiative edits to prevent improper payment when incorrect code combinations are reported. A plan without comparable edits can pay for the same work twice.

Eligibility and Coordination of Benefits

Coordination of benefits errors occur when a plan pays first although Medicare or another plan should pay first. Payments for members whose coverage has ended create the same problem.

Pricing and Plan-Term Mismatches

A claim paid above the contracted rate or beyond a plan limit looks normal in a summary report. It surfaces only when each line is compared with the contract and the plan document.

Why Current Approaches Aren't Enough

Today's oversight tools examine a thin slice of claims, so claims leakage often goes unmeasured. The table compares that status quo with a fiduciary-grade approach.

Dimension Status Quo Recommended Approach
Scope Sample of claims Every claim in the plan year
Timing Periodic review after payment Ongoing monitoring plus annual audit
Data access Summary accuracy reports Line-level claims files guaranteed by contract
Verifier TPA quality checks Independent reviewer
Evidence Audit summary letter Findings and corrective actions in committee minutes

Speed metrics such as turnaround time show how fast claims move. They do not show whether the dollars moved correctly. None of this means TPAs are careless, because the standard toolset was never designed to answer the question a fiduciary must answer.

How to Fix It

A benefits committee can start these seven steps this quarter.

1
Read Your Administrative Services Agreement
Note the audit rights, data access terms and notice requirements before starting any review.
2
Request 12 to 24 Months of Line-Level Claims Data
Request de-identified, line-level claims data in writing. ERISA Section 724, added by the Consolidated Appropriations Act, bars agreements that restrict a plan from electronically accessing this data.
3
Review Claims Leakage Across All Dollar Ranges
Define a review scope that covers claims leakage across all dollar ranges. Do not limit the review to claims near the deductible.
4
Engage an Independent Reviewer
Use an independent reviewer and document that its fee is reasonable as part of the oversight process.
5
Track Recoveries and Corrective Actions
Route findings to the TPA with a corrective-action log that tracks both recoveries and system fixes.
6
Move to Monthly or Quarterly Monitoring
Review claims regularly so errors surface while they are still small, rather than waiting for a periodic audit.
7
Add Overpayment Rates to Performance Guarantees
At renewal, ask for overpayment-rate measures in the performance guarantees so accuracy carries the same weight as speed.

Red Flags That Signal the Problem Applies to Your Plan

No one on your benefits committee can name last year's overpayment rate as a number.
Your committee has never measured claims leakage below the deductible.
You receive accuracy summaries but cannot describe the sampling method or sample size.
Your agreement restricts which firms may audit or when they may begin.
You have not pulled line-level claims data in the past 12 months.
Dependent eligibility was last verified when the plan launched.
You changed administrators within three years, but earlier claims were never independently reviewed.
Pharmacy and specialty drug claims are not compared with contract pricing.

The ROI of Doing It Right

Independent claims oversight pays for itself when it recovers even a small share of claims leakage. Audit firms report that full reviews typically recover 1% to 3% of annual claims spend. Those are vendor-reported figures and not government data, so ask any reviewer to document results from comparable plans. On $10 million in paid claims, that range equals $100,000 to $300,000.

Recovery is only the first return. Corrections to system edits and contract terms stop the same error from recurring in later plan years.

Fiduciary protection is the third return. ERISA Section 404(a)(1)(B) sets the prudence standard, and the DOL notes that prudence focuses on process, so decisions and their basis should be documented. A written monitoring record is the evidence that meets it.

Conclusion and Next Steps

Healthcare claims leakage below stop-loss thresholds is measurable, recoverable and preventable. The plans that address it start with one question at the next benefits committee meeting: what was our overpayment rate last year? If no one can answer with a number, request an independent assessment and record the request in the minutes.

Frequently Asked Questions

What is a claims audit?

A claims audit is an independent comparison of paid claims against plan terms and provider contracts to find payment errors.

Who is responsible for claims accuracy on a self-funded plan?

The plan sponsor. DOL guidance says employers may delegate administration to a TPA but must monitor that provider periodically.

How often should a self-funded plan review claims?

ERISA sets no fixed schedule. DOL guidance calls for review at reasonable intervals, so more frequent checks catch errors while they are small.

Does the gag clause attestation prove claims were paid correctly?

No. It attests that contracts do not restrict data access. It does not verify that claims were paid correctly.

Is a sample audit enough?

Not for recovery. A sample estimates an error rate, but only the claims actually reviewed can produce a recovery.

Does healthcare claims leakage affect small employers too?

Yes. KFF reports 27% of covered workers at small firms are in self-funded plans, and every employer-funded dollar carries the same exposure.

Will independent review strain the TPA relationship?

It need not. Framed as a routine fiduciary process with agreed data requests, review gives both sides a shared record of payments.