What the EMP501 reconciles
The EMP501 is part of SARS’s employer reconciliation process. It connects the employer’s declared liabilities, payments and employee certificate information for the relevant period.
The SARS reconciliation page identifies three sets of records to reconcile: monthly EMP201 declarations, relevant payments and the IRP5 or IT3(a) certificate values. The review includes the applicable PAYE, SDL, UIF and ETI treatment.
Confirm whether the work concerns the interim or annual period. Use the current submission requirements for that cycle. A period label copied from a prior file can cause problems even when its arithmetic appears sound.
Why reconciliation involves more than one total
Prepare a schedule by month and component. Compare payroll calculations with the declarations, then compare payments with the SARS account. Review the employee certificates against payroll separately.
This makes the pattern of a difference visible. A duplicated certificate, an unprocessed payroll correction and a payment applied to another period can produce different problems that should not be fixed in the same way.
Retain the supporting explanation for adjustments. Do not change a correct liability or certificate simply because a software screen will then balance. A successful submission should reflect the underlying facts, not just satisfy an arithmetic check.
The EMP501 mismatch guide provides a practical diagnostic sequence and approval checks.
Illustrative example: payroll migration duplicates a certificate
A fictional employer changes payroll software during the year. The old system contains an employee’s earlier earnings, and the new system imports those figures. During reconciliation, a second certificate is also captured for the same earlier employment information.
The resulting certificate totals exceed the correct payroll history. Paying additional money or increasing monthly liabilities would not fix the underlying duplication.
The employer checks the employee’s identity, employment period, certificate records and migration history. It establishes which records should remain and uses the appropriate correction or cancellation process for the actual submission stage.
After correcting the evidence, the team repeats the affected reconciliation checks and retains the outcome. This example illustrates a possible cause, not an assumption that every difference arises from payroll migration.
What an EMP501 is not
An EMP501 is not an individual employee’s income-tax return. The employer reconciliation supplies employment information, while the employee’s overall tax position may include other income and deductions.
It is not the EMP201 monthly payment declaration, a Compensation Fund return of earnings or a Letter of Good Standing. Using the same payroll data does not merge these separate processes.
Submission also does not eliminate the need to review SARS correspondence or validation results. Keep the acknowledgement, resolve reported issues and retain the corrected records where changes are required.
For EMP501 preparation and submission support, provide the period’s payroll, monthly declarations, payments and employee certificates. Give each unresolved difference a named owner and a recorded next action. Explain prior submissions and known corrections so the adviser can use the appropriate route.
Sources and review
Checked on 30 September 2026. Use the linked official guidance for current requirements and forms.
- SARS reconciliations
Three reconciliation elements, applicable period and employer certificate process.
- SARS employer declarations
EMP501 versus EMP201 and correction-stage distinctions.
Support for EMP201 EMP501 submissions
Discuss your records and the support your business needs.
Explore EMP201 EMP501 submissions