By role · Payroll teams
Close payroll with every figure explained.
Simulate the month against the last one paid, see exactly why someone’s pay changed, and hand it to an approver knowing it adds up.
my-workspace.hrmspay.com/dashboard/payroll-run/133
Monthly Staff
October 2026
People
52
Gross
4,612,300.00
Net
3,298,914.60
Changes since September (last paid)
Brian Otieno
Raise from 1 October
Aisha Mohamed
Two days unpaid leave
Faith Achieng
SACCO loan instalment
Processed by Brian Kamau · approval by Grace NjeriSend backApprove
Sound familiar?
- Finding why net pay moved takes hours.
- Back pay and corrections mean manual adjustments.
- Every new allowance needs the vendor.
With HRMSPay
- Show how it was worked outEvery payslip line opens to its inputs, the rule that fired and the result.
- Back pay and reversals built inBackdated changes recalculate past months; an unpaid run can be undone with history kept.
- Rules you change yourselfAdd a component, a bracket or a formula, test it on a real person, and date it.
Close every month knowing the payroll is right.
See HRMSPay run a month for an organisation like yours, with your pay cycles, your countries and your ERP.
- Statutory rules for your country
- Your data moved in with you
- A parallel run before you go live