Accounter Payroll runs South-African payroll on a calculation engine verified to the cent — PAYE, UIF, SDL, ETI, medical credits and the statutory filing set, with leave and an employee self-service portal in the same platform.
No enforced period close. Edit any historical period safely. Recompute a migrated year through our own engine — and reconcile it against your own figures before you go live.
| No. | Name | Pay point | Jul | Jun | May |
|---|---|---|---|---|---|
| 0002 | Thabo Nkosi | Head office | Draft | Done | Done |
| 0003 | Gerhard Botha | Head office | Draft | Draft | Done |
| 0004 | Lerato Mokoena | Cape Town | Done | Done | Done |
We stripped the friction out of running payroll while keeping every bit of the statutory rigour.
Payslips are simply Draft ⇄ Completed. Calculation and persistence happen on Completed, and reports and exports become available — no rigid "close the period" gate before you can do anything.
Need sign-off? A per-cycle checkbox adds a Release step that gates reports and exports only — never calculation. Turn it on for the businesses that require it, off for the rest.
Fix a past period with tiered warnings and a correct per-employee, YTD-aware cascade. Once a period is filed, changes are captured as proper correction records.
Built for accountants and bookkeepers: switch between client businesses from a single dashboard, each with its own pay points, cycles and component catalogue.
A downloadable per-business template your clients complete each pay period — new employees plus transactions — validated with a completeness check before it lands.
Employee PII stays in Johannesburg for POPIA, fronted by Cloudflare for security. Your sensitive payroll data never leaves the country.
Set what each business grants and how it accrues; leave accrues on every completed payslip and days taken are captured where you run the payroll. Unpaid leave comes off as a negative income line, so PAYE and UIF follow what was actually earned.
Terminate with a last day and a UIF status code together, so they can't drift apart. Re-employ someone and it opens a second spell — which is what decides their IRP5 certificates, whether PAYE restarts, and which periods they weren't employed in.
Overtime takes its rate from Normal Time at 1.5×, Sunday and public holidays at 2× — enter one wage and the rest follow. Custom components can use a formula. A calculation that can't work is refused when you save it, never mid-pay-run.
The engine implements the current SARS tables exactly — cross-checked against live data, line by line.
Everything you touch on a pay run is one or two clicks away — and the navigation gets out of the way when you don't need it.
One grid per pay cycle, in whichever view suits the job: Current for the live period alone, History for the last three, or Batch to capture the whole company on one screen.
Open a period, capture inputs, and watch the payslip calculate with a per-line trace and SARS source codes on every value.
A second site, on its own address, where an employee signs in to read what they've been paid and ask for time off. Nothing else — no company data, no other employee, and no way to touch the payroll.
Part of the Pro add-on, on the Business and Bureau plans.
Access is yours to give, one employee at a time, and it lapses six months after someone's last day — long enough to fetch the certificate for their final tax year.
Not by getting a permission check right. Portal sign-ins live in their own table and are signed with a different key for a different audience, so an admin session can't be used on the portal and a portal session can't be used anywhere else.
No portal address takes an employee or a company as a parameter. Every query resolves from who signed in, so there is no id to change in a URL and see somebody else's pay.
A password plus whatever second factor the business asks for: none, an authenticator app, or a six-digit code by e-mail — a code rather than a link, because mail scanners follow links and would spend a one-time link before the employee ever clicked it.
Migration adapters don't trust the source's figures. We recompute every historical period through our own engine and reconcile against your source figures line by line, so the year is internally consistent from cut-over.
Secure by design, compliant by default, and ready to scale from your first business onward.
Your employees' personal data stays in South Africa, hosted in Johannesburg — built for POPIA compliance from the ground up.
ID numbers, tax numbers and bank details are encrypted at rest under a key held per business. Access is role-controlled, every change to an employee is audited, and the employee portal signs in with two-factor authentication.
Starts lean for a single business and scales smoothly as you grow — no re-platforming, no disruptive migrations.
Payroll doesn't end at the payslip. Accounter pushes money, returns and journals straight to where they belong — reconciled to the cent before they leave.
Pay the whole run in one batch. Accounter builds the Netcash “PaySalaries” EFT file — balanced to the cent against net pay and ready to upload, with no manual capture.
Submit your monthly EMP201 — PAYE, UIF and SDL less ETI — straight to SARS eFiling from the figures Accounter already reconciled. No re-keying, no portal round-trips.
Every pay run produces a balanced journal — wages, PAYE, UIF and SDL control accounts — to export and post to Accounter Ledger or any general ledger you run. Debits equal credits, every time.
Start free and upgrade as you grow. Save 15% on annual billing
Save 15% when you pay annually.
For large employers and payroll bureaus with custom requirements — volume pricing, bespoke integrations, onboarding and SLAs. We'll build a plan around you.
See the engine reconcile your own numbers to the cent. Book a walkthrough and we'll migrate a sample business with you.