An IRP5 or IT3(a) records employment remuneration and related tax information for the relevant reporting period. Employers prepare certificates under SARS requirements and reconcile them with payroll declarations and payments. Employees should compare their final certificate with their records and ask the employer to investigate errors rather than altering an employer-issued certificate themselves.
Understand what the certificate represents
An employee tax certificate is a reporting document produced from the employer’s payroll history. It is not a new calculation of the employee’s entire personal tax position. It describes the relevant employment income and associated items using SARS fields and codes, including employees’ tax where appropriate. Other sources of personal income or deductions may still affect the employee’s annual return.
The distinction between an IRP5 and an IT3(a) should follow the applicable SARS rules, including whether tax was withheld and the relevant reason codes. An employer should not choose whichever document name an employee prefers. The current SARS certificate guide explains the formats and validation requirements. A familiar-looking certificate can still be incorrect if its period, identity details or financial codes are wrong.
The certificate belongs to a specific employer and reporting period. Where a person has several employers or separate employment periods, the reporting treatment needs to reflect those facts. Keep the employer registration and employee identifiers consistent across payroll, reconciliation and the document supplied to the employee. Small differences in these fields can create a mismatch even when the salary totals are correct.
Build the certificate from controlled payroll history
Begin with a final payroll report for the relevant period, not with the employee’s latest payslip alone. A single payslip may show year-to-date figures, but those figures need to be supported by the complete history, including starters, leavers, adjustments and benefits. Confirm that opening balances imported during a payroll migration have not been omitted or duplicated.
Map each pay component to the appropriate current SARS code. Keep explanations for unusual items such as termination payments, directive-related amounts or corrections. A general “other income” entry should not become a convenient destination for amounts the preparer has not classified. If the correct treatment is uncertain, resolve it before the final certificate is released.
Retain a control total for certificates, remuneration and tax, and compare it with the payroll and reconciliation reports. The purpose is to identify missing or duplicate employees and unexplained differences. A total that agrees does not prove every employee is correct: one employee’s overstatement may offset another’s understatement. Review selected employee records as well as the combined amount.
Validate personal details before the submission window
Check employee names, identity or passport information, tax reference information and employment dates against reliable records. Do this throughout the year, especially for new starters. Waiting until the submission deadline turns a straightforward data query into an urgent exception. Employees should be told what information is missing and given a safe way to provide it.
SARS applies detailed certificate validation rules, including rules concerning income tax reference numbers. Use the current employer guide and certificate specification for the relevant transaction year. Do not assume that a number accepted by an older payroll version will satisfy a later submission. Equally, do not claim that every missing-number scenario has the same consequence without checking the current rule and the employee’s circumstances.
Where the employee cannot locate a tax number, use the appropriate official registration or verification process. Never insert a made-up number to get past a software screen. Keep sensitive identity information out of general email chains and shared exception reports. Management may need to know that a case is unresolved without needing the full identification document attached to every update.
Distinguish interim submission from final issuing
Employer reporting includes interim and annual reconciliation processes, but a certificate submitted as part of an interim reconciliation is not automatically a final certificate for the employee. SARS’s reconciliation guidance distinguishes those uses and contains special rules where employment has ended or the employer has ceased to be an employer.
The practical control is to label the process and output clearly. A draft certificate for internal checking should not be sent in a way that makes the employee believe it is final. A final certificate should correspond with the acceptable reconciliation and the applicable issuing rules. Preserve the submission result and the exact certificate version supplied.
Do not describe an annually recurring filing window as a permanent fixed deadline without checking the current notice. SARS publishes the relevant reconciliation dates, and software specifications can change. Put the current window in the employer’s compliance calendar, together with an internal preparation date that allows time for validation errors, employee queries and corrections.
Review what employees should compare
Employees can make a useful first check by comparing the employer name, tax year, employment dates and personal details with their own records. Next, compare the certificate’s broad remuneration and tax figures with the final payroll history. A difference is a reason to investigate, not proof that either document is automatically wrong.
Taxable benefits and reporting classifications can mean that a certificate total does not equal the cash paid into the bank. Bank deposits alone therefore cannot establish the correct taxable remuneration. Ask the employer for an explanation of the relevant item, particularly where a benefit or earlier-period adjustment appears. The explanation should identify the payroll record and treatment rather than simply state that the software generated it.
Employees should keep the final certificate and correction correspondence with their tax records. If information on a pre-populated personal return differs from the employer’s final certificate, record the difference and contact the employer or appropriate adviser. Do not edit a PDF certificate or invent a replacement amount as a shortcut to completing a personal return.
Correct the source record rather than only the PDF
Suppose an illustrative employee discovers that the employment start date is wrong. Changing the displayed date in a PDF would not correct the employer’s payroll database or SARS submission. The employer needs to investigate the source record, determine the affected reporting process and use the appropriate correction route. The employee should then receive the corrected final document where required.
The same principle applies to an omitted payment or an incorrect tax code. Establish whether the underlying payroll was wrong, whether the reporting mapping was wrong or whether the employee received an outdated version. Those causes require different remedies. Keep a short chronology showing the original submission, correction request, revised result and delivery to the employee.
Avoid producing duplicate final certificates simply to make a query disappear. The current certificate and reconciliation rules govern cancellations, replacement documents and corrections. Where earlier tax years are involved, retain the relevant historical specification as well as the current process guidance. A current software format does not mean historical amounts may be casually moved into a later year.
Keep evidence that supports future queries
A useful certificate file links the final payroll totals, employer reconciliation, submission outcome and issued documents. Preserve records of unusual classifications and directives where applicable. Keep the file organised by employer and period so it remains understandable when a payroll administrator leaves or the software provider changes.
Access should be limited to people with a legitimate role. An employer can provide an employee with their own certificate without giving them a folder containing everyone else’s information. Check attachment names, recipient details and access permissions before distributing documents in bulk. A simple recipient-control review can prevent a serious confidentiality problem.
Document which system is the authoritative source for the final certificate. If a payroll package, eFiling record and internal folder all contain different versions, staff need to know which has been submitted and issued. Keep superseded versions identifiable instead of deleting the history. That makes later explanations easier and reduces the risk of an old certificate being re-sent by mistake.
Use the annual cycle to improve payroll quality
Certificate preparation often reveals problems that began months earlier: inconsistent employee names, unreviewed opening balances, unusual pay codes or unresolved corrections. Feed those findings back into onboarding and monthly payroll. A year-end checklist alone cannot compensate for a year of uncontrolled source data.
Create a short improvement list after the reconciliation closes. Assign responsibility for missing-information checks, pay-code reviews and software updates. Where the same query affected several employees, correct the common process rather than handling each case as an isolated exception. Measure whether the next reporting cycle contains fewer unresolved cases and less manual rework.
Axia Finance can assist with employee certificate preparation and payroll reconciliation as part of an agreed scope. Employees with personal tax questions may also need advice on their full income position. A reliable certificate is an essential input to that conversation, but it does not justify a promise about the employee’s final assessment or refund.
Common questions.
Does an IRP5 guarantee a tax refund?
No. It reports employment information under SARS rules. A refund or additional liability depends on the employee’s complete assessed tax position, including other relevant income, deductions and credits. Neither an employer nor an article should promise a particular assessment outcome.
Can an employee fix a certificate themselves?
An employee should identify the suspected error and provide supporting information to the employer. The employer must investigate and use the appropriate payroll and SARS correction process. Editing a document privately does not correct the official submission or the employer’s records.
Should every interim certificate be sent to employees?
No. Interim submission and final issuing have different rules, including special circumstances for ended employment. Follow the current SARS certificate and reconciliation guides and clearly distinguish draft, interim and final documents.
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.
- SARS: Completion and submission of employees’ tax certificates, 2027
- SARS: Guide to the employer reconciliation process
- SARS: Completing and submitting employer declarations
- SARS Guide for Employers: Employees’ Tax, 2027 tax year
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.
