Weekly pay, real overtime categories, and timesheets that need a client's sign-off before anyone gets paid β that's a genuinely different shape of payroll than a monthly office job, and most payroll software isn't actually built for it.
No credit card required.
Standard hours, weekday overtime, Saturday, Sunday, and public holiday rates are each their own category β calculated and taxed correctly, not lumped together and estimated.
PAYE is annualised correctly against a worker's real pay frequency, not just divided by 12 as if everyone were paid monthly β a common, quiet miscalculation in payroll tools built for salaried staff first.
Timesheets go through an approval step before payroll processes them β the same hours can't be paid out twice across overlapping weekly runs, and nothing gets paid without approval first.
Run several Pay Groups β different pay days, different frequencies β within the same company, rather than needing a separate account per site or client contract.
Not just a PAYE calculator β the full chain from timesheet to SARS submission.
Capture personal details, banking, tax numbers and employment terms once. Migrating from Excel or another system? Bulk import your whole employee list instead of retyping it.
A flat salary field hides the real answer. Build a proper Cost-to-Company package β basic salary, allowances, employer contributions β so the number you budget against is the number it actually costs.
Cross-referencing emails every Monday to check who's off and whether the balance is even right, isn't sustainable past a handful of employees. Employees request, managers approve, balances update themselves.
That's a real, common complaint β generic timesheet apps ignore payroll entirely. Ours doesn't: approved hours (weekly, fortnightly, or monthly) feed straight into the pay run, no re-collecting them from a spreadsheet or WhatsApp.
Employees log into their own portal to download payslips and IRP5 certificates, check leave balances, and submit requests directly β without emailing you for a copy every time.
That mismatch is where trust breaks down. EMP201 due dates are calculated correctly against weekends and public holidays, and IRP5/EMP501 are built from the same real SARS source-code data as the payslip β not a separate spreadsheet that quietly drifts out of sync.
Payroll journals post directly into ZinithX Accounting the moment a run is approved. No exporting a CSV from one system and re-entering it into another.
Once payroll is approved, generate a single EFT batch ready for your bank β net pay to every employee, in one file.
One login, every client. Employee count pooled across your whole book, so growing your client list doesn't mean juggling more separate accounts.
Up to 5 employees
1 user
R20 per additional employee
Up to 10 employees
2 users
R20 per additional employee
Up to 25 employees
3 users
R20 per additional employee
Up to 50 employees
3 users
R20 per additional employee
Up to 75 employees
4 users
R20 per additional employee
Up to 100 employees
5 users
R20 per additional employee
Over 100 employees β contact us
Managing payroll for multiple clients? See accounting practice pricing β
Sign up and run your first pay run, all in the same trial.
Start Your 14-Day Free TrialNo credit card required.