Payroll software that gets the statutory position right.
How to judge a payroll system on the things that actually go wrong.
Payroll software is usually evaluated on its calculation engine, which is almost never the problem. Payroll goes wrong because of what arrives at it: attendance submitted late, changes nobody approved, records missing an identifier, a rate that changed mid-period. A payroll system that sits on top of the records producing those inputs is structurally different from one that receives a spreadsheet — and that difference is what to evaluate.
What to check before you buy payroll software here
Run these against any payroll system you are considering, including this one.
- Where do the inputs come from? If attendance and leave arrive as files, you have automated the calculation and kept the problem.
- Can you see the payroll position before the run? Knowing on day three that six records will block the run is worth more than any feature in the calculation.
- Is variance attributed to a cause? A total that moved without an explanation gets approved anyway, which is how errors survive.
- What happens to an incomplete record? It should hold the payment visibly, not drop the person from the run.
- Is the run locked on approval? If corrections can be made in the file afterwards, the source records stay wrong.
- How is statutory handling configured and kept current? Ask who is responsible when a rate changes, and what the process is.
On statutory rates. This page deliberately does not publish current statutory rates, bands or thresholds. They change, a marketing page is the wrong place to maintain them, and a stale figure here would be worse than none. What we describe is how statutory handling is configured and maintained for your implementation — the current position should always be confirmed against the relevant authority.
How PiPO HRIS approaches it
Inputs before calculation
Attendance and leave close before the cycle opens, and changes to pay elements carry an approver.
Payroll readiness
A live view of how much of the cycle is ready to pay and exactly what is blocking the rest — while there is time to fix it.
Explained variance
Movement against the previous period attributed to cause: starters, leavers, overtime, rate changes.
Configured statutory handling
Statutory deduction handling configured per implementation against the rules that apply to your organisation, and maintained as part of support.
Common questions
Statutory deduction handling is configured per implementation against the rules that apply to your organisation, and reviewed with you before go-live. We confirm what applies to your specific situation during scoping rather than claiming every scenario is automated out of the box.
Yes. Organisations commonly run a monthly cycle for permanent staff and a separate cycle for casual and frontline workers, in the same environment.
Payment file formats are configured to the banks you actually use. The specific format is confirmed during scoping.
The configuration is updated as part of ongoing support. The current statutory position should always be confirmed against the relevant authority.
Statutory detail on this page reviewed for Kenya. Rates and thresholds change — confirm the current position before relying on it.
See PiPO HRIS around your workforce.
Book a demo and we will walk through the parts relevant to your organisation.