Why does the EMP501 reconciliation not match the EMP201 amounts submitted?

Reconcile distinct records rather than one grand total

The SARS reconciliation guidance identifies monthly declarations, payments and employee tax certificates as the elements that must reconcile. The payroll records support those amounts, but they are not automatically identical to every figure already submitted or allocated at SARS.

Begin by identifying the employer and reconciliation period. An interim reconciliation and an annual reconciliation cover different periods. A correct full-year payroll total will not match a six-month declaration comparison, and a company’s accounting year-end should not be substituted for the payroll reconciliation period.

Keep PAYE, UIF and SDL distinct, with ETI considered where applicable. A combined bank payment may settle several components, while interest or penalties may appear separately on the account. Comparing only the total cash leaving the bank with certificate tax totals can hide the actual source of the difference.

Use the pattern of the difference to choose the next check

The table identifies enquiries, not automatic corrections. Several issues can exist together, and one total may conceal an overstatement in one month and an understatement in another.

Build a monthly reconciliation schedule

Create a row for each month in the relevant period and separate columns for payroll liabilities, submitted declarations and payments reflected on the account. Add the difference and an explanation reference. Keep source documents available for each row.

Use the submitted EMP201 versions, not only draft calculations saved by payroll staff. Where a return was corrected, identify the current version and preserve the earlier one. A working paper prepared before a bonus run may not explain the final declared liability.

The SARS employer-account guidance describes the statement and account-management tools. Reconcile payments to the account allocation as well as to the bank. A receipt proves a payment event; the statement helps show where SARS recorded it.

Do not net unexplained differences across tax types to make the final row zero. A PAYE overpayment and a UIF shortfall require their own analysis. Record any correction or allocation action needed and verify the result afterwards.

Check employee certificates against the approved payroll

Prepare employee-level totals for the period and compare them with the certificate information being submitted. Check identities, employment dates, certificate periods, remuneration codes and deductions relevant to the actual employee. A matching overall amount can still contain errors affecting individual employees.

Include employees who left during the period and payments processed outside the regular salary run. Review reversals and reissues so the same remuneration is not included twice. If an employee moved between payroll systems, reconcile the history across both systems before generating the final certificate set.

The SARS reconciliation process guide explains the link between certificates and the reconciliation. The information can affect employees’ own tax returns, so correcting the employer’s totals should include checking the resulting employee records.

Keep genuine separate certificates distinguishable from duplicates. Multiple employment periods or other legitimate circumstances may require a specific treatment. Do not delete a certificate solely because the employee’s name appears more than once.

Separate payment problems from calculation problems

If the declared liability is correct but the account does not show the expected payment, inspect the payment reference, tax period, bank proof and allocation. Ask whether money is unallocated, allocated elsewhere or not yet reflected. Changing a correct liability does not fix a payment posted to the wrong place.

Exclude penalty and interest payments from a comparison intended to reconcile the payroll tax payments specified by SARS. Keep those charges visible in the wider account review. Otherwise a payment towards interest may appear to be an unexplained excess in the payroll reconciliation.

Where ETI applies, trace the amounts through the payroll calculation and declarations. Do not treat ETI as an arbitrary balancing entry. Eligibility, calculated amounts, utilisation and any carry-forward position need supported records. If those questions are unresolved, identify them separately before approving the reconciliation.

Use the correction route appropriate to the submission stage

The SARS declaration guidance distinguishes corrections before and after an EMP501 has been submitted. Before reconciliation, an EMP201 error can be addressed through the applicable request-for-correction process. After the EMP501 submission, the correction is handled through the EMP501 process rather than simply editing the EMP201.

Check the actual submission status and channel before taking action. A locally saved reconciliation is different from one transmitted and accepted. Preserve the original submission and official response so the next step is based on what SARS received.

If SARS has assessed or audited the reconciliation, review the notice and applicable procedure with the adviser. Do not assume that a normal correction button is the right response to every formal outcome. Identify the issue, period and requested correction clearly.

Which totals should I reconcile before approving an EMP501?

Approve the reconciliation only after reviewing a supported comparison of the monthly liabilities, actual relevant payments and employee certificate totals for the correct period. Obtain separate PAYE, UIF and SDL schedules and the ETI explanation where applicable. The approver should be able to trace material differences to evidence.

Check gross remuneration and other certificate information against the approved payroll, not merely the tax totals. Confirm that leavers, off-cycle payments, bonuses, reversals and migration balances are included appropriately. Ask for the employee count and certificate count to be explained if they differ, without assuming they must always be identical.

Review outstanding account issues and correction references. A schedule marked “to be fixed” is not proof that the correction was submitted or reflected. Distinguish a reconciled amount from an unresolved allocation query and record the decision about any remaining issue.

Finally, check the employer reference, period, submission channel and final file version. Preserve the approval and the schedule reviewed. If the file changes afterwards, identify what changed and whether approval must be refreshed rather than treating an earlier sign-off as permission for any later version.

A fictional difference that is not a missing payment

A fictional employer’s monthly declarations agree with its bank payments, but its employee certificates include a bonus adjustment processed after the original payroll report. The reconciliation shows a difference even though no payment appears missing from the bank.

The review must establish whether the adjustment is correct, which period it affects and what declarations or payments need correction. Simply reducing the certificate total to match the old EMP201 figures would hide the issue and could leave the employee’s record wrong.

The example does not calculate the tax outcome. It shows why the first task is to establish the correct payroll liability and supporting records, then bring the declarations, payments and certificates into a supported reconciliation.

Check the official outcome after submitting

1. Save the approved reconciliation and certificate set.
2. Retain the submission acknowledgement and official processing response.
3. Resolve validation errors using their exact descriptions.
4. Check the employer account and employee records affected by corrections.
5. Keep unresolved items on a dated follow-up list.

For Vatco’s EMP201 and EMP501 support, provide the monthly schedule, payroll reports, submitted declarations and account statement. Include the actual error message and submission history. A useful review explains the difference and the action needed; it does not promise that uploading a file guarantees acceptance.