Write the employer scenario first, then let payroll software prove it can handle it

Choose payroll software against one documented employer workflow, not a star rating or the longest feature page. The right product must support the relevant PAYE reporting, pay patterns, pension arrangement, controls and recovery process at a sustainable total cost.

Write the scenario first

Record active employees, PAYE schemes, weekly or monthly runs, variable pay, directors, starters, leavers, statutory payments, pension providers, approvals and connected systems. State who operates payroll and who can approve a purchase.

HMRC's software selection guidance notes that products may differ in payslips, pension functions, pay periods and report types. Treat that list as a starting prompt, then add the employer's actual cases.

Confirm the reporting boundary

Check the exact product on HMRC's recognised software list. Recognition supports online PAYE reporting, but HMRC does not recommend a supplier or accept responsibility for a purchased product.

Ask which tax year and submission types the selected edition supports. Demonstrate a successful test and retain the response. Do not infer that another product from the same vendor has identical status.

Test pensions end to end

The Pensions Regulator's payroll software checklist covers assessment, contributions, tax-relief method, pension-provider data, communications, worker requests and records.

Test the tasks actually required with the named pension provider. Confirm the file or connection version, rejection handling and reconciliation. A contribution calculation alone does not establish complete compatibility.

Rehearse migration and ordinary work

Use synthetic records to test initial balances, year-to-date figures, payroll IDs, pay calendars, deductions and opening pension information. Run the old and candidate systems in parallel, investigate every difference and name the authoritative result.

Then let the intended operator complete a normal run, late input, leaver, correction and failed submission. Count human interventions and support contacts. A polished demonstration led by a salesperson does not show daily usability.

Review data, access and resilience

Document controller, processor and sub-processor roles; storage and overseas access; retention; account closure; administrator controls; audit logs; backup and recovery. Test customer separation where a bureau is involved.

Ask the supplier to show incident and service-status routes. Verify support availability against actual payroll deadlines. Review contract promises against operational evidence.

Compare full cost and exit

Calculate subscription, active-employee charges, extra runs, modules, migration, training, support and internal time. Use identical scenarios for every candidate and mark quote-only facts unknown.

Test a full export before signing. Record cancellation, renewal, transition help, deletion and any access lost at closure.

Score each requirement as essential, useful or irrelevant before viewing products. Require evidence for pass or fail and keep unresolved points visible. The final choice should explain why one product fits the defined employer better, not claim a universal winner.

Involve the people who must operate the choice

Ask the payroll operator to complete test runs, finance to inspect approvals and reconciliations, IT or security to review access and resilience, and the business owner to examine cost and change risk. Include employees with relevant access needs when testing payslips or self-service.

Record disagreements rather than averaging scores. A product that pleases the buyer but blocks the operator should not pass unnoticed.

Use acceptance and stop conditions

Set minimum evidence before the trial begins: all essential cases completed, no unexplained calculation difference, successful report acknowledgement, accepted pension exchange, restored backup and usable export. Define who can stop migration and what happens if a criterion fails.

Keep the current system authoritative through parallel testing. The deadline for the next payroll is not evidence that the candidate is ready. After several live cycles, review correction rate, operator time, support use and total cost against the decision assumptions. Reopen selection if the chosen product requires material workarounds that the original comparison did not price.