What companies ask before they switch.

No. The pay engine runs on rules you configure, so it pays people in any country and currency. Kenya comes ready out of the box; another country is set up as its own rates, bands and returns, alongside the ones you have.

Both. The same system pays a team of twenty or a group of companies with thousands of staff, several pay cycles, departments, approval chains and organisations under one sign-in.

Yes. PAYE bands and personal relief, NSSF, SHIF and the Housing Levy come set up, each dated from when it applies. P10 returns, P9 tax cards and the contribution schedules are ready as soon as payroll is approved.

It prepares them. You download the P10 or the bank file and upload it to iTax or your bank’s bulk payment service, then record what the bank paid. Nothing leaves without a person checking it.

Yes. Each payroll area has its own cycle (monthly, weekly, fortnightly or daily-rated) with its own pay day, working hours and rest days.

Only roles you allow. Salaries, bank accounts and tax PINs are masked for everyone else, department managers never see pay, and every full view or download is recorded in the audit log.

No. One sign-in can belong to several organisations, with a different role in each, and switch between them from the menu.

We load your employees, contracts, bank and tax details with you, then run a parallel payroll so you can compare HRMSPay’s figures with your last month before going live.

Yes. HRMSPay runs in the browser on any phone, tablet or computer, so employees can check payslips and apply for leave without installing anything.

Yes. HRMSPay connects to SAP, Oracle, Microsoft Dynamics, IFS or any ERP with an API. Fields are mapped, not coded: payroll journals and results go out with your GL codes, and employee changes come in for review.