The setup
An employee terminates March 31. The termination is keyed late, so the carrier's April bill charges a full month for them. Then the corrections start arriving:
| Bill | Line for this member | Amount |
|---|---|---|
| April | April premium | $320.09 |
| May | Retro credit — April | −$320.09 |
| June | Retro credit — April | −$320.09 |
Look at June's bill on its own and the line is reasonable: a terminated employee, a credit for a month after their termination. That's what a term correction is supposed to look like. It gets accepted.
It's the second credit for the same month.
The three-amount test
Any adjustment for a past month has to be checked against three amounts, not one:
what it should have been − what was originally billed − what has already been adjusted, on any later bill
| April, this member | Amount |
|---|---|
| What it should have been (termed 3/31) | $0.00 |
| What was originally billed (April bill) | $320.09 |
| Already adjusted (May bill) | −$320.09 |
| Still owed by the carrier, before June | $0.00 |
| Credited again on June bill | −$320.09 |
| Over-credited | $320.09 |
The June credit has nothing left to offset. It's money the carrier will want back.
The subtler version: a partial credit, then a full one
Exact duplicates are the easy case, because the amounts match. The harder case is a correction that gets made twice, once wrong and once right.
A second member drops spousal coverage effective May 1. EE is $320.09, EE+SP is $687.59, and May was billed at EE+SP. The carrier's first correction works from the wrong date and credits half the difference. A later reprocessing credits the full difference without accounting for the first one:
| May, second member | Amount |
|---|---|
| What it should have been (EE) | $320.09 |
| What was originally billed (EE+SP) | $687.59 |
| Already adjusted (June bill, partial) | −$183.75 |
| Still owed by the carrier | $183.75 |
| Credited on July bill | −$367.50 |
| Over-credited | $183.75 |
Nothing about the July line looks wrong. −$367.50 is exactly the EE+SP → EE difference, the amount an analyst would expect to see. It's only an over-credit when you remember June.
Why carriers produce them
Carrier systems commonly regenerate retroactive adjustments whenever a member's record is touched again: a termination re-sent on a full file, a correction to an unrelated field, a manual fix by a service rep after a phone call. Not every system checks what it has already credited for that member and month before issuing another credit. Eventually a reconciliation on the carrier's side finds the excess, and it comes back as a debit.
Why this is expensive under consolidated billing
If the employer group pays the carrier directly, a duplicate credit is mostly a timing nuisance. The money comes and goes on the same account.
If you're in the middle, paying carriers and invoicing groups, the timeline looks like this:
| When | Carrier side | Group side |
|---|---|---|
| June | Duplicate credit received: −$320.09 | — |
| July | — | Credit passed through on the group's invoice: −$320.09 |
| September | Clawback: +$320.09, labeled only "adjustment" | Already credited; nothing to offset it |
Now there are two bad options: go back to the employer and re-bill a credit you told them they'd earned, with an explanation that's hard to make sound competent, or absorb it. And the September debit has its own risk. With no context attached, an analyst who doesn't connect it to June may dispute a legitimate charge, which starts another round.
Index adjustments by the month they're for
The structural fix is in how adjustments are stored. Most reconciliations file an adjustment under the bill it arrived on. Netting requires filing it under the member, plan, and coverage month it corrects, so that every bill's contribution to that month (original charge, partial fixes, full fixes, reversals) sits together and adds up to one remaining balance.
- Key: member + plan + coverage month (+ tier where tiers can change mid-period).
- Look back far enough. Corrections for a month can arrive on any of the next several bills. The lookback should match the longest retro window on any contract in the book.
- Net before you pass through. Only the remaining balance should reach the group's invoice. Excess credits get held as a liability until the carrier collects them, or are reported to the carrier proactively. Reporting a duplicate before it's clawed back is the cheapest credibility you'll ever buy in a future dispute.
What to do with this
- Check every retro credit against the full history for that member-month, not against the bill it appears on.
- Treat credits that exactly match a common rate difference as more suspicious when a prior credit exists, not less.
- Don't pass credits to groups until they've been netted.
- When an unexplained "adjustment" debit arrives, search for an earlier over-credit before disputing it.