Payroll Setup Checklist South Africa
Set up payroll records, PAYE, UIF, SDL, payslips, approvals, and month-end controls before the first South African payroll run.
- Payroll setup should confirm employee records, pay rules, statutory registrations, approval steps, and monthly reporting before the first run.
- PAYE, UIF, and SDL should be reviewed as part of one payroll setup, not as disconnected registrations.
- A payroll file is not ready if employee details, bank details, tax numbers, leave rules, and approval evidence are still incomplete.
- The setup should leave a repeatable monthly process for payslips, EMP201 figures, UIF declarations, and payroll journals.
Payroll setup is where a South African employer decides whether payroll will run as a controlled monthly process or as a set of urgent fixes. The first payslip may look simple, but payroll quickly connects to employee records, PAYE, UIF, SDL where applicable, EMP201 submissions, leave records, salary approvals, bank payments, and accounting journals.
That is why setup should happen before the first run is processed. A business that waits until salaries are due usually ends up collecting employee information, confirming SARS access, checking UIF details, and approving payment files at the same time. That is the point where payroll errors become expensive to find and difficult to explain.
If the business needs practical monthly support, connect this setup checklist to Payroll Services. If payroll must also feed reliable management accounts, read it with Payroll in Accounting.
Quick Answer
A payroll setup checklist should confirm five things before payroll starts:
- who will be paid and what records support each employee
- which statutory obligations apply to the employer
- how pay, deductions, benefits, leave, and reimbursements will be calculated
- who approves the payroll before payment
- how the payroll output will support EMP201, UIF, payroll journals, and later EMP501 work
The key point is timing. The setup file should be complete before the business is under pressure to pay people.
Key Numbers
| Item | Number / threshold | Notes |
|---|---|---|
| EMP201 timing | Within 7 days after month-end | SARS states that EMP201 and payment, if applicable, must be submitted within this period. |
| UIF return timing | No later than the 7th of each month | uFiling describes monthly UIF return timing for the preceding month. |
| Payroll setup checks | 5 | Employee records, statutory setup, pay rules, approvals, and handoff controls. |
| Reconciliation rhythm | Monthly | Payroll gets harder to fix when differences roll forward. |
These numbers matter because payroll is not only an employee payment process. It is also a monthly evidence process.
1. Confirm employee records before pay is calculated
Start with the employee file. Payroll cannot be clean if the source records are still incomplete.
The setup file should include:
- employee full name and identity details
- tax number where available
- start date and employment status
- bank details
- contract or appointment details
- agreed salary, wage, commission, overtime, allowance, or benefit rules
- leave opening balances where relevant
- emergency or HR contact details where the employer keeps them
The payroll provider or finance lead should not have to guess whether a payment is salary, reimbursement, commission, bonus, director remuneration, or contractor cost. Each treatment can affect payroll, tax, and accounting differently.
2. Review PAYE, UIF, and SDL before the first run
Payroll setup should test the employer registration position before amounts are deducted. SARS guidance on registering for employees' tax explains that employers who need PAYE or SDL registration also need to deal with UIF contribution registration. In practice, the employer should treat the setup as one payroll compliance file instead of a series of separate admin tasks.
Check whether:
- the business has an active PAYE reference where required
- UIF registration and declaration responsibilities are understood
- SDL is considered where applicable
- the person submitting employer returns has the right access
- payroll records can support the first EMP201 period
This step is not only about registration. It is about making sure the first monthly payroll cycle can be declared and reconciled without reconstruction.
3. Set pay rules that match the employment reality
Payroll mistakes often start when the pay rules are vague. The business may know what someone should receive, but payroll needs to know how that amount is made up.
Document the rules for:
- basic salary or hourly wage
- overtime
- commission
- bonuses
- allowances
- reimbursements
- unpaid leave
- benefit deductions
- retirement or medical aid deductions where relevant
The goal is not to create a long policy document. The goal is to make the calculation repeatable. If a manager and payroll processor would calculate the same person's pay differently from the same facts, the setup is not ready.
Requirements Table
| Requirement | Why it matters | Owner |
|---|---|---|
| Employee master file | Prevents missing or inconsistent employee records | Employer |
| Statutory registration check | Confirms PAYE, UIF, and SDL treatment before filing starts | Employer and adviser |
| Pay-rule schedule | Keeps salaries, overtime, allowances, and benefits consistent | Payroll |
| Approval workflow | Shows who signs off payroll before payment | Management |
| Monthly payroll pack | Supports EMP201, UIF declarations, journals, and later reconciliation | Payroll and finance |
Each item should be visible before the first payroll deadline arrives.
Numbered Checklist
- Collect employee identity, tax, bank, contract, start-date, and pay-rule information.
- Confirm PAYE, UIF, and SDL responsibilities before payroll deductions are processed.
- Build the payroll calendar, including cut-off dates, approval dates, payment dates, and return dates.
- Prepare the payslip, payroll summary, bank payment, and payroll journal handoff process.
- Keep a monthly exception log so payroll changes are visible before the next run starts.
4. Build an approval path before salary payment
Payroll should not move straight from input to payment. A small business still needs an approval step, especially when overtime, commission, leave without pay, bonuses, or starter and leaver changes are involved.
A simple approval file should show:
- who submitted the payroll input
- who reviewed the calculation
- who approved the payment amount
- what changed from the prior month
That record matters later. If an employee query, SARS review, or management-account question appears, the business can explain what was approved and why.
5. Connect payroll to the accounting handoff
Payroll setup is incomplete if the finance team only receives a net salary total. The accounting file needs the payroll summary, statutory deductions, employer costs, net pay, and any exceptions that affect the month.
For this reason, the setup should define the monthly handoff from payroll to accounting. That handoff usually includes the payroll summary, bank payment support, statutory liability summary, and payroll journal. The same pack supports Payroll Month-End Checklist work later.
When the handoff is weak, payroll may still pay employees correctly while the ledger carries unclear balances. That creates avoidable work at EMP201, EMP501, management reporting, and year-end.
6. Keep payroll changes visible
Most payroll problems are caused by change. A new employee starts. A salary changes. A commission is approved late. A leaver needs a final payment. A reimbursement is treated as ordinary pay. None of those items is unusual, but each one needs evidence.
The setup process should therefore include a change log from the first month. The log does not need to be complicated. It should show the employee, the change, the effective date, the approval, and whether the change affects PAYE, UIF, SDL, leave, or the payroll journal.
That control keeps payroll from becoming dependent on memory.
7. Manager takeaway
A strong payroll setup makes the monthly payroll cycle calmer because the hard questions are answered before the payment date. The employer knows who is on payroll, what each person should be paid, which statutory steps apply, who approves the run, and what records must be retained after the run.
That is the practical standard. Payroll should not depend on last-minute messages or undocumented assumptions. It should produce a repeatable monthly record that employees, management, SARS, labour processes, and accounting can all rely on.
Related Resources
- EMP201 Submission Checklist for the monthly declaration and payment cycle
- EMP501 and IRP5 Reconciliation Checklist for interim and annual employer reconciliation work
- Payroll Reconciliation Checklist for tying payroll back to bank and ledger balances