LRLossReserves.com
Back to The WireHealth Plans

Scentsy Ruling Makes Late Stop-Loss Claims a Reserve Issue

A September 3 Idaho federal ruling found a plan administrator breached its ERISA fiduciary duty after a high-cost infant claim missed a disputed stop-loss payment window. The reserve lesson is to carry the claim gross until the recovery is confirmed, rather than netting it because the care occurred in the policy period.

On September 3, the U.S. District Court for the District of Idaho granted Scentsy summary judgment on its ERISA fiduciary-duty claims against Blue Cross of Idaho. The employer’s self-funded plan had both a claims-administration agreement and specific stop-loss coverage with Blue Cross. The court found the carrier had a conflict when it administered a claim that could also trigger its own excess-coverage obligation.

The disputed claim arose from care for Baby H., who was born with serious congenital conditions in February 2022 and transferred to a California neonatal intensive care unit. The order says $987,353 of care incurred in February and March was paid and covered under the excess contract. A further approximately $1.412 million incurred through April 22 reached Blue Cross in September, after the carrier’s asserted three-month payment window had closed. Blue Cross denied excess coverage and Scentsy paid that second claim.

The court did not say every delayed claim is collectible. Its narrower and more useful point is that Blue Cross knew the participant was a high-cost claimant before the coverage window ended, yet did not expedite the claim or seek retroactive coverage. That turns an administrative delay into a stop-loss claims reserve problem.

Who it affects

Self-funded employers with expiring specific stop-loss contracts, particularly plans with newborn intensive care, transplant, cancer, or other high-cost claims moving through an out-of-area network. It also matters to captive-backed health plans and benefits finance teams whose third-party administrator, stop-loss carrier, or affiliates perform more than one role in the claims flow.

The exposure is not limited to a disputed denial. A plan can book a favorable net claim position too early if its claims system marks a recovery as expected while the carrier has not accepted it. The dated carrier acknowledgment, not the claims-system flag, is the control that distinguishes a recovery from a hope.

The reserve mechanism

For a claimant approaching or exceeding the specific deductible, track five dates together: service incurred, claim received, adjudicated, paid, and submitted to the stop-loss carrier. Then retain two estimates in the reserve exhibit: the gross claim liability, including paid amounts and remaining broad IBNR, and the separately assessed stop-loss recovery.

The error is netting the second figure against the first simply because the medical services fall inside the policy period. As Scentsy shows, a contract can also require payment during a defined run-out period. If a recovery is disputed or its submission is late, the plan remains exposed to the gross high-cost claim while it resolves the coverage question. That affects both the case reserve for a known claimant and the expected claim ratio used for the current accrual.

This is distinct from the attachment and trend problem discussed in Stop-Loss Lasering Leaves Self-Insureds With Unhedged IBNR. Lasering changes how much risk the plan retains. Scentsy concerns whether a recovery already assumed in the net reserve is operationally and contractually real. For a primer on where those unpaid health claims sit, see IBNR for Self-Funded Health Plans.

What this means for your next review

Ask for a claimant-level reconciliation of every open case above the specific deductible: incurred amount, paid amount, carrier notice, submission date, written recovery acceptance, and cash received. Test terminal-payment and run-out provisions at the same time, especially for claims handled through other Blue Cross or provider networks. Where acceptance is absent, show the gross liability and the disputed recovery separately in the monitoring package; do not let a net claim reserve hide the collection risk.

Sources