Leave management
Policy is set once
Entitlements, working days and each country’s public holidays become configuration, and every balance downstream computes itself from policy and tenure.
The situation
Every workforce, at its most disputed edge.
Away this week
Kai TanakaAnnual leaveWed to Fri
Nadia RahmanSick leaveToday
Lina FaroukWork from homeThu
Leave and attendance is where every workforce meets its administration: the parent planning around school holidays, the team lead protecting a deadline, the shift worker whose overtime is their mortgage margin, and the finance director who just wants the numbers to reconcile. It is the highest-volume HR process in any company, and the one where a wrong number is noticed by the person it belongs to, immediately.
Where it breaks
The problems that live in this world.
Not generic HR pains: the specific ways this environment grinds people teams down, one honest description at a time.
The disputed balance.
The tracker says twelve days, the employee remembers fifteen, and the manager approved something in a corridor. Year end becomes an archaeology of good intentions.
Approving blind.
A manager says yes without seeing that two others on the team are already off that week. The gap is discovered by the customer.
Holidays counted wrong per country.
A day count that ignores public holidays, or applies the wrong country’s, quietly shortchanges someone in every cycle, and the error compounds all year.
Attendance never reaches pay.
Hours and overtime live on paper or in a punch-clock export, then get retyped into payroll. Every retype is a dispute scheduled for payday.
Day to day
Three operational realities, handled.
Attendance, pay and compliance are where this world gets judged. Here is how each one runs on a connected record.
01
Attendance on the same record.
Clock in and out land on each person’s record, the live board shows who is in, late or absent across every team and location, geofenced check-in covers field teams, and lateness and flexi balances are read against each schedule with the working shown.
02
Overtime that pays itself correctly.
Approved timesheet overtime feeds the pay run automatically, with runs validated before processing and signed off under dual control. UK and GCC payroll run in full; statutory rules are configured per country elsewhere.
03
Absence patterns, read honestly.
Absence is read with the Bradford factor so frequent short absences surface early, approved leave updates presence everywhere including the org chart, and carry over is handled automatically at year end with every movement on the ledger.
The modules that fit
Take what fits, leave the rest.
HarmoniHRM is modular. These are the pieces that earn their keep in this world, each reading and writing the same connected record.
Leave management→
Ledgered balances from policy, tenure and entitlement, with clash-aware approvals.
Time & attendance→
The live board, clock in and out, geofenced check-in and overtime flowing to pay.
Company Calendar→
Leave and public holidays per country on one calendar; drag a range on the month to start a request.
Payroll→
The pay run that reads approved hours and overtime with nothing retyped.
Organo→
Presence and leave status live on every card, so cover questions answer themselves.
Reports→
Leave, time and overtime reports with filters, exports and the derivation printed.
A working day, connected
How the day actually runs.
Follow one realistic cycle through HarmoniHRM, step by step, from the first event of the day to the numbers that close it.
01
Policy is set once
Entitlements, working days and each country’s public holidays become configuration, and every balance downstream computes itself from policy and tenure.
02
A request starts anywhere
From the portal, or by dragging a date range on the month view of the calendar, with the day count already excluding the right holidays.
03
The approver sees the team
Before saying yes, the manager sees who else is already off for those dates, so coverage is part of the decision.
04
Approval updates the world
The balance moves on the ledger, presence updates everywhere it is shown, and cover for an approver on leave is arranged automatically.
05
Hours meet payday
Clock-ins, lateness and approved overtime are read against each schedule, and the overtime lands in the validated pay run automatically.
06
Year end closes itself
Carry over is applied automatically under your policy cap, with a use-by date and every movement recorded on the ledger.
Who lives this
The people inside this playbook.
Time & attendance
A request starts anywhere
From the portal, or by dragging a date range on the month view of the calendar, with the day count already excluding the right holidays.
Company Calendar
The approver sees the team
Before saying yes, the manager sees who else is already off for those dates, so coverage is part of the decision.
Payroll
Approval updates the world
The balance moves on the ledger, presence updates everywhere it is shown, and cover for an approver on leave is arranged automatically.
Keep reading
Related playbooks in this family.
Asked before buying
The questions that come up every time.
How are balances actually calculated?
From policy, tenure and entitlement, automatically, with public holidays for each person’s country excluded from day counts and carry over applied at year end under your policy cap and its use-by date. Every movement lives on a ledger, so a balance is a derivation, not an assertion.
What does the approver see before deciding?
Who else on the team already has approved leave for those dates, so a deadline week is never approved empty by accident. Once approved, presence updates everywhere it is shown, including the org chart.
What is the Bradford factor and why does it matter?
It is a standard measure that weights frequent short absences more heavily than rare long ones. HarmoniHRM reads absence patterns with it so the disruptive pattern surfaces early, with the working shown, before it becomes a crisis.
Does overtime genuinely reach payroll without re-entry?
Yes. Approved timesheet overtime feeds the pay run automatically, the run validates itself before processing, and dual control signs off, so the number worked and the number paid are the same number.
Run it on your own organisation.
Modular pricing, no long contracts. Start with the modules this world actually needs and add the rest when you are ready.