Somewhere in your company, an employee who started three weeks ago still can’t fill a prescription — the system says they don’t exist yet.
On paper, your HRIS and your insurer are connected. In practice, the handoff is where things quietly break. Orchard is the advisor who fixes it.
Every Canadian HR lead has seen some version of this:
A new hire enrolls on day one and waits 2–6 weeks for their benefits card — meaning they’re paying out of pocket or going without.
An employee submits a claim during the gap, and it’s denied because the carrier doesn’t have them on file yet.
An employee goes on leave with stale salary data, and their disability coverage gets miscalculated at exactly the moment they need it most.
A termination doesn’t propagate to the carrier for months, and the company keeps paying premiums on someone who left in February.
A dependent update gets entered in the HRIS, but never makes it to the insurer — and the family finds out at the pharmacy counter.
And they happen to companies that did everything right — picked a good platform, hired a good HR lead, signed with a reputable carrier.
The limbo period is the part of the system no one warns you about. It’s also the part Orchard exists to fix.
Most HRIS platforms will tell you they connect to the major Canadian insurers, and most of them do. The gap isn’t in the claim. It’s in what “connected” means when there’s no standard defining it.
In the United States, federal law requires health plans to accept a common enrolment file format — the ANSI 834 — and carriers can’t charge employers to use it. Every platform and every carrier builds to the same specification.
Canada has no equivalent. The CLHIA publishes guidance on how group insurance contracts should be administered, but there is no mandated enrolment file standard. Each carrier defines its own format, its own transmission schedule, and its own rules for what happens when a record doesn’t validate.
That’s the whole story. It’s not that anyone is doing their job badly. It’s that every HRIS-to-carrier connection in this country is effectively custom, and the details determine whether your people get their cards in five days or five weeks.
The HRIS does its job. The insurer does its job. The space between them isn't owned by anyone — because nothing requires it to be.
HRIS platforms have different commercial models, and the differences matter more than the feature lists. None of this is hidden — it’s just rarely asked about during a demo. Five questions worth putting to any vendor:
Is the benefits connection real-time or a scheduled file? Ask for the actual frequency and the carrier’s processing window on top of it. Add them together. That sum is your limbo period.
Which Canadian carriers do you have a live, tested connection with — not a partnership, a connection? Logos on a slide aren’t feeds. Ask which specific carriers they’ve moved data to in the last twelve months, and for a reference client on your carrier.
Is payroll native or connected? See below — this is the single biggest driver of how much manual work lands on your team.
What’s your benefits distribution model? Some platforms operate or partner with a brokerage; others are software only. Both are legitimate. But you should know which one you’re buying, because it shapes who advises you at renewal and how they’re compensated. Ask directly, and ask what happens to your existing advisor’s access.
Who owns the data, and what else is it used for? Get the answer in the contract rather than the sales call — specifically around aggregation, benchmarking, and anonymised reporting.
We're platform-agnostic and we don't take referral fees from any HRIS. We'll help you work through these questions on whatever platform you're considering, including ones we don't currently support.
This comes up in almost every HRIS conversation we have, and it’s the question most likely to be answered vaguely on a demo call.
Native payroll means the platform processes payroll itself, inside the same database that holds your employee records. Deductions, benefit premiums, and salary changes move without leaving the system.
Connected payroll means the platform passes data to a separate payroll provider through an integration. It can work well. But every handoff is a place where timing slips and records disagree.
Neither model is automatically right. Native is simpler for benefits administration. Connected can be the better call if you already have a payroll provider that handles something specific to your business well, or if you're operating across countries.
What matters is knowing which one you have, because it determines how much manual reconciliation your team absorbs every month. We map this before you sign, not after.
Most advisors stop at “we’ll help you pick a platform.” We start where they stop — at the data layer between your HRIS and your carrier.
We document every field, every trigger, every place a human has to retype something, and we engineer it out.
Most advisors are reactive, fixing the integration after a claim is denied or an employee complains. We pressure-test your data flow against the failure modes we’ve seen across Canadian plans, and we flag the exposures before they surface: stale beneficiary data, coverage mismatches, gaps during leaves, and contractor-versus-employee misclassifications in the feed.
Beyond the integration itself, Orchard clients get access to our own forward-looking risk profiling — a proprietary tool, built in-house, that models where your plan is heading three to five years out based on your demographics and claims trends, ranked by claim impact and likelihood. Sample reports available on request.
HRIS implementations are usually one-and-done. The advisor leaves, the integration drifts, and within 18 months you’re back where you started. Orchard treats the HRIS-to-carrier connection as a living system — monitored, audited quarterly, and updated as your headcount, plan design, and carrier processes change.
We’re platform-agnostic on purpose. Orchard doesn’t operate a brokerage inside any HRIS, and we don’t take referral fees or partnership cuts from platform vendors — when we negotiate something on your behalf, the savings go to you. When the platform underneath you changes, and it will, Orchard stays the constant.
When Collage reintroduced its advisor portal and access stopped being automatic, we didn’t wait for clients to notice. We built a reconnection playbook and walked teams through it.
Collage recently reintroduced its advisor portal after removing it a couple of years ago. Advisor access is no longer automatically maintained, which means Orchard may need to be reconnected at the account level to keep supporting your team inside the platform.
Download this step-by-step guide to get reconnected. Reconnection takes about two minutes.
Four steps. No drawn-out discovery phase, no deliverables that sit in a drawer.
We trace every data point that should be moving between your HRIS and your carrier, and we show you where it’s actually going.
You get a written assessment of where your plan is exposed today and where it’s heading over the next three to five years, ranked by claim impact and likelihood.
We work directly with your HRIS provider and carrier — not as a translator, but as the accountable party — to engineer a feed that holds.
Quarterly reviews, anomaly alerts, and a single point of contact when something changes on either side.
We work across the major Canadian HRIS platforms — including ADP, Ceridian (Dayforce), UKG, Workday, BambooHR, Rippling, Humi, Rise, Folks, Collage, Payworks, and Nethris — and with every major Canadian carrier.
The platform matters less than the connection. If yours isn’t on this list, we’ve almost certainly mapped one like it.
A 20-minute conversation tells us whether your HRIS and your carrier are actually talking, or just nodding at each other across the room.
