Changing payroll providers securely

Changing payroll providers requires a controlled transfer of employee data, year-to-date figures, reporting history and upcoming deadlines. Agree which provider processes the final old payroll and the first new one, with explicit responsibility for corrections.

Validate imported totals and identifiers before the next live submission. Transfer sensitive files securely and revoke obsolete access only after the handover is complete.

Define the first payroll under the new provider

Agree the final pay period handled by the outgoing provider and the first one handled by the incoming team. Include off-cycle payments, corrections and year-end tasks in that decision. A contract end date does not necessarily identify who will process a bonus paid later or amend an earlier submission. Put the responsibility split in writing and name the employer's approver for the transition.

The employer still needs accurate payroll calculations, reporting and records throughout the change. The ordinary payroll duties continue even while systems and advisers are being replaced. Plan the transfer around the real payday and reporting timetable rather than choosing a migration date solely because it is convenient for software access. The new provider needs both current employee data and the history necessary to continue the year correctly. ^[1]

Transfer a complete but proportionate dataset

List the required employee details, year-to-date totals, tax codes, National Insurance categories, director information, statutory-pay records and recurring deductions. Include relevant benefits and pension settings and the accepted submission history. Agree the file format and secure transfer method before exporting. A database dump may contain more sensitive information than the provider needs while still omitting a crucial working paper held outside the system.

Keep an inventory of what was supplied, the period it covers and any known limitation. Record outstanding employee queries, corrections and notices received after the last processed payroll. The incoming team should not discover those matters only when a worker complains about the first new payslip. Use a concise issue log so the information is actionable rather than buried in a long email chain with conflicting attachments.

Preserve employment continuity and cumulative figures

Map employee identifiers carefully between the systems and follow the supported process for any change. Compare imported year-to-date amounts with the final outgoing reports at employee level, not only as a workforce total. Two offsetting errors can leave the overall total correct while individual records are wrong. Check starters and leavers separately, including any record expected to receive a payment after departure.

Review statutory-pay balances, pension membership dates and deduction balances that must continue across the change. These may not be captured in a basic pay-and-tax export. Ask each provider to explain which fields transfer automatically and which require a reviewed manual setup. Keep the source evidence for those manual entries so they can be checked without returning to the outgoing team for every later query.

Compare the first calculation before submission

Run an internal comparison using the agreed inputs for the first new payroll. Investigate differences in gross pay, deductions, net pay and employer costs, distinguishing expected configuration changes from errors. Do not submit duplicate live reports simply to test whether the new system works. The employer should approve the reconciled calculation and know which provider will make the single intended submission for the period.

Confirm the payment-file process and employee payslip delivery. A correct payroll can still fail operationally if the bank file uses old details or staff cannot access the new portal. Check a proportionate sample and the overall control totals before release. Keep the approval, submission acknowledgement and payment evidence together so the first run has a clear completion record rather than several disconnected assurances from different suppliers.

Close old access and retain the archive

After the agreed handover work is complete, remove permissions that are no longer required and confirm any continuing access needed for specific corrections. Review connected applications and shared folders as well as the main payroll account. Retain the required historical records in a form the employer can retrieve. Terminating the old subscription should not make a prior tax year's calculations or employee documents inaccessible.

Use Payroll data protection and access controls for payroll data-access controls and Payroll administration to discuss a provider transition. State the next payday, current software, employee count and whether the change is midyear. A useful transition scope identifies the data transfer, reconciliation, first submission and historic correction ownership, with enough time to resolve gaps before employees depend on the new process.

Hold a brief review after the first successful run and close any remaining transition issues explicitly. If an item still depends on the former provider, give it a named owner and date. This prevents temporary handover arrangements from becoming permanent uncertainty about who is responsible for an employee record or unresolved HMRC balance.

Illustrative scenario

An employer changes provider midyear. Both teams reconcile cumulative figures and run a comparison of the next payroll so a duplicate employment record is detected before submission.

Preparation checklist

• Agree the cutover payroll
• Transfer cumulative figures
• Validate identifiers
• Review access and correction ownership