OE Closes in March. The Audit Happens in June

This site contains affiliate links. View the disclosure for more information.

Picture Tara, eighteen months into her first benefits admin role. It’s the first Friday of January, and her Teams has been pinging since 7:14 a.m.

“Why is my deduction $284? It should be $112.”

“You took out family coverage. I waived family.”

“My HSA contribution is wrong. I didn’t want to contribute this year, and it’s still taking what I did last year?”

“I’m out $400 on this check. What happened?”

By Monday, it’s forty-seven employees. By Tuesday, her CHRO is standing in her doorway, holding, asking why Benefits didn’t catch this before it hit checks.

Here’s what Tara didn’t know:

The employee who’d moved from single to family at OE got billed at last year’s single rate. The employee who’d stopped her HSA contribution at OE still had last year’s bi-weekly amount pulled from her paycheck.

Forty-seven of them.

The fix wasn’t elegant. One month of reconciliation between prior-year deductions and new-plan-year deductions. Refunds for the overcharged. Arrearages collected from the under-deducted. Phone calls. Spreadsheets. Apologies. One difficult conversation with a CHRO who wanted to know why this hadn’t been caught before checks ran.

I know this story because it’s mine. Different company, different ben admin system, same brutal recovery.

Tara isn’t bad at her job. Nobody told her the payroll calendar inside her Ben Admin doesn’t auto-roll. Nobody told her that this — not the November push — is where careers get saved or quietly unraveled.

This is the post nobody wrote for me when I was Tara.

What everyone gets wrong about open enrollment

Here’s the part most benefits admins don’t realize in their first or second OE:

When you close the enrollment portal, you’re at the halfway point. Not the end. The middle.

Here’s the part most benefits content gets wrong: the portal closes in November, but OE doesn’t actually close until March 15. That’s when the prior-year FSA grace period ends — the last day employees can spend down last year’s pre-tax dollars. It’s also the moment any employee who moved from a PPO with a Healthcare FSA to an HDHP can finally start HSA contributions on April 1. Until then, OE is still settling.

Open enrollment, the way most content treats it, runs from announcement to close — about six weeks. Then you exhale and move on.

The other half — the part nobody talks about — runs from the close of OE through about March. That’s when the data you submitted in November has to flow through to carriers, payroll, your HSA (Health Savings Account) vendor, your FSA (Flexible Spending Account) administrator, your COBRA TPA (third-party administrator handling COBRA continuation coverage), and every voluntary benefit carrier you forgot you had.

Each handoff is a place something can go silently wrong.

And then the first paycheck drops and forty-seven people ping you in one day. Or three months later, an employee calls crying about a Medicare denial you never saw coming. (I told that one in my Post-OE Audit field guide — different phase, same root cause.) Or your AP (Accounts Payable) team flags you’ve been paying premiums for someone who terminated in January.

These are not freak occurrences. They are the predictable cost of treating OE as “done” when the portal closes.

Know your integration type

Before you can audit anything, you need to know what kind of relationship your ben admin has with your payroll system. There are three flavors, and the failure modes are different in each one. If you don’t know which one is yours, that’s the first question to bring to payroll.

1. Bundled systems. HRIS, Ben Admin, and Payroll all under one roof. Gusto. Rippling. ADP Workforce Now. Paylocity. The promise: one system, one source of truth. The risk: you assume everything talks to itself, so you stop checking. Bundled systems still have configuration that can drift — deduction codes that don’t auto-create for new plans, calendars that need manual rollover, effective dates that didn’t carry. “All one system” is not the same as “all in sync.”

2. API-integrated separate systems. HRIS in one platform, Ben Admin in another, with an API connecting them. Oracle HCM + Benefitsolver. UKG + PlanSource. Workday + a benefits TPA. The promise: real-time sync. The reality: integrations have parent-child relationships, and if those aren’t configured right, updates in the Ben Admin don’t actually flow through. We had a UKG + PlanSource setup where the new payroll calendar was correctly updated in PlanSource. It didn’t feed UKG. The parent-child relationship between the two systems wasn’t mapped the way the team assumed. New plan year deductions never triggered.

3. File-feed or manual import. Still common in mid-market and government. The ben admin holds the elections; payroll holds the deductions; someone has to push a file or manually import the new-plan-year amounts. Oracle HRIS + Benefitsolver ben admin worked this way for us — the new plan year deductions had to be imported into Oracle. Miss the import? Payroll runs with last year’s amounts. Do the import wrong? Same outcome.

If you’re reading this and don’t know which type you have, that’s the first thing to figure out. Ask your payroll partner: “How do new-plan-year deductions actually get from our ben admin into payroll? Is it automatic, an API, a file, or a manual import?” The answer tells you which failure modes to watch for.

What usually goes wrong between November and March

The mid-year audit doesn’t exist because admins are sloppy. It exists because the systems we trust to talk to each other don’t always do it cleanly.

