How do I move payroll providers without losing employee year to date records?

Define the change and the legal employer

A change of payroll provider is not automatically a change of employer. Confirm that the same legal entity and employer references will continue, or identify any separate restructuring that needs advice. The migration plan must reflect the actual transaction. Treating every employee as a new starter because the software is new can lose service and tax history.

Agree the last pay period processed by the old provider and the first processed by the new provider. Include off-cycle payments, corrections and any work already in progress. A calendar date alone is insufficient if one provider is still responsible for a prior-period correction while the other is preparing the current payroll. Write down responsibility for each remaining task.

Request more than the last set of payslips

Payslips are useful but may not contain all the data needed to continue payroll or complete employer reconciliations. Obtain employee master records, employment dates, pay structures, benefits, deductions, leave balances, loan or advance balances and relevant directives or supporting instructions. Request year to date values by employee and by the applicable payroll and tax codes, together with the period history behind them.

Also obtain employer-level payroll reports, submitted declarations, payment records, reconciliation files, employee certificate information and outstanding query correspondence. Ask for both usable data exports and readable reports so the figures can be checked independently of the old software. Confirm that exported files open correctly and are complete before assuming the handover has succeeded.

Use a written handover inventory

Mark each item as received, checked or outstanding. A provider’s statement that the payroll has been transferred should not replace evidence that the employer can read and reconcile the records.

Map codes before importing balances

The two systems may use different internal descriptions for earnings, deductions and employer contributions. Map each item to the appropriate destination and applicable reporting code. A label such as allowance can conceal several different treatments. Use current SARS specifications and the actual nature of the payment, not a guess based on similar wording.

Check whether the new system expects opening year to date totals, detailed historical periods or another supported migration method. Follow the provider’s documented process and verify the result. Importing both full history and opening totals without the correct configuration can double the accumulated amounts. Keep a mapping file and the import results so later differences can be traced.

Illustrative example: totals agree but one employee is wrong

A fictional employer changes providers after several payroll periods. The old system reports total employee deductions of R60,000 for the relevant history. The new system also reports R60,000 after import, so the initial summary appears correct. A check by employee reveals that R4,000 has been allocated to the wrong person because two employee identifiers were mapped incorrectly.

The employer total alone would not reveal the error. The team compares each employee’s gross remuneration, deductions, employer contributions and relevant code totals with the source reports. It also checks employees who left earlier in the year, because they may not appear on the current active payroll list but can still be relevant to annual reporting.

These invented figures illustrate a reconciliation risk, not a tax calculation. The correction must preserve the underlying history and any existing certificate identity. The team documents the mapping error, reruns the import in the controlled test process and obtains approval before using the data for live payroll or submissions.

Reconcile payroll with declarations and payments

SARS explains that employer reconciliation brings together monthly declarations, payments and employee tax certificates. Preserve the information needed to connect those elements across the provider change. A clean new payroll system cannot by itself establish that earlier declarations or payments were correct. Record any existing differences and who will resolve them.

Check the period covered by each export and submission. A report headed year to date may use a different cutoff from the migration date or the relevant tax year. Include off-cycle runs, reversals and corrections where applicable. Do not assume that the employer’s financial year and the payroll tax reporting period are identical.

Control certificate continuity and outstanding submissions

Agree who will prepare the next employer reconciliation and manage any certificate corrections. The current SARS rules and system specifications determine the required certificate treatment. Do not issue duplicate certificates for the same payroll history simply because both providers can generate them. Preserve existing certificate references and submission status in the handover.

Likewise, avoid submitting the same declaration twice or omitting a period because each provider assumes the other is responsible. Use a task schedule showing period, return type, preparer, reviewer, submission status and payment status. If a correction to an earlier period is needed after cutover, make sure the responsible person has the data and authority to perform it.

Test the first new payroll without paying twice

Run a controlled comparison using the agreed inputs and current rules. Compare gross pay, deductions, employer costs, net pay, leave movements and year to date totals. Investigate differences by cause, including valid rule changes, rounding, configuration or data errors. The objective is an explained result, not forcing the new system to reproduce an old mistake.

A parallel calculation should not release a second salary payment or send duplicate payslips and submissions unintentionally. Control who can authorise live payments and identify which output is approved. After the first live run, reconcile the bank payment and ledger postings with the approved schedule and confirm that accumulated balances continue from the correct opening position.

Protect employee information during the transfer

Payroll data includes sensitive personal and financial information. Use an agreed secure transfer method, limit access to the migration team and verify the recipient. Avoid placing a full payroll export in an unrestricted shared folder. Keep a record of the files transferred and remove temporary access when the migration checks are complete, while preserving required employer records.

Clarify what the outgoing provider retains and how the employer can obtain historical information later. Do not cancel access before exports, reconciliations and archive retrieval have been tested. Retention and deletion decisions should follow applicable requirements and the service arrangement, including any ongoing dispute, audit or investigation. A provider change is not a reason to discard the payroll history.

Carry forward non-tax balances deliberately

Leave, staff loans, advances and recurring deductions can be lost even when taxable remuneration imports correctly. Reconcile each balance to its supporting history and confirm the effective date. An opening leave balance should distinguish the relevant categories and follow the employer’s lawful policy; copying one total into an unrelated field can change what the employee appears entitled to take.

For a staff loan or advance, retain the agreement, deductions already made and remaining balance. Check that a deduction stopped in the old system is not restarted in the new one through an outdated template. Conversely, a valid continuing deduction should not disappear merely because the employee’s master record was recreated.

Have the responsible employer reviewer approve these balances separately from the tax-code reconciliation. This makes clear that a successful import message is only a technical result. The business still needs evidence that the employee’s full payroll position has been preserved accurately.

Close the handover with an exceptions record

Approve the migration only after the key reconciliations are complete and remaining issues are documented with owners. Retain the source exports, mapping, comparison reports, approvals and first-run evidence. Schedule a follow-up review before the next major reconciliation so a hidden history problem does not remain undiscovered until filing time.

Vatco’s payroll services can help organise the transition and ongoing administration. Bring the cutover plan, source reports, current declarations and the list of unresolved items. For the related statutory reporting work, EMP201 and EMP501 submission support can help connect the payroll history with the required reconciliation process.