HRIS and payroll system setup

What this actually solves

A company goes from eight people to twenty-five and the HR function is still an office manager, a spreadsheet and a messaging thread. Nobody can say with confidence how much leave anyone has left, because approvals happened verbally and were written down some of the time. A new starter arrives and waits three days for a laptop, an email address and access, because there is no list of what a new starter needs and no one person responsible for it. Contract end dates and document renewals are remembered rather than tracked. It works, until it does not.

Then there is pay, which is a different category of problem. Everything else in a business can be approximately right for a while. Pay cannot. One person's number being wrong is not an administrative error to the person it happens to — it is personal, it is discussed across the whole office by lunchtime, and it costs more trust than the amount involved. Meanwhile the calculation itself is tied to legislation that changes, and getting it wrong carries penalties that arrive later and land on the employer. That combination is why this project is built the way it is described below — slowly, with the old method still running beside the new one until the numbers agree.

How the work runs

1. Policy before configuration. Leave entitlement and carry-over, notice periods, probation, overtime treatment, public holidays, working patterns. Much of this exists only as custom and has never been written down, and the differences between what people believe are usually discovered here. Anything statutory is confirmed with a specialist in your jurisdiction and the source recorded. One to two weeks.
2. The people processes, mapped as checklists. Onboarding and offboarding step by step, with the owner of each step named — equipment, accounts, access, documents, induction. Offboarding gets the same attention as onboarding, because that is the list that removes access when someone leaves. One week.
3. Build — records, leave, attendance, documents. Employee records with the fields that are actually used, the leave request and approval workflow, the attendance or working-time setup, the document library with expiry reminders, and permissions per role decided deliberately rather than accepted as they came. Two to four weeks.
4. Payroll configuration. Pay elements, allowances, deductions, statutory items, employer contributions, pay calendar and payslip layout, plus the export or filing your accountant or payroll provider needs. Every rule is traceable to a source, so it can be checked again when the rules change. Two to four weeks.
5. Historic data in, then a parallel run. Employees, contracts, salary history and accrued leave balances imported and reconciled to the source. Then at least two pay cycles calculated both ways in full, with every person's gross, deductions and net compared individually. Two to three months for the parallel period.
6. Training and cutover. Managers are taught approvals and their own team's records; employees are taught the three things they will ever do, which is request leave, find a payslip and update their details. Short recorded sessions and a printed one-page sheet. The old method is stopped only once the parallel numbers have matched. One to two weeks.

What moves the price

The range is $1,000–$20,000 and it is set mostly by three things.

Whether payroll is in scope at all. HRIS on its own — records, documents, leave and onboarding — sits at the lower end and is a genuinely contained project. Adding payroll brings statutory configuration, a parallel period and a much longer testing burden, and it is what carries a project toward the top of the range.

How many countries you employ in. Each additional jurisdiction has its own entitlements, deductions, filing formats and holiday calendar, and none of it can be copied from the first one. Each one has to be configured, confirmed with a specialist and parallel-run on its own before anyone is paid from it.

Headcount and how messy the existing records are. Fifteen employees whose contracts and leave balances are already in one spreadsheet is quick. Two hundred people whose records are split between a filing cabinet, a legacy system and several spreadsheets, with leave balances that nobody has reconciled in years, is where the data work starts to dominate the project.

What usually goes wrong

The parallel run gets dropped to save a month. You look at a test payslip, decide the numbers are fine, and ask to move straight onto the new system. Then the first real payroll pays four people the wrong amount, and those four tell everyone. The damage is not financial — it is that the whole company now distrusts the system in its first week, and that distrust takes far longer than a month to undo. Two full cycles run side by side, reconciled person by person, is the minimum that makes this safe.

Statutory rates are taken from a convenient source rather than a current one. A rate found in an article, remembered from last year, or produced by a generative tool looks authoritative and may be out of date. The under-deduction is discovered at filing, the penalty falls on the employer, and the blame falls on whoever configured it. Every statutory figure must come from a named, current source or from a payroll specialist, and be recorded as such.

Permissions are left as they arrived, and offboarding never removes access. This system holds salaries, national identity numbers and bank details. Default configurations are frequently more open than anyone intends, so a line manager can see pay across departments, or a leaver keeps access for months because the departure checklist ends at the laptop. Both are ordinary configuration failures with legal consequences, and both are prevented by treating role permissions and the offboarding checklist as deliverables.