Payroll processing turns approved employment information into earnings, deductions, employer costs and net payments. A sound process checks the inputs, applies the relevant rules, obtains payment approval and preserves an audit trail. The payslip explains the result to the employee; it does not replace the employer’s tax, labour or reporting obligations.
Start with the complete pay cycle
Payroll is a recurring business process rather than a single calculation at the end of a month. It begins when an employee joins, changes roles, takes leave or records time. It continues through approval, calculation, payment and the resolution of questions after payday. A useful process makes each handover visible, so the person preparing payroll is not expected to infer decisions from messages or bank activity.
Choose a clear calendar for the organisation: when variable inputs close, when managers approve them, when the draft is reviewed and when authorised payments are released. An internal cut-off helps organise work but does not allow an employer to delay remuneration unlawfully or disregard a valid entitlement. Urgent changes need an exception route with named approval, not an informal instruction that bypasses the records.
The Basic Conditions of Employment Act sets requirements affecting remuneration and written payment information, subject to its application provisions. Contracts, collective agreements and sector rules can add relevant conditions. Map those requirements before choosing software settings. A convenient default in a payroll package is not evidence that the setting is right for every employee.
Build an employee record that can support the calculation
A payroll record should link the employee’s identity and start date to the employment terms used in the pay run. Record the agreed pay basis, ordinary working arrangement, relevant benefits and approved deductions. Distinguish a monthly salary from an hourly rate and document how changes take effect. Keep the signed agreement or approved amendment accessible to the people who need to verify the entry.
Check tax reference information, identification details and the dates needed for reporting before the first year-end submission. An incorrect digit may not affect the employee’s bank payment, yet it can stop certificate validation later. Do not solve that problem by inventing a number or borrowing another employee’s details. Ask for the correct evidence and use the available official verification or registration route.
Bank changes deserve particular attention because they redirect money. A practical control is independent confirmation through a previously established contact channel, together with a record of who checked the instruction. That is an internal fraud control, not a universal statutory formality. Restrict access to identity, salary and banking information. A shared payroll spreadsheet should not become a general staff directory containing information everyone can see.
Separate fixed terms from monthly changes
The fixed record holds continuing terms such as the employee’s salary or recurring allowance. A separate change schedule captures approved overtime, unpaid time, commission, once-off awards and other movements. This separation makes it possible to explain why this month differs from the previous month without rebuilding the employee’s history from email.
For every variable item, identify the period, quantity, rate or calculation basis, approver and supporting record. A commission instruction should explain the approved amount or formula and the sales period to which it relates. An overtime instruction should identify the hours and the applicable agreement or rule. A manager’s approval of hours does not, by itself, settle every question about legal entitlement or the correct tax treatment.
Record rejected or deferred inputs as well as accepted ones. If a timesheet arrives after the internal cut-off, someone must decide how it will be handled and communicate that decision. Leaving it outside the system without an owner makes omission likely. Preserve the original instruction when a correction is made, so the review trail shows both what was received and why the final payroll entry changed.
Review gross pay, deductions and net pay separately
Gross remuneration is not always the amount paid into the employee’s bank account, and employer cost is not always the same as gross remuneration. Review those measures separately. Some items are cash payments, others are benefits reported for tax purposes, and employer contributions may be additional costs. Combining everything into one total can obscure whether the employee’s net pay and the accounting entry are both correct.
Use the current SARS employer guide when assessing employees’ tax and the relevant payroll contribution rules. Different statutory calculations can use different definitions of remuneration. An item’s label in a spreadsheet does not determine its treatment. Where a benefit, allowance, directive or unusual payment needs interpretation, resolve that question before treating a previous month’s result as a precedent.
Compare the draft with the prior period and with approved changes. Explain new starters, leavers, unusually high amounts, negative net pay and unexpected differences. Recalculate a small sample from source information, especially after a software update or significant rule change. A reasonableness review complements the payroll calculation; it should not become an exercise in forcing the new total to resemble last month when the underlying circumstances have changed.
Make the payslip useful to the employee
A payslip should allow an employee to understand which period is being paid, the earnings included, the deductions made and the amount due. The BCEA’s written-information provisions are the starting point where applicable. Check the required particulars rather than assuming that a document headed “payslip” automatically meets them. The format can be clear and compact while still providing the necessary detail.
Use descriptions that staff can recognise. “Overtime: approved hours for October” is more useful than an unexplained internal code. Keep taxable benefits distinguishable from cash earnings, and show deductions in a way that makes their purpose understandable. If the software uses shortened labels, supply a simple explanation when employees first encounter them. A confusing slip generates avoidable questions and can conceal real errors.
Deliver slips through a method appropriate for confidential employment information. Check the recipient before sending, avoid exposing several employees’ documents in one message and agree a safe route for replacement copies. An employee’s query should lead to a documented investigation. Explain whether a change affects only the display, the current payment, a statutory submission or a later correction; those are different outcomes.
Use an approval pack before money is released
A practical approval pack contains the draft payroll, the movement report, a schedule of exceptions and the proposed payment totals. The reviewer should be able to trace a sample of changes to approved instructions. Approval should state what has been authorised: payroll calculations, employee bank payments, statutory payments or all of those within a defined process. A vague “looks fine” message leaves the scope uncertain.
For example, a small consultancy adds one employee and pays a once-off project award. The preparer identifies the new employee separately, checks the start date and first-period basis, and attaches the approved award instruction. The reviewer compares the total bank file with net pay, confirms that the award was not entered twice and checks the employer cost report. These are illustrative controls, not a prescribed checklist for every business.
After approval, protect the final version. If a change is necessary, produce a revised report and obtain the appropriate further approval. Do not let a bank file and payslip pack silently diverge. Keep evidence of release and settlement, including rejected payments. A payment failure does not mean the payroll liability disappeared; it creates a matter to investigate and resolve.
Close the run and connect it to accounting
After payday, reconcile the payment report to the bank and investigate returns or short payments. Post the payroll journal to the correct accounting period and check that clearing accounts explain amounts still payable. Employer contributions, employee deductions and net wages should not be left in a single suspense balance that nobody can interpret.
Monthly tax declarations and later employer reconciliations are connected to the payroll record. SARS explains the relationship between the EMP201, EMP501 and employee certificates in its employer declarations guidance. Keep submitted returns, payment references and supporting schedules with the relevant period, rather than relying only on a payroll software dashboard.
At the end of each run, note unresolved questions and assign an owner and target date. Examples include an employee’s missing tax information, a bank rejection or a pending interpretation of a benefit. Review these before the next run. A closed month should mean the records are controlled and exceptions are visible, not that every open issue has been hidden by carrying forward an unexplained amount.
Improve the process as the team grows
The right process for a handful of stable salaries may become inadequate when the business adds shifts, sales commissions or multiple pay frequencies. Review the process when complexity changes. Look for repeated late instructions, repeated manual adjustments and employees who are difficult to reconcile across systems. Those patterns indicate a process issue, even when the preparer manages to produce a payment on time.
Decide what management needs to see: headcount, total employer cost, department allocations and significant changes can all be useful. Keep the report’s purpose separate from the confidential employee detail. A department manager may need a cost summary without needing every tax number and bank account. Access should follow responsibilities and be removed when roles change.
Axia Finance can assist with payroll preparation, records and reconciliation as part of an agreed service scope. Employment-law interpretation, disputed deductions and unusual tax treatments may require additional professional input. Before handing over, agree who approves employee changes, who releases payments and who monitors statutory obligations. Outsourcing preparation works best when responsibility and the underlying evidence remain clear.
Common questions.
Can payroll software replace a review?
No. Software calculates from the information and settings supplied. A review is still needed to check employee changes, unusual payments, the applicable rules and whether the bank payment agrees with the approved result. The level of review should reflect the business’s size and payroll complexity.
Is a payslip the same as an IRP5?
No. A payslip explains a payment period. An IRP5 or IT3(a) is an employee tax certificate prepared under SARS rules for the relevant reporting period. They should be consistent with the same underlying payroll history, but they serve different purposes.
What should happen when a payslip is wrong?
Record the query, check the original instructions and calculation, and determine which records or payments need correction. Preserve the earlier version and the reason for the change. Tell the employee what was corrected and when any payment difference will be resolved.
Support for your next step.
Axia Finance supports individuals and businesses across Greater Cape Town, the Cape Winelands and the Cape West Coast. Explore our payroll services services or discuss your circumstances with us.
Continue with the payroll knowledge collection for related practical guides.
Sources and further reading.
Official references consulted for this guide. Rules and administrative processes can change; check the applicable period and your circumstances.
- Basic Conditions of Employment Act — Department of Employment and Labour
- SARS Guide for Employers: Employees’ Tax, 2027 tax year
- SARS: Completing and submitting employer declarations
General educational information, current to 5 November 2026. This guide does not determine the legal, tax or accounting treatment of a particular person or transaction. Obtain advice appropriate to your facts before acting. Read our editorial approach.
