The setup
An employee drops spousal coverage effective May 1 — spouse picked up coverage at their own job. The change is entered in the ben-admin system on May 3, well inside any reasonable cutoff. The EDI file goes out. Everything looks done.
The carrier's June bill shows the employee at EE+SP. So does July's. So does August's.
| Bill month | Should bill (EE) | Carrier billed (EE+SP) | Overcharge | Cumulative |
|---|---|---|---|---|
| June | $320.09 | $687.59 | $367.50 | $367.50 |
| July | $320.09 | $687.59 | $367.50 | $735.00 |
| August | $320.09 | $687.59 | $367.50 | $1,102.50 |
Why nobody sees it
On a 300-life group billing roughly $120,000 a month, $367.50 is three tenths of one percent. The month-over-month total moves more than that from ordinary churn — new hires, terms, plan changes. Totals-level review is structurally incapable of catching this class of error, no matter how careful the reviewer is.
And the one person who would notice — the employee — has no reason to. Their payroll deduction was updated correctly by the ben-admin system in May. The employer eats the difference between what payroll collects and what the carrier bills, which is precisely why this error is so common and so quiet: the error lives in the one gap nobody's paycheck depends on.
The clock: retroactivity limits
Most carrier agreements cap retroactive premium adjustments — 60 days and 90 days are the common numbers; some contracts express it as one or two billing cycles. The cap exists for legitimate reasons (carriers can't reopen closed financial periods forever), but the operational consequence is brutal:
This is why an annual audit — the way most groups do it, if they do it at all — recovers so much less than it finds. Finding a twelve-month-old error is an autopsy. Finding a one-month-old error is a refund.
The part that defeats spreadsheets: the three-amount problem
Here's where retro work gets genuinely hard. Suppose the carrier partially fixed it: after a call in July, they applied one month of credit, but their system corrected from the wrong start date. Now the true remaining recovery for June is:
what it should have been − what was originally billed − what was already credited on a later bill
Three amounts, per member, per plan, per affected month — where the credit for June might appear on the August bill, labeled with a description only the carrier's system understands. Once a group has a handful of these in flight, the reconciliation isn't a spreadsheet exercise anymore; it's a data-matching problem across multiple billing periods. Analysts resolve it by sampling and judgment, which is exactly how partial credits get accepted as full ones.
An audit that recomputes every line against every open prior period does this matching mechanically: each retro exception nets original charge, current expectation, and any credits already applied — so the dispute you send the carrier is the remaining delta, not a number they can bounce back with "we already adjusted that."
What to do with this
- Find your retro cap. It's in the carrier agreement or the group policy's premium provisions. If you don't know it, you're negotiating every recovery from a position of weakness.
- Treat the adjustment section of the bill as evidence, not noise — every credit/rebill pair is the carrier telling you their record of your group changed. Verify the arithmetic. (More on this in the adjustment-noise guide.)
- Reconcile monthly, not annually. The math above is the entire argument: monthly reconciliation keeps every error inside the window.