Payroll took medical deductions from 47 employees. The carrier invoice lists 52.
So which number is right?
Probably neither, at least not without context. The invoice includes two terminated employees. A new hire is missing from payroll. One employee added a child, yet the carrier still has the old tier. Another name belongs to a COBRA participant.
This is what makes carrier billing reconciliation frustrating. Enrollment, payroll, carrier billing and COBRA administration keep separate records on different schedules.
One enrollment change moves through several clocks
An HR administrator enters a termination in the benefits platform. That action feels final. It is not.
The change waits for the next eligibility file, passes the carrier’s validation rules and posts to its membership system. Billing has its own cutoff. If the invoice was generated first, the employee stays on it. Enrollment shows the termination while the carrier’s ledger still reflects the previous month.
That timing gap often corrects on the next invoice. Retroactive changes are messier. When HR receives a termination late, the carrier has already billed beyond the employee’s last day. Someone must confirm the effective date, request the change and track the credit. Carrier contracts sometimes limit how far back credits go.
Late additions move in reverse. A new hire misses the carrier’s cutoff, then appears on the next invoice with both the current premium and a retroactive charge.
Life events rarely reach every system together
A birth changes the dependent roster, coverage tier, employee deduction and carrier premium. Those updates start with one event but do not travel as a package.
The employee submits documentation after payroll closes. Enrollment updates first, payroll catches the deduction on the next check and the carrier processes the dependent after billing. For a few weeks, three versions of the same enrollment exist.
Marriage and divorce create the same problem when documentation delays approval or the event is reported late. Removing a former spouse from enrollment does not change an invoice already in production. Adding a spouse after the effective date produces a retroactive charge. The invoice reflects one cutoff, not the whole story.
List-bill errors are built into the setup
With self-billing, the employer calculates the premium from its own eligibility data and sends the carrier the amount due. The employer controls the starting record.
List-billing works differently. The carrier produces a roster showing each covered employee, dependent, tier and premium. The employer then compares that roster with the benefits platform. Two ledgers exist, so differences have somewhere to hide.
This is also where small manual errors become monthly billing problems. A 5/1 effective date entered as 6/1 drops a month of premium. The wrong subgroup puts an employee on another division’s invoice. An unrelated credit offsets the bad charge. The total looks fine. The member detail is not.
Why is a terminated employee back on the bill?
Sometimes the answer is COBRA.
Active coverage ends, the carrier removes the record, and the former employee later elects COBRA retroactively. The carrier reinstates coverage, and the charges show up later. The billing arrangement determines whether they appear on the employer’s invoice or a separate bill.
That is why crossing out every terminated employee is a bad reconciliation method. The termination date, COBRA election, coverage period and premium collection all have to agree first.
Renewal is where small setup errors get expensive
One incorrect employee record affects one premium. One incorrect renewal rate affects everyone in that tier.
The benefits platform and payroll start using the new rates on the plan-year effective date, but the carrier invoice still reflects the old rate table. Or the rates are correct and a plan code is not. Either way, the first renewal invoice arrives with a difference repeated across dozens or hundreds of employees.
This is the one that actually costs money fast.
These are not harmless accounting differences
Paying for terminated employees wastes plan dollars. Missing an eligible employee creates unpaid claims and coverage disputes. Incorrect elections flow into payroll deductions and imputed income calculations. For ERISA-covered plans, approving carrier bills without reconciling eligibility creates fiduciary exposure. The plan is paying claims and premiums based on records no one has verified.
What actually fixes the problem
Monthly totals are not enough. Reconciliation has to happen at the member level, comparing employees, dependents, coverage tiers, effective dates and premiums.
Every discrepancy also needs an owner and a status. Was the carrier asked to correct it? Is a credit pending? Was the enrollment record wrong? Should the payment be adjusted? The item stays open until the expected charge or credit appears. Otherwise, the same discrepancy gets rediscovered next month.
That is the work handled through ebm’s Consolidated Carrier Billing & Reconciliation service. Carrier invoices are audited against enrollment data, discrepancies are coordinated with the employer and carrier, and the employer receives the premium due by carrier along with a summary of adjustments and expected credits.
