This is the same group as the premium sample audit. Harbor Point's medical plan is level-funded, so the list bill is only half of what the plan pays. The other half is claims, and the stop-loss contract that's supposed to cap them. This audit checks that half: every paid claim against coverage on its date of service, and every stop-loss accumulator against the contract.
What we received
- The paid-claims extract: Meridian's file for claims paid September 1, 2025 through October 31, 2026. 1,602 rows, reversals included, with the carrier's member ID, the patient, date of service, paid date, and paid amount. The layout doesn't matter; every administrator's is different, and mapping it is our job.
- Eligibility history: not a snapshot. Every person's coverage spans, with the date each change was entered, and COBRA election status. The entry date is what tells a missed change apart from a retro-term.
- The stop-loss policy schedule and Meridian's reports: $50,000 specific deductible, 12/15 basis, monthly aggregate factors, 50% surplus share, plus the large-claimant report and the preliminary aggregate accumulator.
The topline
$40,771.95 owed to the plan. Add the $4,812.66 from the August bill and one group's files turned up $45,584.61. Two of the people involved, Maria Delgado and Devon Carter, appear in both audits for the same reason: a change entered on time that the administrator never applied. On the bill it cost premium; in the claims extract it cost claims.
The findings
In the order we'd take them on the review call: anything on a clock first, then the administrator credits, then the watch list.
1 · Runout claims excluded: a 12/15 contract run as 12/12
Meridian credited $13,480.00 on $63,480.00 of claims paid by August 31. The contract counts claims incurred in the plan year and paid through November 30. Her two August claims, $8,734.20 and $3,191.40, paid in the runout and were never counted. She was already past the deductible, so every dollar of them is reimbursable.
Why it's first
The runout closes November 30, and the contract's filing deadline follows it. This is the item most likely to turn from recoverable to permanent while everyone waits for the final settlement. It's also systemic: an accumulator configured 12/12 will do this to every claimant whose care runs into August. The full arithmetic is in the stop-loss guide.
2 · One claimant, two member IDs, no reimbursement
Meridian reissued Grimaldi's member ID in March after an SSN correction. Its specific accumulator is keyed by member ID, so $41,860.00 and $27,145.30 each sat below the $50,000 deductible. Together they're $69,005.30, and $19,005.30 is reimbursable. The carrier's own large-claimant report lists him twice.
How it was caught
We accumulate by person, matched on identifiers that don't change, and carry every carrier ID the person has had. Seeing the same name and birth date twice on a large-claimant report is a two-second check, but only if someone is looking.
3 · Retro-term with no refund requested
Coverage ended March 31; HR entered the termination April 20, five days after the claim paid. The payment was correct when made and is an overpayment now. The fix is a provider refund request, and seven months later there isn't one on file.
Why it's on a clock
Retro-term recovery windows in administrative agreements, and refund limits in provider contracts and state law, both run from the payment date. Dana Whitcomb's record (below) shows the administrator can recover a retro-term. It just didn't for this one.
4 · Changes on file, not applied: the same two people as the bill audit
Delgado's termination was entered June 28, effective June 30. Her July and August claims paid 26 and 52 days after the termination was on file. Carter's spousal drop was entered April 22, effective April 30. His spouse's June and August claims paid 71 and 125 days after it.
The pattern read
These are the same two changes behind findings 1 and 2 of the premium audit. The administrator's eligibility never picked them up, so it kept billing and kept paying. The change was on file before every one of these payments, so this is the administrator's credit to the plan, not a provider refund. Disputing the premium alone recovers $1,742.68 and leaves $4,199.90 behind. More in the claims-after-termination guide.
5 · Dependent aged out, rule not applied
Owen turned 26 on March 12, so under the plan's end-of-birth-month rule his coverage ended March 31. The record has no end date, since nobody has to send one. His February claim is clean, and his May and July claims aren't.
One check before the dispute
We confirm there's no incapacitated-dependent certification on file. A disabled dependent can stay covered past 26, and that approval is often kept outside the eligibility file.
6 · Specific accumulator verified
Correct to the penny. It isn't an exception, but it's in the findings because it makes findings 1 and 2 provable: the same arithmetic that ties out for Lockhart doesn't tie out for Kowalczyk or Grimaldi.
On watch: not counted in the total
COBRA election still open: not wrong yet
Active coverage ended July 31 and the claim paid with no coverage on file. But her COBRA election window is open until November 13. If she elects, coverage goes back to August 1 and the claim is valid. We recheck after the deadline; disputing now would mean a reversal and a reprocess for a claim that may be correct. Same reasoning as timing exceptions on the bill.
Aggregate accumulator overstated: the settlement check
Meridian's preliminary aggregate is $40,771.95 too high. That's exactly the ineligible claims in findings 3–5 plus the uncredited specific excess in findings 1 and 2, still sitting in plan claims. It's not counted separately because it's the same money, seen from the settlement. At the 50% surplus share it means $20,385.98 more refund to Harbor Point, which is the number to confirm on the final settlement once findings 1–5 are credited.
Two that looked wrong and weren't
- Dana Whitcomb (HP0204): a $1,175.25 claim paid February 17, after her January 31 termination. The termination was a retro-term entered February 20, and the administrator reversed the claim on March 10. Net zero, recovered.
- Leon Marsh (HP0203): an $868.90 claim for June 20, after his May 31 termination. He elected COBRA on July 20, retroactive to June 1. Valid.
Both would show up on a naive "claims after term date" query. A finding list that includes them costs the administrator's trust on the first call, so we don't send one.
The exception register
One row per exception or watch item, expandable to the claims and accumulators behind it. Click any row.
| Exception | Who | Recovery route | Amount |
|---|
What ships with the audit
Behind each exception ships the backup the recovery needs: the claim lines cited by claim number, the eligibility span with its entry date, the contract term (basis, deductible, age rule) cited to the policy schedule, and the recomputed amount with its arithmetic. Administrator credits, provider refund requests, and stop-loss filings each get their own packet, because they go to different people.