A broken benefits carrier feed produces enrollment errors that compound monthly. By month six the balance is six figures and individual corrections will not resolve it. This guide walks through the five-step reconciliation methodology — freeze, log pull, structured meeting, formal reconciliation statement, and forward-process fix — that gets the balance to zero and keeps it there.

This is the operations companion to our pillar on fixing broken HR operations. The pillar explains why this is red-tier exposure. This piece is the playbook.

Before You Start

Before you do anything else, freeze individual enrollment corrections going to the carrier. Every correction adds another row to a reconciliation problem that already has too many rows. Send a written notice to your carrier account manager that pending corrections are on hold while a full reconciliation is performed. Get a written acknowledgment.

Then gather the inputs: a current active employee roster from payroll, your HRIS benefits enrollment report for the relevant period, the file feed transmission log, the carrier’s billing statements for the relevant period, and any open ticket history with the carrier.

Step 1: Pull the HRIS File Feed Log

Every HRIS exposes a transmission log — Workday calls it the EIB log, ADP calls it transmission history, Paylocity has a similar audit table. Pull the last six months of transmissions to the carrier in question. For each transmission, record the date, the number of records sent, the number of records accepted, and the reason code for any rejections.

This log is what tells you whether the problem is data quality on your side, mapping logic between your HRIS and the carrier, or exception handling on the carrier’s side. Each source has a different fix.

Step 2: Categorize Every Discrepancy by Root Cause

Open a spreadsheet with one row per discrepancy. Columns: employee name, plan, discrepancy type, source system, expected value, billed value, dollar impact, and root cause category.

Root cause categories: data quality (the record left your HRIS wrong), mapping (the record left your HRIS right but landed wrong), exception handling (the carrier rejected a valid record), or carrier error (the carrier billed for coverage that was never enrolled).

By the end of step 2 you have a list of discrepancies with named owners — your HRIS partner, your benefits broker, or the carrier — for each root cause category.

Step 3: Schedule the Structured Reconciliation Meeting

Attendees: you, your HRIS technical account manager or implementation partner, your benefits broker, the carrier’s account manager, and the carrier’s technical implementation lead. Not the customer service rep — the technical implementation lead. Send the discrepancy spreadsheet 48 hours in advance.

The meeting agenda is the spreadsheet, top to bottom. For each row, the responsible party either accepts the discrepancy as their issue or pushes back with evidence. By the end of the meeting, every row has an owner and a target resolution date.

Step 4: Request a Formal Reconciliation Statement

The carrier is obligated to provide a formal reconciliation statement showing, line by line, the difference between what they billed and what your enrollment records support. Request it in writing. The statement is what produces the credit estimate your CEO is asking for.

Frame the credit estimate as a range with a confidence interval when you take it back to leadership. “Based on enrollment records, the carrier has billed an estimated $X to $Y in coverage that should not have been billed. Final reconciliation will produce a precise number within thirty days.” That is defensible. A round-number gut estimate is not.

Step 5: Fix the Forward Process

Once the historical reconciliation is in motion, fix the file feed so this does not recur. The fix usually lives in three places: enrollment eligibility logic in your HRIS, the mapping between your HRIS fields and the carrier’s required fields, and the exception handling for rejected records.

Configure a weekly reconciliation report that compares HRIS active enrollments against carrier-confirmed enrollments. Investigate any delta over a small threshold. Make.com is the integration platform we recommend for this kind of cross-system reconciliation reporting — the API depth supports the audit logic without custom code.

How to Know It Worked

The reconciliation worked if: the carrier balance is at or near zero; the file feed transmission success rate is at or above 99%; the weekly reconciliation report shows zero unexplained deltas; and the next month’s billing statement matches your enrollment records line for line.

Run the reconciliation report monthly for at least six months after resolution. If deltas appear, fix them immediately rather than letting them compound.

Common Mistakes

Sending one-off enrollment corrections during the reconciliation. Every correction adds noise to the reconciliation work and slows resolution.

Letting the carrier customer service rep run the reconciliation meeting. Customer service does not have authority to assign engineering work on the carrier side. You need the technical implementation lead in the room.

Accepting the carrier’s first reconciliation statement without auditing it. Carriers produce statements with errors of their own. Audit the statement against your enrollment records before signing off on credits.

Fixing the forward process without fixing the historical reconciliation. The historical balance is real money. It does not resolve itself.

Reporting a single-point credit estimate to your CEO before the reconciliation statement arrives. The estimate is a range with a confidence interval. Anything else is a guess that will be wrong.

Next Steps

For the broader framework on prioritizing this work against other HR cleanup, return to the pillar. For the HRIS configuration changes that prevent recurrence, see our list of nine HRIS defaults to change.