The Carrier Connection Questions HRIS Buyers Skip (and Why They Break in January)

Key takeaways

• A carrier connection is the pipe that carries enrollment changes from your HRIS to your insurance carriers. It is the part of an HRIS deal most buyers never scope.
• Problems rarely show up in the demo. They show up in January, when open enrollment changes hit the carriers and the first invoices arrive.
• Ask the vendor to name each of your carriers and say exactly how it connects: an EDI file, an API, or a person typing changes into a carrier portal.
• Ask who reads the error report when a carrier rejects a record. "The system handles it" is not an answer.
• Make sure the system can produce the report you need to check carrier invoices. If it can't, someone on your team will rebuild it by hand every month.

What happens after an employee clicks "submit"?

Every HRIS demo shows the same thing: a clean enrollment screen, an employee picking a medical plan, a confirmation page. It looks finished.

It isn't. That click only updates your system. The insurance carrier still has to find out, and so does payroll. If either one misses the change, you get the classic January mess: a new hire with no ID card, a terminated employee still covered, and an invoice that doesn't match what payroll took.

I've spent nearly 20 years in benefits administration. The questions below are the ones I wish every HR team asked before signing, because they are the ones that decide whether your first open enrollment on the new system is calm or a fire drill.

What is a carrier connection, in plain English?

A carrier connection is how enrollment changes get from your HRIS to each insurance company. There are three common ways:

• EDI file. The HRIS sends a file to the carrier on a schedule, often weekly. For medical, dental, and vision, this is usually an 834 file, the standard format for benefit enrollment.
• API. The systems talk to each other directly, closer to real time. More carriers support this every year, but not all of them, and not for every plan type.
• Manual. Someone logs into the carrier's portal or emails a form. This is common for smaller carriers and for life, disability, and voluntary plans.

Most companies end up with a mix. The trap is assuming that "we integrate with carriers" means all of yours, for every plan you offer.

Why do carrier connections break in January?

Because open enrollment changes everything at once. New plans, new rates, sometimes a new carrier, plus every employee's elections. The connection has to be updated and tested for all of it, usually during the same weeks HR is answering a flood of employee questions.

Then the first invoices of the year arrive. That is when the gaps show up: people the carrier never received, people who should have been removed, and coverage levels that don't match.

The fix is not a better enrollment screen. It is asking the right questions before you sign.

10 questions to ask an HRIS vendor about carrier connections

1. Which of our carriers do you connect to today, and how?

Bring your carrier list, including dental, vision, life, disability, EAP, and voluntary plans. Ask the vendor to mark each one EDI, API, or manual.

A good answer is specific: carrier by carrier, plan by plan. A weak answer is "we connect with all the major carriers."

2. Who builds each connection, and what does it cost?

Some vendors build and maintain connections themselves. Some use a third-party partner. Some leave it to you or your broker. Ask about setup fees per carrier, ongoing fees, and what it costs to change a connection later.

3. How long does setup take, and how does it line up with our open enrollment?

Carriers often need several rounds of test files before they accept a new connection, and that can take weeks or longer. If testing runs into open enrollment, you could be running enrollment in a system that isn't sending clean files yet.

Ask for a timeline, then work backward from your open enrollment dates. If the dates don't fit, plan to keep the old process running until they do.

4. How often do files go out, and are they full files or changes only?

A full file sends everyone every time. A change file sends only what changed since the last one. Both work, but they fail differently. With change files, one missed file can mean a change never reaches the carrier at all.

Ask how often files run and what happens if one fails to send.

5. Who reads the error report when a carrier rejects a record?

Carriers send back errors: a missing date of birth, a dependent over the age limit, a plan code that doesn't exist. Someone has to read those reports and fix the records.

Ask for a name or a role, not a team. Ask how fast errors get worked, and whether you can see the reports yourself. This one question tells you more about the vendor's service than the whole demo.

6. How are terminations sent, and how far back can a change go?

When someone leaves, the carrier needs to end their coverage on the right date. If the termination is late, you may keep paying premiums for a person who isn't there, and claims may get paid that shouldn't.

Many carriers limit how far back they will accept a change. Ask how the system handles a termination entered late, and who catches it if a carrier refuses it.

7. What happens with COBRA?

When an employee loses coverage, COBRA starts. The employer generally has 30 days after a qualifying event, like a termination, to notify the plan administrator, and the COBRA administrator has to get notices out after that.

Ask whether the HRIS sends terminations to your COBRA administrator automatically, and how often. If the answer is "you email them," put that on someone's calendar now.

8. What happens at renewal when plans, rates, or carriers change?

Every year something changes. A plan gets renamed, rates go up, you add a carrier. Each change can mean the connection has to be remapped and tested again.

Ask who does that work, how much lead time they need, and whether it costs extra.

9. Can I pull an enrollment report for any date, by person, plan, and coverage level?

This is the report you need to check carrier invoices. It should show who was enrolled in which plan, at which coverage level (employee only, employee plus spouse, family), on a given date.

If the system can't produce it easily, someone will rebuild it in a spreadsheet every month. Ask to see the report in the demo, not a description of it.

10. Do payroll deductions come from the same elections the carrier sees?

Your HRIS, your payroll, and your carrier should all agree on who has what coverage. When they don't, ask which system wins and how you'll find out.

If deductions and carrier files come from different places, they will drift apart. You'll find out when an employee asks why they're paying for a plan they dropped.

What does invoice reconciliation have to do with the HRIS you pick?

Every month, three things should match: who is enrolled in your HRIS, what payroll deducted, and what the carrier billed. Checking that is called invoice reconciliation, and most HRIS platforms do not do it for you.

What the HRIS can do is make it easy or hard. A clean enrollment report and a single source for elections make reconciliation a short monthly task. A messy one turns it into a project.

Here's why it matters. Say a carrier keeps one terminated employee on family medical coverage at $2,000 a month, and nobody catches it for six months. That's $12,000 gone, and many carriers will only credit back part of it. Multiply that by a few people and a few plan types, and you can see why the questions above are worth an extra hour in the buying process.

Red flags to listen for in the demo

• "We integrate with all the major carriers," with no carrier-by-carrier list.
• "The carrier handles that," when you ask about errors or terminations.
• No named person or role responsible for reading carrier error reports.
• A setup timeline that ends after your open enrollment starts.
• An enrollment report that only shows today's data, not any date you choose.

The bottom line

The enrollment screen is the easy part. What breaks in January is everything after the click: the files, the errors, the terminations, and the invoices. Ask these 10 questions, get the answers in writing, and assign an owner for the carrier side before you sign. Your first open enrollment on the new system will thank you.

Frequently asked questions

What is an 834 file?

An 834 is the standard file format used to send benefit enrollment changes, like new enrollments, changes, and terminations, from an employer's system to an insurance carrier.

Do small companies need EDI carrier connections?

Not always. With a small headcount and a few carriers, manual updates in carrier portals can work if someone owns them and does them on a set schedule. EDI starts to pay off as headcount, turnover, and the number of carriers grow.

When should carrier connections be live before open enrollment?

Early enough to finish testing before enrollment opens. Ask each carrier and your vendor how long testing usually takes, then work backward from your open enrollment dates.

Who is responsible when a carrier file fails?

It depends on your contract, which is why you should ask before you sign. Get it in writing: who monitors files, who reads error reports, and how fast problems get fixed.

Erica Kirby is the founder of Nobody Told Me That (ericakirby.com), where she writes plain-English guides for people new to benefits administration. She has nearly 20 years of experience running US and global employee benefits programs. Her free Post-OE Audit walks HR teams through matching enrollment, payroll deductions, and carrier invoices after open enrollment.