The master sheet, the leave tracker, the payroll export and the folder of contracts all describe the same people differently. HarmoniHRM replaces the pile with one record that has permissions, history and a memory.
This world has a real workforce and a shadow one. The real one works, takes leave and gets paid. The shadow one lives in a master spreadsheet owned by whoever built it, a leave tracker with formulas nobody dares touch, a payroll export edited by hand every month, and a shared drive of contracts in six naming conventions. Every question about the real workforce is answered by the shadow one, and they disagree more every week.
Not generic HR pains: the specific ways this environment grinds people teams down, one honest description at a time.
The sheet gets emailed, copied and edited in parallel. Two versions disagree about a salary, and the one that reaches payroll is whichever was attached last.
A dragged formula skips a row and someone’s leave balance is wrong for months. Spreadsheets do not raise errors about being wrong, they just keep being wrong politely.
A spreadsheet has no row-level permissions. Either the salary column is visible to whoever opens the file, or HR becomes the bottleneck for every single lookup.
Cells get overwritten. Who changed the salary, when the role changed, what the balance was in March: unanswerable, which is uncomfortable in a dispute and fatal in an audit.
Attendance, pay and compliance are where this world gets judged. Here is how each one runs on a connected record.
Balances are calculated automatically from policy, tenure and entitlement, with public holidays per country excluded and carry over handled at year end with every movement on the ledger. Approvers see who else is off before saying yes, instead of finding out from the tracker afterwards.
Payroll reads the same record HR maintains, so the monthly export-edit-import ritual disappears. Runs are validated before they process, anomalies are flagged, and two approvers sign off. UK and GCC payroll run in full; elsewhere, statutory rules are configured per country.
The dates that lived in a column nobody sorted, visas, right to work, certifications, become tracked items with 90, 60 and 30 day warnings and a daily check across every record.
HarmoniHRM is modular. These are the pieces that earn their keep in this world, each reading and writing the same connected record.
The record that replaces the master sheet: one profile per person, documents in a vault, history kept.
Ledgered balances and clash-aware approvals instead of a formula-driven tracker.
The pivot tables, rebuilt: filtered, exportable, permission scoped and audit logged.
The org chart drawn from the data itself, updating the moment something changes.
Runs that read the record directly, killing the monthly export-and-edit ritual.
Leave, holidays and pay days visible on one permission-aware calendar instead of a tab.
Follow one realistic cycle through HarmoniHRM, step by step, from the first event of the day to the numbers that close it.
The master spreadsheet becomes employee records in one import, and the org chart builds itself from the data on day one.
The self service portal lets everyone update their own details, bank information and emergency contacts, and a daily data quality check ranks whatever is still wrong.
Policies are set once, balances compute themselves, and every request, approval and adjustment is a ledger entry rather than a cell edit.
A request shows who else on the team is already away, so approvals stop being a guess about a spreadsheet nobody checked.
The month-end questions become saved reports with filters and CSV export, each carrying a line naming exactly how its numbers were derived.
The file that ran the company gets a dignified retirement: kept for history, opened never.
The core move is one import: your people data becomes records, and the org chart builds from it automatically with no manual chart edits. From there, self service and daily data quality checks clean up what the spreadsheet had quietly got wrong.
Modular pricing, no long contracts. Start with the modules this world actually needs and add the rest when you are ready.