Eligibility answers itself.
Rules read role, tenure and working pattern from the same record as pay. Who qualifies is the current answer, never last quarter’s spreadsheet.
Part of Employee Management
Benefits, enrolled and tracked in one place.
Plans, providers, eligibility rules and enrolments administered on the employee record itself. Because benefits read role, tenure and working pattern from the same record as everything else, eligibility answers itself.
- Eligibility reads role, tenure and working pattern from the same record as pay.
- A status change updates cover. Part time caps are pro rata.
- What someone is enrolled in, and since when, sits on the record. Payroll reads it.
- Renewals show before the invoice. A paid claim raises one payroll input.
Elena VossSenior Software EngineerEnrolled since Thursday, 1 May 2025Eligible fromDay 90Counted from the day she joined
Cover on her record
- Health insurance
- Dental
- Vision
- Retirement plan
Claim · dental, $180
- Submitted with receipt
- Within plan limit
- Approved by People
- On the next payslip
The problem
Benefits live in a folder, and eligibility drifts quietly.
Eligibility by memory.
Who qualifies after probation? Who lost cover when they went part time? The rules live in a policy document, and the answers live in guesswork.
Enrolment archaeology.
What is this person actually enrolled in, and since when? The answer is spread across emails, provider portals and an old spreadsheet.
Renewals that ambush.
The policy renews in three weeks and nobody has reviewed it. Every year, the same scramble.
How Benefits fixes it
What Benefits does on the connected record.
Enrolment against real rules: eligibility is tracked against role, tenure and the rules you set, on the same record as pay and status
Status changes update cover: a move to part time, a promotion or a leaver updates benefits eligibility automatically
One enrolment record: what each person is enrolled in, and since when, visible to HR and payroll without a separate system
Provider directory: the providers behind each plan, kept alongside the plans themselves
Renewal calendar: renewal dates visible ahead of time, so reviews happen before the deadline, not after it
Fair for part time staff: employer contribution caps are shown pro rata against each person’s working pattern
A real workflow
From plan setup to renewal.
- Plans and providers go in once.Each plan is recorded with the provider behind it, so the answer to who covers what is a lookup, not an email chain.
- Eligibility comes from the record.Rules on role and tenure are evaluated against live employment data, so who qualifies is always the current answer, never last quarter’s.
- Enrolment is written down properly.What each person is enrolled in, and since when, sits on their record where HR and payroll both read it, with nothing held in a private spreadsheet.
- A status change updates cover.A move to part time, a promotion or a leaver flows through to eligibility automatically, and contribution caps are shown pro rata against the new working pattern.
- Renewals arrive with warning.The renewal calendar shows every policy date ahead of time, so the review happens before the deadline rather than after the invoice.
One record. Nothing entered twice.
Benefits does not live on an island.
Benefits read role, tenure and status straight from the employee record, so eligibility is always current. Payroll sees the same enrolments, and Reports can answer who is covered without an export.
Why teams switch
Cover that follows the record, not a folder.
A status change updates cover.
Part time, promotion or a leaver flows through. Contribution caps are shown pro rata against the new pattern. Nobody retypes the plan.
Enrolment is written once.
What someone is enrolled in, and since when, sits on their record. Payroll reads the same row. A paid claim raises one input, not a line that repeats every run.
Renewals arrive with warning.
The calendar shows the policy date ahead of time. The review happens before the invoice, not after it.
Already connected
Payroll already sees the same enrolment.
What someone is enrolled in, and since when, sits on their record. A paid claim can raise one payroll input. It does not reimburse itself every run forever.
- Plans and providers go in once, so who covers what is a lookup, not an email chain.
- A receipt can be required above a threshold you set per category. Blank claims still need a receipt.
- Pakistan IPD is the health_ipd benefit. OPD lands on the slip as a reimbursement. Those are not the same thing.
- View Policy opens the Studio course when one is attached, or the PDF when only a document is linked.
Who it is for
The people who actually enrol and renew.
People
The person who owns the plan.
Amara records the provider once. Eligibility is evaluated against live employment data, not last year’s export.
Payroll
The person who pays the claim.
A paid claim raises one benefit_reimbursement input. It does not haunt every later run.
The employee
The person reading their cover.
Kai opens My Benefits and sees what he is enrolled in, and since when. A part time cap is shown pro rata.
Finance
The person watching renewals.
The calendar names the date. The scramble is no longer the process.
Keep reading
How cover should behave.
Questions people actually ask.
Where does eligibility come from?
Role, tenure and working pattern on the employee record. Benefits do not keep a second copy of those facts.
Does a paid claim keep paying every month?
No. A paid claim raises one benefit_reimbursement payroll input. It does not reimburse again on every later run.
Is a receipt always required?
A blank claim always needs a receipt. Above a threshold you set per category, the field is required. Below it, the form can submit without one.
Is HARMONI included with Benefits?
No. Benefits is complete without it. HARMONI AI is an optional add-on, off until a platform admin grants it.
Included with Employee ManagementBenefits ships inside Employee Management at $5 per employee / mo · payroll included, with connected Organo included at no extra charge.Compare pricing →
More of Employee Management
The rest of the record.
Ready for benefits
that lives on one record?
Benefits arrives as part of Employee Management, connected to the same record every other module reads. Nothing to sync, nothing entered twice.
← Back to Employee Management