Payroll software: what it must do before anything else

Payroll is the one system where a mistake is personal. A late or wrong payment is not an inconvenience, it is somebody's rent, and the trust cost is out of all proportion to the size of the error.

This article covers what payroll software has to do before any feature comparison: the HMRC reporting obligation, the records you must keep, the joins that cause most of the trouble, what changes for small employers, and the questions to ask a provider. New Dynamics does not sell payroll, so this is general guidance and names no products. It describes the United Kingdom position and is general information rather than tax or legal advice.

Pay decisions land better when the reasoning behind them is visible. See how New Dynamics performance reviews keep the evidence for a pay conversation in one place.

If the pay conversation itself is the problem rather than the processing, our post on performance reviews and pay covers the link honestly.

The non-negotiable job

Government guidance is specific about what payroll software is for: "recording your employees' details, working out your employees' pay and deductions, reporting payroll information to HMRC", and it must be able to "report PAYE information online", including the Full Payment Submission and, where relevant, the Employer Payment Summary.

Two practical notes from the same guidance. You can choose from HMRC-recognised payroll software, and HMRC "cannot recommend one software product or service over another and is not responsible for any problems you have with software that you've bought". Recognition means it can do the submissions, not that it suits you.

So the first question for any product is not about the interface. It is: show me a Full Payment Submission going out, and show me what happens when one is rejected.

The records, and how long they live

Payroll records are evidence. The guidance on the minimum wage is direct: "It's the employer's responsibility to keep records proving that they are paying the minimum wage", usually through payroll records showing total pay and total hours worked, and records created on or after 1 April 2021 must be kept for at least six years.

That has three consequences for a purchase:

• Retention has to be configurable to six years or more, including for leavers.
• Hours have to arrive in a form you can evidence, which is why our post on time and attendance software matters to this decision.
• Export must produce something readable without the vendor, because the obligation outlives most contracts.

The joins are where it goes wrong

Payroll calculations are a solved problem. The failures almost always happen at the boundaries.

1. Starters and leavers. A person added in HR but not in payroll gets paid late. A leaver not removed gets paid once more, which is awkward to recover.
2. Hours. Rounding rules, unsocial hours, overtime rates and corrections. Decide where the truth lives and make the other system read it.
3. Absence. Statutory payments, sickness, parental leave and unpaid days, which have their own rules and timing.
4. Pensions. Auto-enrolment assessments, opt-outs and contribution changes.
5. Expenses and benefits. Anything reportable, including the recognition awards covered in our post on employee recognition software.

Ask each provider to run a period containing a mid-month starter, a leaver, an overtime correction and one statutory payment. That single test tells you more than any feature grid.

What changes for small employers

• Payroll is monthly and unforgiving, so reliability matters more than configurability.
• One person usually does it, which makes documentation and cover a real risk rather than a theoretical one.
• An accountant or bureau may be the better answer than software you run yourself, and the comparison should be total time and risk rather than licence fee.
• Integration with whatever records hours matters more than reporting depth.

If payroll currently takes a day a month and causes anxiety, the thing to buy may be a service rather than a system.

Questions for the demo

1. Show me a Full Payment Submission being sent, and a rejection being corrected.
2. Run a messy period: mid-month starter, leaver, overtime correction, one statutory payment.
3. Show me the audit trail for a changed pay element, including who approved it.
4. Show me retention settings and what a leaver's record looks like after six years.
5. How does it receive hours, and what happens when the time system corrects a past period?
6. What is the support model on pay day, with a named response time?
7. What is the export, and can we read it without you?

What usually goes wrong

• Buying on price for a system that cannot be left. Migration mid-tax-year is painful, so exit terms matter at purchase.
• Manual re-keying between HR and payroll, which is where most errors live.
• No documented process, so one person's absence becomes a crisis.
• Retention set to the default, which is usually too short for the obligation.
• Testing with clean data, which hides exactly the cases that go wrong.
• Treating pay queries as a payroll problem rather than a communication one. An explained deduction is a question; an unexplained one is a grievance.

Frequently asked questions

What does payroll software have to do in the UK?

It must record employee details, work out pay and deductions, and report PAYE information to HMRC online, including the Full Payment Submission and the Employer Payment Summary where relevant. Anything else, such as self-service payslips or analytics, is useful but secondary.

What is HMRC-recognised payroll software?

Software that HMRC has recognised as able to make the required submissions. HMRC is explicit that it cannot recommend one product over another and is not responsible for problems with software you have bought, so recognition is a minimum qualification rather than an endorsement.

How long do you have to keep payroll records?

Keep records proving minimum wage compliance, and for records created on or after 1 April 2021 that means at least six years. Set the retention period in the software deliberately, including for leavers, rather than accepting a shorter default.

Should payroll and HR be one system?

It helps when starters, leavers and contract changes flow automatically, because manual re-keying is where most payroll errors begin. A single system is not essential, but a reliable, tested join is. Decide which system is the source of truth for each field.

Do small businesses need payroll software?

They need a compliant way to run payroll, which may be software or a bureau. Compare total time and risk rather than licence cost: if payroll takes a day a month and only one person understands it, a service may be the better purchase.

What should you test in a payroll demo?

A messy period: a mid-month starter, a leaver, an overtime correction and a statutory payment, plus a submission being rejected and corrected. Clean demonstration data hides precisely the cases that cause real-world errors.

Your next step: run the messy period

1. Write down your last three payroll errors and where each originated. Most will be at a join.
2. Check your retention setting against the six-year obligation.
3. Ask any provider to run the messy period test live, with your own scenarios.
4. Document the payroll process well enough for someone else to run it next month.

For the wider duties around employee data, read and download our employee data protection guide. The guide is free to read, and the PDF uses our short download form.

Want pay conversations supported by evidence rather than recollection? Book a New Dynamics demo and bring your review and pay timeline. You can also email contact@new-dynamics.com.