Which employee records should I retain when correcting UIF contribution history?

Define the correction before collecting the file

Write a short case summary identifying the employer, employee, affected periods and suspected error. State whether the issue concerns identity, employment dates, earnings, contributor status, declarations or payments. Several issues may exist together, but each needs its own supported conclusion. A general instruction to fix UIF does not give a reviewer enough information.

Record how the problem was discovered and who is coordinating the response. Keep a list of outstanding evidence rather than filling gaps from memory. If an employee’s claim is affected, note that fact without promising a particular benefit result. The employer’s task is to correct and substantiate its records; the official claim decision remains a separate matter.

Preserve identity and employment evidence

Keep the identity details used for the original record and the documents supporting any correction. Retain the employment agreement, commencement evidence and relevant changes to the employment relationship. Where a person moved between legal employers, identify the entity and dates for each period instead of treating the trading name as the employer.

For a termination-related correction, retain the records supporting the actual date and reason. Do not replace a resignation, dismissal or contract-ending reason merely to create a different UIF outcome. If the facts are disputed, obtain appropriate employment advice and keep the dispute visible. The declaration should follow the supported position rather than an informal agreement to use a convenient code.

Reconstruct remuneration by the affected period

Collect the original payroll reports, payslips, time or attendance records and approved pay adjustments. Explain the remuneration components and the UIF treatment used. A bank transfer can support that money was paid, but it may represent net wages, an advance or several items and does not by itself establish the contribution base.

Use the rules and ceiling applicable to the historical period. Do not recalculate several years using today’s settings without checking changes. Show the original calculation, corrected calculation and difference for each period. If earnings data is incomplete, identify the missing evidence and obtain it where possible instead of creating a precise-looking spreadsheet unsupported by the employment and payment records.

Retain what was actually declared

Save the original declaration files or forms, the period covered, submission references and processing feedback. A report generated today after editing payroll may not reproduce what was sent originally. Keep that distinction clear. The correction reviewer needs to see how the inaccurate record arose and what information the authority received.

If another provider submitted the declarations, request the historical exports and outcomes before its access ends. Where records are unavailable, document the request and seek guidance on reconstructing the history. Do not describe a local payroll backup as proof of submission. A saved file and an official receipt answer different questions and should be labelled accordingly.

Match payments without assuming they repair the history

Keep the EMP201 or other applicable payment declaration, bank proof, payment reference and evidence of allocation to the employer account and period. Compare the amount paid with the payroll contribution totals. An employee-information omission may exist even when the money was paid correctly; a payment shortfall may also remain after the identity data is corrected.

Prepare a separate reconciliation of financial differences. Do not automatically pay the contribution again because a history screen is incomplete. Equally, do not assume a data correction clears an unpaid balance. If money was paid through the wrong route or reference, obtain guidance on the appropriate correction or allocation process using the actual payment evidence.

Organise the evidence in a review table

Use the table as an index to documents, not as a substitute for them. Restrict access to employee-specific information and avoid circulating an entire payroll file when only one person’s history is relevant.

Illustrative example: the wrong commencement month

An employee began work in March, but a payroll migration recorded April as the start month. March’s payslip and attendance record support employment during March, and the employer’s contribution reconciliation shows the amount was paid. The missing element is the employee history for that period, not necessarily an additional payment.

The correction pack should include the true commencement evidence, March payroll and payment records, the original declaration detail and the proposed corrected data. Keep the explanation of the migration error and the authority’s response. After processing, check that the history reflects the supported period. This example shows how several records work together; no single payslip proves every part of the correction.

Keep a clear approval and change log

Record the field or amount being changed, the old value, the new value, the reason and the supporting document. Identify who prepared and reviewed the change. Preserve the original version instead of overwriting the only copy. That protects the audit trail and helps answer later questions about why two versions of the record exist.

If a correction affects several employees, separate the common cause from each person’s evidence. A shared software-setting error does not mean every employee has the same financial adjustment. Review the scope and identify unaffected periods. This prevents a targeted repair from becoming a broad rewrite of valid payroll history and gives the business a defensible record of its decisions.

Check the limits on recovering employee amounts

If the review identifies an old under-deduction, do not simply take the total from the employee’s next salary. The UIF contribution rules restrict deductions and recovery of arrears, and the employer’s own share must not be shifted to the employee. Obtain advice on the lawful treatment for the periods and facts involved.

An over-deduction also requires proper handling. The SARS guide addresses refunds to employees where amounts were not due or exceeded what was due. Keep the employee calculation, payroll correction and payment evidence, and assess the employer’s separate account or refund position. Do not leave a known employee over-deduction unresolved merely because the employer’s authority-side process is still being considered.

Verify the outcome across related records

After submitting the correction, retain the receipt and any case reference, then obtain or inspect the resulting record. A logged request is not proof of completion. Compare the corrected employee history with the supported dates and amounts, and reconcile the payment account where a financial change was involved.

Check whether related payroll reports, employee certificates or employer reconciliations also need attention. Do not assume that changing one system automatically updates all others. Document the follow-through and any remaining difference. If the correction is rejected, keep the reason and respond with relevant evidence rather than repeatedly submitting an unchanged pack or making unsupported alterations to obtain acceptance.

Keep unresolved periods separate from completed corrections

A case covering several months may be processed in stages. Maintain a period list showing what was submitted, what has been confirmed and what remains unresolved. Do not close the entire case because one month now appears correctly or because a payment adjustment was posted.

Use that list when following up so the official or adviser can identify the remaining issue without rereading the whole history. Retain the dates of responses and the evidence of each completed change. This also helps a replacement payroll administrator continue the work without duplicating submissions or assuming that every period in the original request was accepted.

Retain a usable and secure final file

Apply the relevant record-retention requirements and consider outstanding audits, disputes or other circumstances that require longer retention. Do not destroy the originals simply because a routine period has passed or the employee has left. Keep an index, secure backups and access controls so the records can be retrieved without being widely exposed.

Vatco’s payroll services and UIF support can help organise the evidence and correction work. Provide the affected periods and original records at the outset. The completed file should explain the error, support the correction and show what the relevant authority actually processed, with remaining issues clearly identified.