Post: How an HR of One Cleaned Up a $500K Carrier Overpayment: A Case Study
An HR-of-one inherited a benefits operation with a $500,000 carrier balance the CEO wanted explained by Monday. The cleanup took fourteen weeks. The final reconciliation produced a $214,000 credit, a stable file feed, and a forward process the carrier and the HRIS partner both signed off on. This case study walks through the methodology that produced that outcome — and what the HR leader changed about her communication with the CEO along the way.
This is a representative composite case based on patterns we see across 4Spot client work. The HR leader is referenced as “the HR director” rather than by name. Dollar figures and timelines are illustrative of the methodology described in our pillar.
The execution framework is documented in our pillar on fixing broken HR operations and the specific reconciliation methodology lives in our carrier feed reconciliation guide.
Summary
- Initial carrier balance: $507,000 reported by the carrier
- Final credit: $214,000 after reconciliation
- Net carrier balance: $293,000 (genuine premium owed)
- Cleanup duration: 14 weeks
- Headcount: ~1,050 employees
- HR team: One benefits administrator (the protagonist)
Before / After
| Metric | Before | After |
|---|---|---|
| File feed success rate | 72% | 99.4% |
| Open enrollment discrepancies | 147 unresolved | 3 unresolved |
| Monthly reconciliation cadence | None | Weekly |
| Carrier balance | $507,000 | $293,000 (validated) |
| HR-to-carrier escalation path | Customer service rep only | Named technical lead |
| Weekly CEO updates | Reactive only | Written, every Friday |
Context
The HR director inherited the operation seven months after a payroll-and-benefits platform migration. The implementation partner had walked away. The file feed had never fully stabilized. By the time she opened the carrier portal, twenty-six different employees had pending enrollment changes that had been rejected for various reasons. The carrier invoice was $507,000 over what HR records supported. The CEO wanted an estimate of how much should be credited back.
Her first instinct was to start submitting individual corrections. That instinct was wrong, and recognizing it was wrong became the first turning point.
Approach
Step one was to freeze new corrections. She emailed the carrier account manager and asked for a hold on individual adjustments pending a full reconciliation pass. The carrier agreed and sent a written acknowledgment.
Step two was the file feed log pull. The HRIS exposed six months of transmission history. She categorized every failed transmission by reason code: 42% were data quality errors on the HRIS side, 31% were mapping errors between the HRIS and the carrier, 19% were exception-handling errors on the carrier side, and the remaining 8% were carrier billing errors with no underlying record at all.
Step three was assembling the right meeting. She refused to take the carrier customer service rep as the technical owner. She escalated to her account manager and requested the carrier’s technical implementation lead. The first meeting included her, the HRIS implementation partner she pulled back in (paid hourly), the benefits broker, the carrier account manager, and the carrier technical lead.
Implementation
The first meeting produced a written ownership grid covering every category of discrepancy. The HRIS partner owned the data quality fixes. The carrier owned the exception-handling and billing errors. The benefits broker owned the eligibility logic review.
Weeks 3–6 were execution. The HRIS partner rebuilt the eligibility logic that had been mis-configured at implementation. The carrier reissued enrollment confirmations for 84 employees whose records had been quietly dropped during transmission failures. The broker audited the plan elections against payroll deductions and surfaced eleven cases where the wrong plan tier had been deducted from payroll.
Weeks 7–9 were the formal reconciliation. The carrier produced a line-by-line statement comparing billed coverage to confirmed enrollment. The HR director audited the statement against her HRIS records and identified twenty-two additional discrepancies the carrier had missed. The statement was revised. The final credit landed at $214,000.
Weeks 10–14 were the forward process. The HRIS partner configured weekly reconciliation reporting using Make.com to compare HRIS active enrollments against carrier-confirmed enrollments. Any delta above a small threshold automatically generated a ticket. The CEO received a written weekly update every Friday throughout, summarizing progress in three sentences per workstream.
Results
The reconciliation closed at the start of week 15. The carrier credited $214,000. The file feed success rate moved from 72% to 99.4% by week 10 and held there. Open enrollment discrepancies dropped from 147 unresolved cases to 3 — all of which had legitimate documentation explanations.
The forward process held through the next open enrollment cycle without producing new reconciliation work. The HR director ran one more spot-check at the six-month mark; the file feed was clean.
The CEO conversation also changed. Through the cleanup, the HR director sent a Friday written update that quantified status in dollars and exposure. When she eventually requested approval for an HRIS configuration retainer to maintain the forward process, the CEO signed off in one email.
Lessons Learned
The first lesson is that individual corrections during a reconciliation make the reconciliation harder. The freeze is the first act of the cleanup, not the last.
The second lesson is that the right meeting attendee list determines the outcome. Customer service reps cannot authorize engineering work on the carrier side. The technical implementation lead can. Insist on the right attendee or the meeting will not produce decisions.
The third lesson is that the forward process matters more than the historical credit. The $214,000 credit was a one-time event. The 99.4% file feed success rate prevents the next $500,000 reconciliation from happening at all. Standardize first, automate second — the 4Spot thesis applied to a real carrier feed problem.
The fourth lesson is that weekly written updates are the cheapest form of insurance an HR leader can buy. By the time the resource ask came up, the CEO was not learning about the problem. He was signing off on a solution he had been watching unfold for three months.
Next Steps
If you are sitting on a carrier balance you cannot explain, the methodology above is the playbook. The detailed step-by-step is in our carrier feed reconciliation guide. The broader triage framework lives in the pillar. For the specific Make.com configuration that enabled the weekly reconciliation reporting in this case, contact 4Spot for an implementation scope.