• Pay period ending dates didn’t roll forward for the new plan year. Pay dates updated. PPE dates didn’t. The system bucketed January checks into December’s pay period and pulled prior-year rates. This is the trap nobody warns you about.
• The payroll calendar inside the Ben Admin didn’t roll forward at all. New plan year arrives. The calendar still shows last year. One month of my life, on one missed checkbox.
• The Ben Admin / Payroll integration broke during the new-plan-year handoff. Family-tier elections get billed at single rates. New elections don’t get deducted. Green on the screen, wrong on the paystub.
• The Send Deductions Date was set wrong or never set. This is the date your ben admin transmits new-plan-year deductions to payroll. Set it after the first paycheck runs, and your first January check goes out at prior-year rates. Most new admins don’t know this date exists — their payroll partner sets it, or nobody does.
• For API integrations: parent-child company IDs were missing the new deduction codes. If your payroll runs multiple company IDs or pay groups, every deduction code has to exist in every child company — not just the parent. Miss one, and that group’s deductions don’t transmit.
• The OE file feeds out with null values in term-date fields. The carrier reads nulls as “still active.” Terminations don’t take effect. The employee calls Medicare six months later in tears.
• FSAs don’t roll. Employees assume they do. January 1 they zero out and call you in tears. $1,800 in vanished pre-tax money is a lot of tears.
• PPO + Healthcare FSA migrants to an HDHP start contributing to an HSA on January 1, not knowing the FSA grace period keeps them on a disqualifying plan until April. The IRS excise tax letter shows up in April.
• Required notices (SBC, WHCRA, Patient Protection, HIPAA, Medicare Part D Creditable Coverage) get duplicated or skipped, with no proof of delivery on file.
• Carrier invoices keep billing for terminated employees. By the time AP flags it, the contractual refund window has closed, and the company eats the loss.

What to do instead — the five-phase mid-year audit

I built the five-phase post-OE audit after I lived through that payroll calendar disaster. Once you spend one month unwinding refunds and arrearages on forty-seven employees, you never want to depend on luck again.

• Phase 1 — File feed audit. Pull every OE file that fed out to a carrier. Reconcile termination counts, adds, and tier changes against your ben admin. Ask each carrier in writing how they interpret null values in your term-date field. The answer is different at every one.
• Phase 2 — Notices distribution. Read your OE guide cover to cover. Most required notices are bundled inside it. Stop duplicating distribution. Build proof of delivery for the few that need standalone treatment.
• Phase 3 — What doesn’t roll. Flag every election type that doesn’t carry forward, plus the plan-interaction traps. Tell the specific people about to lose money or get an IRS letter, by name, before it happens.
• Phase 4 — Pre-payroll reconciliation. This is where Tara lost one month. Before the first January paycheck runs, sit down with payroll — not adjacent, with — and walk through six questions together:
  • (1) Is the payroll calendar loaded for the new plan year, with pay dates AND pay period ending dates?
  • (2) Are all new plan-year deduction codes set up in payroll?
  • (3) How do the new deduction amounts get from the ben admin to payroll — manual import, file feed, or API?
  • (4) For API integrations, do all parent-child company IDs have the new deduction codes?
  • (5) What’s the Send Deductions Date, and is it before the first paycheck of the new year?
  • (6) Run a sample payroll preview and reconcile twenty employees across coverage tiers, line by line, against the ben admin elections. Payroll is the only team that can catch a calendar mismatch before checks run. Treat them like the partner they actually are, not the team you call when something’s wrong.
• Phase 5 — Year-round rechecks.
  • Calendar reminders for January (first feed check)
  • February (silent errors)
  • March 15 (FSA grace closes — OE is finally done)
  • April (HSA eligibility check for HDHP migrants)
  • June (mid-year full audit)
  • September (pre-OE cleanup), and October 15 (Medicare Part D).
• The calendar is the unsexy tool that saves careers. I run mine in Notion because the recurring logic holds and the views travel with me across roles. 90-Day Playbook post on building your benefits calendar

Here’s the part that makes June the last ‘easy’ month: the catch window is the calendar year. Catch a wrong deduction in January, and it’s a refund cycle. Catch it in June, and it’s still a refund cycle — the year’s still open, the corrections are routine, no tax forms are touched.

Catch it the following January after W2s have shipped, and you’re into W2-Cs, amended 941s, and forty-seven employees filing 1040-X amended tax returns because of something HR didn’t catch in time. Same error. Wildly different recovery. The year is the window.

WHAT I WISH SOMEONE HAD TOLD ME

The payroll calendar in your Ben Admin doesn’t auto-roll. Pay period ending dates don’t auto-roll. Send Deductions Dates don’t auto-roll. Deduction codes in parent-child company IDs don’t auto-create. Manual imports don’t happen on their own. Every one of these is a checkpoint someone has to own. If you’re not sure who owns it, the answer is: you — until you sit with payroll and confirm otherwise. Your ben admin and payroll are married. The integration is the contract. And like any contract, it only works if both parties read it every year.

Where to start

If you’ve never run a post-OE audit, start with the free Post-OE Audit field guide. Five phases. A companion Excel tracker that auto-calculates the dollar variance between your ben admin and your payroll preview. Read it. Fill in what applies. Keep it year over year. The patterns are where the real insight lives.

For the full OE execution system — kickoff through close through the mid-year audit, with the 34-page playbook, the 9-tab Excel rate calculator, and the OE Timeline Checklist — that’s the OE Mastery Kit. The audit is the diagnostic. The Kit is the system.

Either way, get the second Tuesday in June on your calendar. Block four hours. Pull your reports. Call payroll. Run the cross-reference.

The next Tara on your team — or the one looking back at you in the mirror next January — is the one who never has to send those Teams messages.

This site contains affiliate links. View the disclosure for more information.