Core HR · benefits enrolment
Most benefits tools stop at a list of who chose what. This one ends at the deduction.
If an election never becomes a priced payroll deduction, it’s still just a form. Everything on this page is about closing that gap.
Each carrying an employee and an employer amount
Each with what it permits and by when
So the new figure reaches the payslip
Trusted by the Caribbean’s best-known employers
Airlines, telecoms, utilities, hotels, credit unions and the National Insurance Board itself.

The plan, and what it carries
You set the plan up once, and everything downstream is worked out from it.
On the plan itself
- A coverage type and a carrier
- A pre-tax flag
- A waiting period in days
- A plan year and a group policy number
- Claims contact details, phone, email and address
- Uploaded plan documents
- A draft state, and an approval route of manager, HR or none
The claims contact sits on the plan, because that’s where an employee looks the day they need it.
Five coverage levels, two amounts each
Employee; employee and spouse; employee and children; children; family. Each level carries an employee amount and an employer amount, set as a fixed amount or as a percentage of pay.
The employer contribution always travels with the employee cost. Employees don’t trust a benefits screen that shows only the deduction. It reads as a charge, and it makes them ask what the employer is actually putting in.
Two of those plan fields do more work than they look. The draft state lets you build a plan over a week without anyone enrolling into a half-finished tier, which is how a wrong premium usually gets out. And the approval route (manager, HR or none) lets a plan that needs a signature sit in the same account as one that doesn’t.
Pricing always carries its basis
Per pay period, monthly and annual equivalents, so nobody ends up comparing a fortnightly figure with a monthly one. Share of pay is measured against take-home, because that’s the number an employee knows from their payslip. A tier priced as a percentage is quoted as a rate. It never gets folded into a currency total.
Eligibility is a rule
No spreadsheet of who’s eligible. Nobody has to remember to add the new starters.
A waiting period from hire plus an employment-level allow-list. While you’re still ticking boxes, the plan wizard tells you how many employees the rules would admit. That changes the work. Eligibility rules are usually written blind, and the mistake shows up at enrolment, when the population is wrong and the window is already open.
The waiting period is left out of that number on purpose. It decides when someone becomes eligible, never whether they are. Mix the two together and you’d understate the population every time.
Three ways a window opens
An account that sets up none of these is unrestricted, so self-service keeps working until an admin opts in to gating. Nothing breaks the day you turn benefits on.
The seven life events
And divorce, each with its own permitted changes
And the death of a dependent
Two separate events, because they permit different changes
A move that changes what someone is eligible for
Reporting an event doesn’t open a window
It takes confirmation. That’s the control HR managers ask us about. An employee can raise an event. Somebody else decides whether it opens anything.
Elections become payroll deductions
This is the part that makes the rest worth having. And it’s where most benefits tools hand you a report instead.
One backing deduction per plan, carrying the carrier and the pre-tax setting. Then one deduction per enrolled employee, priced from their own coverage tier.
Re-price a plan and everyone on it is re-priced, so the new figure reaches the payslip, and not only the enrolment screen. We built it this way to stop one failure: a premium that changed in the benefits module and never reached the run.
A pending election leaves payroll exactly as it is. Opening your own enrolment to look at an option never cancels live cover. Sounds obvious. Until you’ve used a system where it isn’t.
Changes land on pay-period boundaries, and here’s why
The engine doesn’t prorate. Switching plans mid-period would charge two full premiums, so a change takes effect at the boundary. Cover on termination runs to the end of the period the last day worked falls in.
If mid-period proration has burned you somewhere else, you’ll see somebody thought about this.
Dependants, beneficiaries and the check that earns its keep
Dependants and beneficiaries, primary and contingent, with allocations that must total 100% within each designation, so a primary set that adds up to 90% can’t be saved, only to be found at the worst possible moment.
And the coverage reconciliation check: cover level and the people attached to it must agree. Nobody elects Family, attaches nobody, pays the family premium for a year and finds out at the claim. A small check. It stops the most expensive mistake an employee can make on their own behalf.
Put those three rules together. Pending elections leave cover alone. Re-pricing reaches everyone. Changes land on boundaries. They all come from one decision: the enrolment screen and the payslip are never allowed to disagree. Most benefits problems an HR team escalates are some version of that disagreement, and they turn up months later in a reconciliation.
History is kept before and after on plans, elections and qualifying events. Somebody asks what an employee was enrolled in last March, and you can answer.
What it doesn’t do
The integration is the deduction
There’s no carrier feed, no claims workflow, no enrolment file out to an insurer and no continuation cover.
For the problem most employers actually have, the deduction is the part that matters. Most Caribbean employers reconcile with their carrier by email, and always have. A missing carrier feed doesn’t cost them much. What costs them is a premium that changed in one system and never reached the payslip in another, found three months later across a hundred employees.
That’s the gap this closes. Everything else is a reporting problem. This one is a money problem.
Articles
Further reading
Enrolment that ends at the deduction
A list of who chose what. That’s only half the job.
Read the article ArticleA life event, and what it should be allowed to change
The window, the evidence and the effect on the next pay run.
Read the article ArticleReconciling a benefits invoice against payroll
Where the two disagree, and which one is usually right.
Read the articleQuestions HR managers ask about benefits
Does the employer contribution show on an election?
What happens when a premium changes?
Can an employee open their own enrolment window?
Why do cover changes wait for the pay period?
Do you send an enrolment file to our carrier?
What stops someone electing family cover with no dependants?
See it on your own data
Bring your own plan structure: your coverage types, your tiers, your eligibility rules. We’ll set one up and follow it all the way to a payslip.
- A plan configured with its five tiers and both amounts
- An eligibility rule, with the admitted population counted as you build it
- A life event confirmed and the window it opens
- The election arriving as a priced payroll deduction
- SOC 2 Type II attested
- AES-256 at rest
- 99.9% uptime
- Built in The Bahamas
Where to go next
Benefits sits inside Core HR and lands in Payroll. These are the pages either side of it.
Benefits enrolment is part of Core HR, which is included in every plan. Security: AES-256 at rest via AWS KMS, TLS 1.2 and above in transit, SOC 2 Type II attested against the Security criteria with the report available under NDA, and AWS US multi-AZ as standard with on-premises or Caribbean regional cloud on request, subject to scoping. Sign-in is by Microsoft Entra ID single sign-on. See also Payroll, Workforce and Talent · the six territories · clients and contact.
