Benefits, Time Off, Transfers and Offboarding Are Now in Muin HR
Four parts of the employment lifecycle shipped together: priced benefit plans with enrollment windows, time off and timesheets, transfers that compute the access change first, and offboarding you can actually prove.
Most HR tools are good at hiring somebody and vague about everything after. Muin HR has shipped the parts in between: what people are covered by, when they are away, where they move to, and what happens to their access when they leave.
Here is what is in the product today, and the thinking behind each one.
Benefits came out of the config bag
Benefits used to be settings. Now they are real records, and that difference is the whole feature.
Go to HR → Payroll & Benefits → Benefits. You build a catalog of plans, and each plan carries priced coverage levels - employee only, employee and spouse, employee and children, family - with a monthly employee and employer amount on each. A plan with nothing priced says so, and nobody can elect it.
Then you open an enrollment window: annual open enrollment, new hire, or qualifying event. The window’s own dates control when people may elect. The coverage start date is a separate field, because staff elect in November for coverage that starts in January, and closing the window does not start the coverage.
At most one annual open-enrollment window may cover any given day. A second overlapping one is refused, and the refusal says why. A late joiner gets a qualifying-event window of their own, which doubles as the record of why they were let in late.
The part that matters most is invisible
Every enrollment stores its own cost snapshot, taken at the moment of election. Deductions and benefit reports are computed from that snapshot, never from what the plan costs today.
So you can correct a plan’s price mid-year without re-pricing anybody’s history. In the old configuration shape, a price edit silently changed every historical election, including ones already deducted from a paycheck. That is the kind of defect nobody reports because nothing fails.
A waiver is also a first-class election now, with a reason, rather than a blank. A waived coverage and a coverage nobody got round to electing look identical otherwise, and affordability reporting has to tell them apart.
Employees elect for themselves at HR → My Portal → My Benefits, where they see only the plans they personally qualify for and the days remaining in their window.
Time off and hours, in the words people use
HR → Time & Leave → Leave Management holds four tabs: Dashboard, Requests, Policies and Calendar.
A policy is a container with an accrual frequency - per pay period, monthly, annually, or none. Inside it, each leave type carries the rules you actually argue about: accrual rate, max balance, carryover limit, whether it is paid, whether approval is required, and how many days of notice a request needs.
Balances are held per employee, per leave type, per year, as four separate numbers: accrued, used, pending and carried over. Pending is kept apart deliberately, so hours reserved against an undecided request cannot be spent twice.
Employees request from HR → My Portal → My Time Off and can withdraw anything not yet decided. Managers decide from HR → My Portal → My Team, which is the same queue HR sees - no second inbox to keep in sync. Where your rules call for two approvers, the first approval is recorded separately from the final one, so one person cannot satisfy both.
HR → Time & Leave → Time Tracking is the hours half: clock in, clock out, entries, and timesheets per pay period. An entry can carry a review exception that holds it for a human - tardy, outside the schedule, an unusually long punch, a missing punch photo, a geofence violation, a self-amendment, an auto-close, a no-badge fallback. Which of those block automatic approval is a setting, so you decide what a manager must look at by hand.
An unclosed punch gets auto-closed and the auto-close is recorded as an exception rather than letting the hours land quietly in payroll. A period you have finished with goes to Locked, and then it stays closed.
A transfer is an access review with a job title attached
When somebody is promoted or changes department, the paperwork is the easy part. The question that matters is what happens to their access.
HR → People → Transfers answers it before you commit. Pick the person, choose the new department, manager, title or location, then press See the access changes. The preview lists exactly what would be granted and what revoked, and writes nothing - walking away from it changes no record.
Applying does three things in one transaction: moves access, writes the new position, stamps the applied time. If any part is refused, none of it lands.
Two details worth knowing:
- The access change is a delta, not a reset. Access the new position also needs is kept rather than revoked and re-granted, so nobody is briefly locked out of something they are entitled to.
- An empty access delta is a warning, not a pass. It means a position moved and no access consequence was computed, which is usually a gap.
Changing the position on the employee record itself now creates a scheduled transfer rather than editing in place. A position change with no access review is exactly the gap this closes.
Offboarding you can prove
The old shape was a task per connected system, which an admin could tick whether or not the account was gone. That reads as “access revoked” either way. It is a false green on a security control, and it is the thing this replaces.
HR → People → Offboarding lists everyone who has left or been deactivated - including people switched off without a termination, which is precisely the case where nobody explicitly revoked anything. Start an offboarding and Muin deactivates the login, revokes the tokens, and asks every connected system to remove the account.
Then it shows you what each system actually answered, one row each:
- Revoked - the system confirmed it.
- Failed - with the provider’s own reason. Retry it; the retry reports what happened rather than just succeeding.
- Not supported - that system has no provisioning API at all. Muin cannot revoke it and says so rather than pretending. Somebody has to do it by hand.
There is no row you can clear yourself. The header reads Access fully revoked or Access not fully revoked, and offboarding is not finished while a single revoke is outstanding. Outstanding devices are on the same page, because an offboarding that does not name the laptop has not finished.
Identity deactivation and employment termination also happen together now. Before, deprovisioning through an identity provider suspended the login and left the employment record active, so the person kept counting in headcount and in team hours.
And the smaller things
- HR → Overview → Overview is the day’s picture: headcount, documents, compliance score, certifications expiring, what needs attention, what is due soon.
- HR → People → Headcount Impact groups current employees by status, department and employment type, and every bar drills to the employees behind it and a CSV of exactly that list.
- HR → People → I-9 Compliance makes the I-9 clock visible: pending, overdue, violations, and open E-Verify cases counted separately so a case nobody followed up cannot hide behind a completion.
- HR → Documents → Handbook versions the employee handbook. Acknowledgments are per version, so publishing a new one produces a fresh pending list rather than carrying old signatures forward.
- HR → People → Document Impact groups every HR document by lifecycle state and expiry window, so you find out what is going stale before an auditor does.
- HR → People → Profile Approvals is where a bank-account or address change is reviewed before it takes effect, restricted to owners and admins because approving a bank change decides where somebody’s pay is sent.
What Muin still does not do
Muin does not process payroll, calculate taxes, or remit to agencies. Your provider does that. Muin owns everything around it: collecting the employee data, approving the hours, bringing the register in, posting the GL entries, reconciling the bank debit, and giving every employee their own pay stub.
That boundary is deliberate and we would rather say it plainly than let a feature list imply otherwise.