Payroll services
Payroll system setup and payroll migration
Most payroll migrations fail on data, not software. Patuza implements and migrates payrolls with a fixed method: configure, migrate, run in parallel, validate, then go live — with year-to-date figures proven before the first live cycle.
Implementation and configuration
- Company, pay point, department and cost centre structures
- Earnings, deduction, benefit and employer contribution codes with correct tax treatment
- Leave setup: leave types, cycles, accrual rules and opening balances
- Bargaining council, sectoral determination and industry-specific rules where applicable
- General ledger mapping and banking file formats
Payroll data migration
Employee master data, package structures, benefit elections, leave balances and year-to-date tax values are migrated and reconciled to the source system. Year-to-date accuracy matters most: if it is wrong, every remaining EMP201 and the tax certificates at year-end will be wrong too.
Parallel runs and validation
A parallel cycle processes the same period in both systems and compares results employee by employee. Differences are explained before go-live rather than discovered by employees on a payslip.
Historical payroll data
Historical registers, payslips and tax certificates are retained in an accessible form for the statutory retention period, so a mid-year change of system does not break your EMP501 reconciliation or an audit trail.
Go-live and stabilisation
The first live cycle is run with additional review, and the following two cycles are monitored for exceptions. Only then is the payroll treated as business as usual.
Frequently asked questions
When is the best time to migrate a payroll?
The start of a tax year is cleanest because year-to-date values start at zero. Mid-year migrations are entirely workable, but the year-to-date migration and reconciliation must be done carefully.
How long does a payroll migration take?
For a straightforward single-entity payroll, configuration, migration and a parallel run typically span a few weeks. Multi-entity groups, bargaining council environments and complex benefits take longer.
What is a parallel payroll run?
It is processing the same pay period in the old and new systems and comparing every employee's gross, deductions and net pay. It is the only reliable proof that configuration and migrated data are correct.
What happens to our historical payroll records?
They are retained and remain accessible for the statutory retention period, including registers, payslips and tax certificates from the previous system.
Patuza handles configuration, data migration, parallel runs and go-live so employees never feel the change.
Book a consultationRelated services
- Payroll processing →
Monthly and weekly payroll processing, calculations, payslips and statutory deductions.
- Payroll advisory →
Payroll consulting on process, controls, systems, compliance risk and payroll optimisation.
- Payroll audits →
Independent payroll audits covering data integrity, statutory accuracy, controls and risk.
Related topics
Related insights
- Migrating payroll systems →
A migration method that protects year-to-date data and employee trust.
- Payroll reconciliation explained →
What payroll reconciliation means, what it proves and how to run it every month.