Loading
Do not run yet. Tax codes and bank details are the two that produce a payment to the wrong person or the wrong amount.
Weighted towards the errors that reach a person’s bank account. A stale reporting line is annoying; a wrong tax code is a letter from HMRC.
The order to configure payroll in, and what to verify before a live run: entities and registrations, calendars, components, people, then opening balances.
It is ordered deliberately. Entering people before components exist is the most common cause of a bad first run.
Work through it in order and do not skip the parallel runs. Two runs reconciled line by line against your previous system, not totals — totals can match while two errors cancel out.
Tick each edge case explicitly rather than assuming the standard case covers it.
It will not verify your statutory settings against the current rules. Those change, and checking them is the responsibility of whoever runs payroll.
It also cannot tell you when to go live, beyond avoiding a month with a statutory change.
A mid-month joiner, a leaver, somebody on unpaid leave, anybody with a loan, an advance or an attachment of earnings. These are where salary structures break, and they will not appear in a test with three tidy employees.
Also check somebody with a mid-year change of pattern, which combines several of the above.
Two minimum, reconciled line by line.
A quiet month, ideally at the start of a tax year.
No. That stays with whoever runs payroll.
Half an hour on your own figures, and an honest answer about the parts Treepie does not improve.