Benefits
Benefits usually live in three places: an old spreadsheet, an HR inbox, and one person's memory. The catalogue here holds them once, with a record of who is enrolled in what.
Each benefit carries a description, an active state, and a type of either Deduction or Reimbursement. The order is drag-to-reorder, so the list reads the way the company talks about it.
Visibility is per surface. A benefit can be set to show on user cards or stay in the back office.
Enrolment is a matrix of employee against benefit. Each benefit shows its subscriber count, so a line reads 31 of 34 and the gap is visible.
Filters cover user, department and benefit, with a month selector for reading a past period.
The live catalogue runs to eight entries. Medical cover, lunch and dinner subsidies, an AI tool subsidy, a gym allowance, a provident fund, a fuel allowance, and full leave encashment.
That list says something about what a benefits catalogue is for. Half of those are small and local, and none of them would survive being kept in one person's head for a year.
A subscriber count is the cheapest audit there is. A benefit at 31 of 34 people has three names to chase. A benefit at 4 of 34 is one somebody should ask about.
The month selector matters more than it looks. Enrolment changes, people join and leave, and a question about last March needs last March's picture rather than today's.
Typing each entry as a deduction or a reimbursement keeps two different conversations apart. One comes off what somebody gets. The other goes back to them after they spent it.
What it does
- Deduction or reimbursement
- Each benefit is typed, so the catalogue distinguishes what comes off from what goes back.
- Enrolment matrix
- Employee against benefit, with a subscriber count per benefit and a month selector.
- Per-surface visibility
- A benefit can appear on user cards or stay internal.
- Drag to reorder
- The catalogue reads in the order the company actually presents it.
What it needs before it works
- The catalogue needs writing before anyone enrols. A benefit with no description creates questions instead of answering them.
- People need to be in the directory, since enrolment attaches a benefit to a person.
- Departments are worth setting properly. Most of the useful filtering on the enrolment matrix runs through them.
- The benefits permission splits who edits the list from who can read it.
- Decide early which entries show on a user card. A card with eight lines on it stops being read after a week.
Questions people ask
What does the payroll export flag do?
It marks whether a benefit belongs in a payroll export, so whoever runs pay knows which entries count. Payroll itself is planned as a module of its own.
Can I see who is enrolled in a given benefit?
Yes. The enrolment matrix shows employee against benefit with a subscriber count per benefit, filterable by user, department and benefit.
Can I see last month's enrolment?
Yes. A month selector sits on the enrolment matrix, so a question about a past period gets that period's picture rather than today's.