What does benefits administration cover?
Employee benefits administration is the operational side of your benefits program. It decides who is covered, in which plan, at what cost, and keeps that answer the same in every system that needs it: your HR system, payroll, each carrier or TPA, and the invoices you pay.
The work falls into a cycle that repeats all year:
| Step | What happens | Where it goes wrong |
|---|---|---|
| Enrollment and eligibility | New hires, open enrollment and terminations are entered and checked against plan eligibility rules | Eligibility rules applied inconsistently |
| Carrier data feeds | Elections are sent to carriers and TPAs, usually in 834 files | Feeds fail or drop records without anyone noticing |
| Payroll deductions | Employee contributions are deducted to match elections | Deduction codes don’t match the plan or tier |
| Invoice reconciliation | Carrier bills are checked against enrollment and deductions | Paying for people who left months ago |
| Life events | Marriages, births, divorces and loss of other coverage are processed mid-year | Late or undocumented changes |
| COBRA handoff | Qualifying events are sent to whoever runs COBRA | Missed notices |
| ACA tracking | Hours and offers of coverage are tracked for ACA reporting | Variable-hour employees measured wrong |
Benefits administration is different from claims administration. A third party administrator pays medical claims for a self-funded plan. Benefits administration makes sure the TPA or carrier has the right list of people to pay claims for.
Who can enroll, and how is it checked?
Your plan document and eligibility rules decide who can enroll: which employees, after what waiting period, and which dependents. Enrollment is where every downstream number comes from, so it has to be right the first time.
A sound enrollment process does four things:
- Applies the same rules to everyone. Eligibility should follow the plan document exactly, including waiting periods, hours requirements and dependent age limits.
- Verifies dependents. Ask for documentation when a spouse or child is added, so the plan doesn’t pay claims for people who aren’t eligible.
- Captures waivers. Record when an employee declines coverage. You will need it for ACA reporting and if the employee later disputes an offer.
- Ends coverage on time. Terminations are the most common gap. If HR knows someone left but the carrier doesn’t, the plan keeps paying premiums or claims.
What should ben admin technology do?
Ben admin technology should hold your plan rules, take employee elections and send the results to payroll and carriers without anyone re-keying them. Most employers run enrollment through a benefits administration platform, either standalone or as a module of their HR and payroll system.
When you choose or review a platform, look at:
- Payroll integration. Elections should flow to payroll deduction codes without being re-keyed.
- Carrier connections. Which of your carriers and TPAs get an automated file, and which still get manual updates or spreadsheets.
- Rules engine. Whether it enforces your eligibility rules, waiting periods and life event windows, or leaves them to whoever is keying the change.
- Reporting. Whether you can pull enrollment by plan and tier to reconcile invoices.
- Error handling. Who is told when a carrier file fails, and how fast.
Technology handles volume. It does not catch a rule that was set up wrong, so test new plans and tiers before open enrollment goes live.
How do 834 file feeds work?
An 834 feed sends your enrollment data to each carrier or TPA in the standard electronic format for health plan enrollment. The file’s formal name is the ASC X12 Benefit Enrollment and Maintenance (834) transaction, and it is the HIPAA standard for enrollment and disenrollment transactions. Most carriers and TPAs accept it.
Your benefits platform builds the 834 from your enrollment records and sends it to each carrier at regular intervals, often weekly. Files can be full files, which send the whole population each time, or change files, which send only what changed since the last one.
Problems with 834 feeds are usually quiet. A file rejects, a record fails a carrier edit, or a new plan code isn’t mapped, and nobody is told. The employee finds out at the pharmacy counter. To prevent this:
- Get error reports from each carrier after every file, and assign someone to clear them.
- Run a full file periodically, even if you normally send change files, to catch drift.
- Compare carrier rosters to your system at least quarterly, plan by plan.
How should payroll deductions be reconciled?
Reconcile deductions against enrollment every payroll cycle, or at least monthly, so every election has a matching deduction at the right amount, tier and tax treatment. Health premiums paid by employees are usually taken pre-tax through a Section 125 cafeteria plan, which limits mid-year changes to events the plan allows.
Look for employees with coverage but no deduction, deductions without coverage, and the wrong tier, such as employee-only deductions for family coverage.
Employee contributions also carry a fiduciary duty. The DOL treats contributions withheld from employees as plan assets, so they must be used only for the plan and handled under its plan asset rules.
How do you reconcile carrier invoices?
Each month, compare every carrier invoice to your enrollment and to what you deducted from payroll. The three should agree by person, plan and tier.
Billing errors tend to fall into a few patterns:
- Former employees still billed because a termination never reached the carrier.
- Wrong tier, such as single coverage billed after a dependent was added, or the reverse.
- Retroactive changes the carrier didn’t apply, or applied twice.
- Rate errors after renewal, when new rates weren’t loaded.
Carriers often limit how far back they will credit a retroactive termination, so an error found in month six may not be fully recoverable. That is the main reason to reconcile monthly instead of annually. On a self-funded plan, the same check applies to the TPA’s administration and stop-loss bills, which are usually priced per enrolled employee.
What changes are allowed after a life event?
Employees can change elections mid-year only after events the plan allows. Federal rules set the minimum windows for special enrollment in a group health plan:
| Event | Minimum window to request enrollment |
|---|---|
| Marriage, birth, adoption or placement for adoption | At least 30 days after the event |
| Loss of other health coverage | At least 30 days after coverage ends |
| Loss of Medicaid or CHIP coverage | 60 days after coverage ends |
| Becoming eligible for Medicaid or CHIP premium assistance | 60 days after the eligibility determination |
Under the Section 125 rules, the change an employee makes must also be consistent with the event. A birth allows adding the child, not switching to a richer plan for the employee alone. Write down your plan’s windows and documentation requirements, and apply them the same way every time.
How does the COBRA handoff work?
When an employee or dependent loses coverage because of a qualifying event, such as termination, reduced hours or divorce, COBRA continuation rules start. They apply to most group health plans of employers with 20 or more employees.
The deadlines run from the event:
- Employer to plan administrator: within 30 days of a qualifying event such as termination or reduced hours.
- Administrator to the qualified beneficiary: an election notice within 14 days of getting the employer’s notice. If the employer is also the plan administrator, the notice is due within 44 days.
- Election period: at least 60 days for the beneficiary to elect coverage.
Many employers hire a COBRA administrator. If you do, the benefits administration system has to send it every qualifying event on time, and terminate the employee’s active coverage with the carrier at the same time. A missed handoff is one of the most common sources of COBRA liability.
What does the ACA require you to track?
Applicable large employers must offer coverage to full-time employees and report those offers each year on Forms 1094-C and 1095-C. Benefits administration supplies the data: who was full-time each month, what was offered, what it cost the employee, and who enrolled.
The IRS defines a full-time employee as one who averages at least 30 hours of service a week, or 130 hours in a month. Employers can measure that month by month, or use the look-back measurement method, which sets a stability period of coverage based on hours in a prior measurement period. The look-back method is common for variable-hour and seasonal workers, but only works if hours are tracked consistently. For the filing itself, see ACA reporting.
What goes wrong in benefits administration?
Most benefits administration failures come back to the same few causes:
- Eligibility mismatches. The HR system, payroll and carrier each show a different population. Claims get paid for people who aren’t covered, or denied for people who are.
- Billing errors. Invoices are paid as billed without being reconciled, so overpayments build up month after month.
- Silent file failures. An 834 feed stops working and no one is assigned to read the error reports.
- Late terminations. Coverage keeps running after someone leaves, and COBRA notices go out late or not at all.
- Inconsistent life event decisions. Exceptions made for one employee become a precedent, or a compliance problem.
- No owner. The work is split across HR, payroll, finance and a broker, and nobody owns the reconciliation.
The fix is a written process with an owner for each step, a monthly reconciliation, and an annual review of rules and file feeds before open enrollment. Ethos Benefits helps employers set this up through its benefits administration work.