River
Y CombinatorBacked by Y Combinator

People & Exec SupportFree

Reconcile Benefits Invoice to Enrollment

The March invoice looked 1.9 percent off. Underneath it were 37 people, four different problems and 19,572 already past the recovery window.

Start here

River matches three sources per person, per plan, per month: the carrier invoice, the enrollment file your HRIS sends, and the payroll deduction register. A two-way match against the invoice finds terminated employees still being billed. It cannot find the four people whose payroll is deducting for coverage the carrier has no record of, because that error never touches the invoice at all. In the worked example the three-way match found 37 people across four different problems.

The second mechanism is that variances are never netted. Marloe Logistics was over-billed 16,386 and under-billed 11,244 on the same March invoice, so the net was 5,142 and looked like rounding. Those are four separate problems with four different owners and four different remedies: a credit request to the carrier, a coverage gap with claims exposure, money owed back to an employee, and money the company quietly absorbed. Netting them produces one number nobody can act on. The termination that never reached the carrier is the same failure as the login nobody disabled.

Third, every variance is aged against the recovery window in your carrier contract. Nine terminated employees had been billed for 31 person-months and 42,016. At a 60-day retroactive termination limit, 22,444 of that is recoverable and 19,572 is gone. Which line a variance falls on is the only fact that decides what to do about it, and it is the argument for running this monthly rather than at renewal, when most of it has already expired. Choosing the plan happens further upstream, in the renewal analysis that priced this year's options before enrollment opened.

The carrier bills from its own records, and nothing makes them match yours

A carrier invoices from its own enrollment database. That database changes only when your enrollment file changes it, and the transaction that carries the change is a federally adopted standard, the ASC X12N 834 benefit enrollment and maintenance transaction (45 CFR 162.1502). Nothing in that standard obliges anybody to reconcile the result. A termination that fails validation on Tuesday produces an acknowledgement in a queue somebody set up two years ago, and the employee stays on the invoice until a human notices.

Presence is the easy half. The expensive half is tier, because a tier change has three destinations and they update on three different clocks. An employee adds a spouse after a qualifying event, which a cafeteria plan permits mid-year under the change in status rules (26 CFR 1.125-4). The enrollment system takes it immediately, payroll takes it next period, and the carrier takes it when the file lands. Match presence only and eleven tier mismatches never appear.

The direction of a variance decides who owns it, which is why they do not get netted. Billed and not enrolled is a credit request. Enrolled and not billed is a person with no coverage on file, and a denied claim is how they find out. Deducted and not enrolled is money taken from an employee for something they do not have. Enrolled and not deducted is under-collection the company usually eats, because reaching back for six months of missed premium is a conversation nobody wants.

How it works

  1. Send three files

    The carrier invoice, the enrollment extract or 834 your HRIS sends, and the payroll deduction register.

  2. Everyone gets matched

    Per person, per plan, per month. Presence first, then tier and plan, because the tier errors are the persistent ones.

  3. Variances split four ways

    By direction, never netted, each routed to the person who can actually fix it.

  4. Recovery gets a deadline

    Each variance aged against the retro-termination window, with the credit request drafted and the unrecoverable total stated plainly.

What you get

  • A per person, per plan, per month match across carrier invoice, enrollment file and payroll register
  • Variances split by direction into four types, never netted, each with its own owner and remedy
  • Tier and plan matched separately from presence, which is where the ongoing overpayment actually lives
  • Every variance aged against your carrier's retroactive termination window and split into recoverable and gone
  • A drafted credit request naming each person, each month and each amount, ready to send
  • The enrollment corrections your HRIS needs to send, listed as changes rather than as errors
  • The employee-facing list: who is owed a refund, who was under-deducted, and what to say

Common questions

Is the recovery actually worth the effort?

Marloe's nine terminated employees had been billed 42,016 across 31 person-months. Inside a 60-day retroactive termination window, 22,444 comes back and 19,572 does not. The unrecoverable number is the more useful one, because it is what seven months without a reconciliation cost, and it repeats every year until somebody runs it monthly.

Why not just check the invoice against a headcount?

Because the net looks fine. Marloe was over-billed 16,386 and under-billed 11,244 in the same month, so the invoice sat 1.9 percent off a headcount check and nothing looked wrong. The gross was 27,630 across 37 people, and the two halves have opposite remedies and different owners.

What is the worst of the four variance types?

Deducted and not enrolled. Four people had premium coming out of their pay for coverage the carrier had no record of, 3,880 in total. It is the smallest number on the page and the only one where somebody presents an insurance card and is told they have none. The signed election form should be in the compliance file.

Why do tier mismatches matter more than terminations?

A termination is a one-off that ends when you catch it. A tier mismatch bills every month until somebody looks, and it hides because the person is legitimately on the invoice. Eleven of them ran 4,470 over and 2,200 under in a single month, on rows a presence check passes without comment.

Where do these errors come from?

Offboarding, mostly. A termination that never reached the carrier is the same failure as the login nobody disabled: a checklist item with no confirmation step behind it. New hires are the mirror image, which is why enrollment belongs on the onboarding register with an owner and a date.

Does this pick up COBRA problems?

It flags the people who should have been offered it. A terminated employee still on the active invoice usually means no election notice went out either, and the administrator has 14 days from receiving notice of a qualifying event (29 CFR 2590.606-4). The list of nine is the same list.

How often should this run?

Monthly, with the invoice. Marloe ran it once in seven months and 19,572 expired inside the gap. Renewal-time reconciliation finds everything and recovers almost none of it, because the retroactive termination window in most carrier contracts is measured in weeks rather than quarters.

Reconcile Benefits Invoice to Enrollment

Fill in the form and your workspace opens with the work already underway.