Cloud payroll software for South African employers

Desktop payroll ties the payroll file to one machine. If that machine fails, is stolen, or belongs to the bookkeeper who has left, the company's statutory records go with it — and SARS still expects five years of payroll records under section 29 of the Tax Administration Act.

Cloud payroll removes the single point of failure. Data is stored redundantly and snapshotted nightly, tax tables update centrally when SARS publishes new brackets, and access is controlled by user account rather than by who is sitting at the desk.

Payroll data is special personal information under POPIA: identity numbers, banking details, medical scheme membership and salary. Cloud payroll only helps compliance if access is controlled and provable.

Every view and change in Payroll Africa is written to an audit log with a timestamp and user. Payslips are delivered as time-limited secure links rather than open attachments, banking details are masked in the interface, and administrators can restrict a user to a single payroll group so wage clerks never see executive salaries.

Approvals are the part of payroll that stalls when someone is out of the office. Managers approve leave, overtime claims and the payroll run itself from a phone browser, and employees use the self-service portal for payslips, IRP5s and leave applications rather than emailing the payroll administrator.

Moving to the cloud does not mean giving up control of the numbers. Every earning, deduction, company contribution and hourly rate remains editable before approval, off-cycle and bonus runs can be created at any time, and a variance report compares each run to the previous period before anything is finalised.

The fear with desktop payroll is that the history is trapped in the software. It is not. Every South African desktop package — Sage Pastel Payroll, VIP, Crest, Paywell and Accsys — can export employee masterfiles, year-to-date totals and leave balances to CSV or Excel, and those three exports are all that is needed to rebuild the company in the cloud.

A typical migration runs over two working days: day one the exports are mapped and loaded into a sandbox company, day two the first parallel run is compared line by line against the last desktop payslip run. Only when net pay, PAYE, UIF and SDL agree to the cent is the live switch made, so the EMP501 for the year still reconciles across both systems.

Employers usually discover the cost of on-premise payroll on the worst possible day. A failed hard drive on the 24th, a bookkeeper who leaves with the only licence password, or a ransomware infection on the office server all produce the same outcome — no payslips, no EMP201 figures and no way to prove what was paid.

Rebuilding a 40-employee payroll from bank statements and paper payslips takes roughly a week of work, and the late EMP201 attracts a 10% penalty plus interest under section 213 of the Tax Administration Act. A ransomware or theft incident involving identity numbers and banking details is also a reportable security compromise to the Information Regulator under section 22 of POPIA.

Cloud payroll changes the failure mode. If a laptop is stolen the payroll is untouched — the thief has a browser, not the data — and access is revoked by disabling the user account rather than by chasing hardware.

Cloud payroll is not automatically the right answer for every employer, but four situations make it decisively better than a desktop package.

Cloud hosting on its own proves nothing about compliance. Ask any provider these questions in writing before signing.