Payroll problems to test software against: migration, bureau exceptions, pension files and input checks

The payroll problems most worth testing are rarely about the calculator. They appear where an employer or bureau repeatedly loses time, lacks evidence or moves data by hand. This guide lists five such problems and the check that shows whether a product handles each one. Products named below are examples of common routes, not verified findings, so test any product you are considering the same way. The demand signals article covers why these pressures recur.

What to take away

Safer payroll migration

Changing systems creates a concentrated problem: opening figures, year-to-date values, employee identifiers and submission history must remain coherent. HMRC's payroll software guidance warns that changed payroll IDs can create duplicate records or an incorrect PAYE bill when the change indicator is not handled correctly.

A sound migration test combines a structured import, validation, a parallel-run comparison and a signed reconciliation report. If a product or provider cannot show these, the migration problem is not solved for you.

A move from Sage 50 Payroll to Xero Payroll has to carry fields such as payroll ID, works number, NI number, tax code, year-to-date pay and tax, starter and leaver dates, and pensionable pay. Validation can reject a file when the payroll ID is missing, an NI number fails HMRC format checks, or year-to-date tax does not reconcile.

Expect pricing to follow employer complexity and data condition, not rows imported. Define which historical records move and who approves the cutover.

Bureau exception management

Payroll bureaux repeat similar work for many clients, yet exceptions arrive in different forms and at different times. A bureau running BrightPay for some clients and Xero Payroll for others can collect hours through a portal, approve them in one queue, submit an FPS batch and keep an evidence trail.

The time saved depends on client count, exception rate and approval delays, measured against the bureau's current email chasing. Test it through time saved per completed client payroll and fewer unresolved exceptions. Employer count alone is a weak measure because one untidy client can consume more work than several stable ones.

Pension data exchange and checking

The Pensions Regulator's guidance on payroll software for automatic enrolment identifies recurring tasks such as assessing staff, calculating contributions and generating pension-provider data. A good product validates files, explains rejections or reconciles amounts between payroll and pension records. Named schemes include NEST, The People's Pension, NOW: Pensions and Smart Pension, often with CSV contribution uploads.

Pass criteria: the scheme accepts the file first time, and the amounts match the payroll records. Compatibility must be proved for named schemes, file versions and tax-relief methods. Avoid claiming comprehensive pension compliance from a narrow export function. Validation should check employee NI number, pensionable pay, contribution rate, scheme reference and tax-relief method before a file is accepted.

Input quality and approval controls

Late starters, incomplete bank details, duplicate identifiers and unapproved variable pay create avoidable correction work. An intake layer can apply validation, deadlines and role-based approval before calculation begins. Field-level checks can reject a missing start date, an invalid bank sort code, a duplicate NI number or a variable pay line without an approver.

The measure is not form completion. It is fewer corrections, shorter review time or clearer responsibility in a live payroll cycle.

Integrations with an auditable boundary

Employers may want approved hours, leave, benefits, accounting entries and payment instructions to pass between HR and payroll systems. For example, approved hours from Deputy or Rotaready can pass into Sage 50 Payroll or Xero Payroll, and BACS files carry payment instructions.

Integration can remove rekeying, but it can also reproduce a bad source value instantly. A useful connector preserves source, timestamp, approver, transformation and error status.

Start with one well-defined data exchange and publish what the integration does not control, so the buyer knows which errors the connector will catch and which it will pass on.

Security and operational continuity

Payroll contains personal and financial information and has a date-sensitive output. The ICO's employment information hub directs organisations to current guidance on keeping worker records under the UK GDPR and Data Protection Act 2018.

A secure product should offer tightly controlled access, approval logs, secure document delivery, tested recovery or an emergency run procedure. Buyers need evidence such as restoration tests and incident routes, not an unexplained "secure" label.

The best product for you solves your most painful part of payroll while making its responsibility boundary unambiguous.

How to run the tests

Run the tests with the people who do the work, whether the payroll is self-serve, run through a bureau or bought as a managed service. The same apparent problem can have a different owner and remedy in each model. Ask the user to show the last completed workflow and a real exception, with personal details removed or protected.

Then run a deliberately narrow trial. Measure elapsed time, human interventions, correction rate and approval over several payroll cycles. A product earns trust when the same fault stops recurring, not when a demonstration looks smooth.

Pricing to check

Ask each supplier what drives the price: employees, pay frequencies, pension schemes, integrations, security review and support hours. Budget a narrow pilot as a fixed fee covering set-up, import and one payroll cycle. Bureau work is often priced per completed client payroll or per active employee, with a floor for support.

Public pricing for products such as BrightPay, Xero Payroll, QuickBooks Payroll and Sage 50 Payroll usually varies by employee count or payslip volume, so check current vendor pages. HMRC Basic PAYE Tools is free at the point of use. Treat any range as typical and confirm it with quotes.

Before you buy

Common questions

What evidence do buyers need on security and continuity?

Restoration tests and incident routes, not an unexplained secure label. The ICO points employers to its current guidance on worker records under the UK GDPR and the Data Protection Act 2018.