Self-funded plans / Claims after termination

Termed in June. Claims still paying in August.

For TPAs, brokers, and anyone whose client pays its own claims.

The same miss, on the other side of the ledger

On a fully insured plan, a termination the carrier never applies costs premium. On a self-funded or level-funded plan it costs premium and claims, and the claims are usually the bigger number.

Maria Delgado's last day was June 30. HR entered the termination on June 28, two days early. The premium audit found her still on the July and August bills: $640.18. Her group's medical plan is level-funded, so the same administrator also pays her claims. The claims extract shows the same miss:

ClaimService datePaidTerm on file before paymentPlan paid
CLM40001198July 14July 2426 days$1,284.50
CLM40001308August 5August 1952 days$412.80
Paid for someone who wasn't covered$1,697.30

One termination, entered on time. $640.18 of premium and $1,697.30 of claims. Correcting the bill recovers less than half of it.

Why the eligibility check passes

Every claim system checks eligibility before it pays. The check is real; it just runs against the administrator's copy of the eligibility, not yours. If the termination never loaded (a rejected record parked in an error queue, a file that arrived after the load window, a member matched on the wrong identifier), the administrator's copy still says active, and the check passes on every claim.

So the question isn't whether the administrator checked eligibility. It's whether its eligibility matched yours on the date of service. The only way to answer that is to join every paid claim to your eligibility history, person by person and date by date.

Four reasons a claim pays for someone who wasn't covered

Finding the claim is the easy half. The reason it paid decides who owes the money back, and a dispute that names the wrong party goes nowhere.

What the record showsWhat it meansWho pays it backSample audit
Change entered before the claim paidThe administrator had the change and didn't apply itThe administrator credits the plan$4,199.90
Change entered after the claim paidRetro-term: correct when paid, an overpayment nowThe provider, through a refund request$3,940.00
No end date, but the birth date ends coverageThe plan's dependent age rule was never appliedThe administrator; the DOB was on file$1,701.15
COBRA election window still openNot wrong yetNobody, yet$5,210.00 on watch

The dependent nobody termed

Devon Carter dropped spousal coverage effective May 1, and the change was entered April 22. The premium audit found Meridian still billing EE+SP in June, July, and August: $1,102.50. His spouse's claims kept paying too:

PatientService datePaidDays change was on filePlan paid
Alicia Carter (spouse)June 18July 271$2,316.40
Alicia Carter (spouse)August 11August 25125$186.20
Paid after spouse coverage ended April 30$2,502.60

This one gets past a reviewer who checks subscribers, because the subscriber is still covered. Carter is an active employee with an active medical election. Eligibility belongs to the person, not the subscriber, so the check has to be per person: is this patient covered on this date of service?

The retro-term: correct when paid, wrong now

Graham Thorsby's last day was March 31. HR didn't enter the termination until April 20. In between, a claim for an April 8 visit paid on April 15. With the information the administrator had on April 15, that payment was correct.

Once the retro-term lands it becomes an overpayment, and the fix is a provider refund request. Most administrators open one automatically. The audit question is whether this one did. Dana Whitcomb's record in the same extract shows what it looks like when recovery works: termination entered February 20, a February 17 claim reversed on March 10, net zero. Thorsby's $3,940.00 has no reversal and no refund on file seven months later.

Retro-terms run on a clock. Administrative agreements often limit how far back a retroactive termination will trigger recovery, and provider contracts and state law limit how long a refund can be requested at all. A retro-term found at plan-year end may already be past both.

The age-out: the rule was in the plan, the date was on file

Owen Ferreira, Laura Ferreira's son, turned 26 on March 12. Under the plan's end-of-birth-month rule his coverage ended March 31. Nobody sent a termination because nobody has to: the rule plus the birth date does it. Except the record carries no end date, and his claims kept paying:

Service datePaidPlan paid
February 3February 17$245.60 · covered, clean
May 2May 14$612.75
July 9July 20$1,088.40

Before disputing an age-out, check for an incapacitated-dependent certification. A disabled child can stay covered past the age limit, and that approval often lives in a different system from the eligibility file.

The one that isn't wrong yet: COBRA

Priya Venkataraman's active coverage ended July 31. A $5,210.00 claim for an August 22 service paid on September 3, with no coverage on file. It looks like the Delgado pattern, but her COBRA election window is open until November 13. If she elects, coverage goes back to August 1 and the claim was always valid. Leon Marsh is the version of this that has already resolved: termed May 31, elected COBRA on July 20 retroactive to June 1, so his June 20 claim is clean.

So Venkataraman goes on the watch list, not the dispute list. Disputing a claim inside the election window means a reversal now and a reprocess later, two transactions for a claim that may be correct. The same reasoning applies on the bill side; see not wrong yet.

What it adds up to

$9,841.05 across seven claims for four people, plus $5,210.00 on watch, in one plan year of a 200-employee group. None of it would show up in a claims-experience report, because every one of these claims is ordinary: an urgent-care visit, an outpatient procedure, an office visit. Nothing about them is wrong except the date.

Stop-loss doesn't absorb them either. A stop-loss carrier reimburses claims for covered people, so an ineligible claim stays with the plan. It also sits in the aggregate accumulator, inflating claims at settlement until it's credited back. How that shows up in the stop-loss settlement →

See it in the self-funded sample audit: four people, seven claims, each classified by who owes it back, alongside the two that looked wrong and weren't. Open the self-funded sample audit →
← The premium side: termed but still billed Next: The stop-loss reimbursement that never arrived →

Who is your plan paying claims for?

Send us the paid-claims extract and your eligibility history. Every paid claim gets checked against coverage on its date of service, and every exception comes back with who owes it.

Book the 20-minute call

Four steps, and the first is a 20-minute call — no files, no member data. Or write to letslook@taresum.com.