EMP501 and IRP5 Reconciliation Checklist
Reconcile EMP501, IRP5 certificates, EMP201 declarations, payments, payroll records, and correction items before employer filing season.
- EMP501 reconciliation should compare payroll records, EMP201 declarations, payments, and employee certificate totals before submission.
- SARS describes employer reconciliation as involving EMP501, IRP5/IT3(a) certificates, and any certificate cancellation declaration where applicable.
- Monthly EMP201 support makes EMP501 easier because differences are explained before filing season.
- Employee details should be checked early because certificate errors can slow submission and affect employees' personal tax returns.
EMP501 and IRP5 reconciliation is where payroll history has to prove itself. The employer is no longer looking at one monthly run. The business now needs the payroll records, EMP201 declarations, SARS payments, employee certificate values, and correction items to agree across the reconciliation period.
This is where weak monthly payroll control becomes visible. A missing employee tax number, an old EMP201 difference, an unexplained payment allocation, or a certificate value that does not agree to payroll may be small in isolation. During reconciliation, those items can block submission, delay certificates, or create avoidable back-and-forth with SARS.
Use this checklist with EMP201 Submission Checklist and Payroll Reconciliation Checklist. The monthly work and reconciliation work should support each other.
Quick Answer
EMP501 and IRP5 reconciliation should confirm:
- payroll records agree to the reconciliation period
- EMP201 declarations agree to payroll support
- payments made to SARS agree to declared liabilities
- IRP5/IT3(a) certificate values agree to employee payroll records
- ETI, corrections, and certificate cancellations are supported where relevant
The reconciliation should not be the first time the employer discovers monthly payroll differences.
Key Numbers
| Item | Number / threshold | Notes |
|---|---|---|
| EMP501 submissions | Twice a year | SARS e@syFile guidance refers to interim and annual employer reconciliation declarations. |
| Main reconciliation elements | 3 | Employer declaration, employee certificates, and certificate cancellation declaration where applicable. |
| Monthly source returns | EMP201 | Monthly declarations and payments form the history that EMP501 must reconcile. |
| Core records to compare | 4 | Payroll, EMP201, payments, and certificates. |
The numbers are useful because they show why reconciliation cannot be treated as a once-off filing task.
1. Start with the payroll year-to-date record
The payroll year-to-date record is the source that certificate values should come from. Before working on EMP501, confirm that the payroll system or payroll file has a complete record for the period.
Check:
- active employees
- terminated employees
- directors or other special payroll cases
- taxable earnings
- PAYE
- UIF
- SDL where applicable
- allowances, benefits, reimbursements, and deductions
- ETI where relevant
This step is about completeness. A reconciliation can only be reliable if every person paid in the period is visible.
2. Compare EMP201 declarations to payroll support
EMP501 depends heavily on the monthly EMP201 trail. Each month should have a declaration, payment record, payroll support, and explanation for any difference.
Review each period and ask:
- does the EMP201 agree to the payroll statutory report
- does the payment agree to the declaration
- was any correction made after submission
- is there an unresolved difference carried forward
This is the point where monthly discipline pays off. If each month was saved properly, reconciliation becomes a review. If not, the employer has to reconstruct the year from separate reports, bank payments, and old correspondence.
3. Check certificate data before submission
Employees rely on IRP5/IT3(a) certificates for their own tax obligations. That means certificate information should be checked before the submission is under deadline pressure.
Review:
- identity numbers
- tax numbers where available
- names and initials
- employment start and termination dates
- income codes
- deduction codes
- PAYE values
- UIF and SDL values where relevant
- benefit and allowance treatment
The goal is to catch certificate problems while there is still time to correct source information.
Requirements Table
| Requirement | Why it matters | Owner |
|---|---|---|
| Payroll year-to-date report | Defines the employee and earnings history | Payroll |
| EMP201 history | Shows monthly declarations submitted to SARS | Payroll or tax adviser |
| SARS payment history | Confirms what was paid and allocated | Finance |
| Certificate preview | Tests IRP5/IT3(a) values before final submission | Payroll |
| Difference log | Keeps corrections visible instead of hidden in emails | Payroll and finance |
This table should be prepared before the final filing review starts.
Numbered Checklist
- Export the payroll year-to-date record and confirm all employees paid in the period are included.
- Compare each EMP201 declaration to payroll support and SARS payment history.
- Review IRP5/IT3(a) certificate data for employee detail and code accuracy.
- Document ETI, corrections, prior-period changes, and certificate cancellations where relevant.
- Submit only once the declaration, certificates, payments, and difference log can be explained together.
4. Separate timing differences from errors
Not every difference means the payroll is wrong. Some differences may be timing items, payment allocation issues, or corrections made after a monthly declaration. The problem appears when those items are not labelled.
A useful difference log should show:
- the month affected
- the employee or liability affected
- whether the issue is timing, payment, payroll, certificate, or correction related
- what action was taken
- who approved the treatment
This turns reconciliation from a memory exercise into a controlled review.
5. Review ETI and corrections carefully
ETI and corrections deserve separate attention because they can affect the employer liability and reconciliation outcome. If the business claimed ETI during the period, the supporting file should show which employees, periods, and values were used. If a prior EMP201 was corrected, the reconciliation file should show why and where the correction is reflected.
Do not bury these items inside a general payroll summary. They are exactly the items that often explain why the EMP501 does not agree on the first pass.
6. Preserve the submitted file and certificates
Once the reconciliation is submitted, the employer should keep the submission confirmation, certificate file, payroll support, payment support, and difference log together. SARS guidance on employer reconciliation refers to keeping the relevant declarations, certificates, returns, and supporting documentation for audit purposes.
That record also helps the business later when an employee asks for a certificate, when a tax clearance issue appears, or when the next reconciliation period starts with opening differences.
7. Manager takeaway
EMP501 and IRP5 reconciliation should not feel like rebuilding payroll history. It should feel like proving the history that was already maintained monthly.
That standard depends on routine discipline: clean employee records, monthly EMP201 support, payment proof, payroll journals, and a visible correction log. If those records exist, filing season is manageable. If they do not, the reconciliation becomes a deadline-driven cleanup project.
Related Resources
- EMP201 Submission Checklist for the monthly declaration trail that feeds reconciliation
- Payroll Setup Checklist South Africa for cleaner employer setup before payroll starts
- Payroll Month-End Checklist for the accounting close controls behind payroll