Home/Insights/Payroll cut-over

Payroll

Payroll cut-over: parallel runs and getting the final mile right

By Zené Olivier / Alexandra Wagener · Zanani People Solutions, Cape Town

6 min read

Nothing breaks trust in a new HR system faster than an inaccurate payslip. The final mile is where you protect it.

Plan for at least two parallel payroll runs before go-live, and three if your payroll is complex. Each run should have a clear job: find setup errors, find data errors, then prove it is stable. Agree in writing what "pass" means before the first run. Projects fail in the final mile when testing gets squeezed, cut-over is overcomplicated and people are not ready for the first live payday.

In our view, payroll is where employees decide whether to trust the new system. Get the first payslip right, and the rest of the rollout gets easier.

What a parallel run is

A parallel run means you run the same payroll in your old system and your new system, then compare the results. You keep paying people from the old system until the new one matches.

How many parallel runs?

One run is rarely enough. HR Blizz, a payroll provider, puts it bluntly: "One cycle is not a parallel run." It quotes IRIS Software Group's guidance that one cycle gets you started, but two or three give you accurate data (HR Blizz, The payroll parallel run playbook).

Give each run a job:

  • Run 1: find setup errors. Wrong rates, wrong tax treatment, pay items mapped to the wrong place. Expect it to be messy.
  • Run 2: find data errors. Include the hard cases on purpose: a new starter mid-month, a leaver with final pay, a backdated increase, unpaid leave, a bonus.
  • Run 3: prove it is stable. No new changes except agreed fixes. The differences should be small and explained.

If run three finds new kinds of errors, you are not ready. Plan a fourth.

Compare more than net pay

Net pay can match while the details are wrong. Two errors can cancel each other out. Check, in this order:

  1. Gross pay, item by item.
  2. Taxable income.
  3. PAYE, UIF and SDL.
  4. Other deductions, such as medical aid, pension or provident fund.
  5. Employer contributions.
  6. Net pay.
  7. The bank file total and number of payments.
  8. The journal to finance, by cost centre.

Invite finance to the last two. They are often skipped.

South African points to check

  • PAYE, UIF and SDL must match exactly. No rounding allowance on statutory amounts.
  • EMP201. Check that the monthly return from the new system matches what you would have submitted.
  • Mid-year cut-over. The South African tax year starts on 1 March. If you switch at any other time, the year-to-date figures for every employee must move across correctly. Otherwise IRP5 certificates and the EMP501 reconciliation will not balance.
  • Leave balances. Check that leave days carry over correctly.
  • Payslips. Make sure employees can read the new layout, and know where to find it.
"Systems don't change organisations. People do." Zanani People Solutions

Why projects fail in the final mile

In a South African Workday rollout, the implementation partner said the biggest pitfalls, and the most stressful phases, usually come during data migration and cut-over. He added that cut-over should not be about optimising. The client team said they overcomplicated cut-over, validation and data migration (CHRO South Africa, Mastering Workday implementation). The same session advised planning enough time for testing.

The common final-mile traps:

  • Testing gets squeezed. Earlier delays eat into test time, but the go-live date remains the same.
  • Late changes. New features are added during cut-over, so nothing is stable.
  • No written "pass". Without agreed criteria, "good enough" keeps moving.
  • One person signs off. Payroll, HR, and Finance should each sign for their part.
  • Employees not prepared. People see a new payslip with no warning, and the queries pour in.

Write down "pass" before the first run

Before the first run, agree in writing what constitutes as a pass. For example:

  • Statutory amounts match exactly.
  • Every other difference is explained and accepted by a named person.
  • The bank file and finance journal match.
  • Payroll, HR, and Finance have each signed off.

HR Blizz advises writing this down before any comparison exists. Once you see the results, the bar tends to drop.

Prepare people for the first payday

  • Tell employees that their payslip will look different, and show them an example.
  • Brief managers and supervisors, so they can answer questions.
  • Have extra payroll help on hand for the first pay run.
  • Explain where to send queries, and how fast they will be answered.

An example

Picture a payroll manager at a mining contractor. Her first parallel run matched on net pay, so the team wanted to go live.

She checked UIF line by line and found a setup error that net pay had hidden. They ran a third cycle, fixed it and went live a month later. Not one employee was paid wrong.

Try this on Monday

Write your "pass" on one page. List what must match exactly, what differences you can accept and who signs for each part. Send it to payroll, HR, and Finance for comment before any parallel run starts.

How Zanani helps

Zanani is an HR technology adoption partner and HR advisory. We help you through the final mile, so the first live payday builds trust, not doubt. Here is what that looks like for you:

  • A calm cut-over. Clear roles, clear criteria and enough time to test.
  • Employees know what is coming. Payslip changes are explained before payday.
  • Managers can answer. Supervisors have guides for common questions.
  • Confidence to switch. Leaders see the evidence before they sign.

We work directly with organisations, and we also work with HR technology providers. Every organisation is different, so let's talk about how we do it.

FAQ

How many parallel payroll runs should we do before go-live?

At least two, and three if your payroll is complex. Give each run a job: find setup errors, find data errors, then prove it is stable.

Is it enough if net pay matches?

No. Errors can cancel out. Check gross pay item by item, PAYE, UIF, SDL, deductions, employer contributions, the bank file and the finance journal.

Why do HR system projects fail in the final mile?

Testing gets squeezed, changes are added late, nobody agreed what "pass" means and employees are not prepared for the first new payslip.

Can we switch payroll in the middle of the tax year?

Yes, but every employee's year-to-date figures must move across correctly, or IRP5s and the EMP501 reconciliation will not balance.

Who should sign off a payroll cut-over?

Payroll, HR, and Finance should each sign for their own part, against criteria agreed before the first parallel run.

Getting ready for payroll cut-over? Email info@zanani.co.za or see what we do. We would love to talk.

FAQ: How do we support your digital journey?