1. Home>
  2. Resources>
  3. Payroll & Reward>
Man and woman at desk with laptop

How to Choose Payroll Software: A UK Selection Guide

Knowing how to choose payroll software comes down to five things: whether it handles your compliance obligations, whether it fits your own pay rules, what it takes to integrate, what support you get when something goes wrong, and what it costs across the whole contract rather than per month. Get those right and the product almost picks itself. Most buyers start in the wrong place, comparing feature lists before they have written down what their payroll actually has to do. This guide works the other way round: define your requirements, then compare against them, then run a selection process that tells you something a sales demo cannot. If what you want is someone else to run payroll for you, choosing a payroll provider is the better read.
 

At a glance

  • Start with what your payroll has to do, not with a feature list. Pay frequencies, pay elements, statutory payments and your entity structure decide what "fit" actually means. > Map your requirements
     
  • HMRC recognition is the floor, not a differentiator. It confirms a product can file to HMRC. HMRC is explicit that it cannot recommend one product over another. > Compliance essentials
     
  • The statutory detail is where systems come apart. Scottish and Welsh taxpayers, hours on variable payslips, attachment orders, and payrolling benefits from April 2027. > Compliance essentials
     
  • Ask how legislative changes reach your system, not whether they do. Release timing, pre-April delivery, and what happens if a rate lands late. > Compliance essentials
     
  • Integration effort is the most underestimated cost of the whole project. > Integration
     
  • Compare total cost over three to five years, not the monthly fee. Implementation, migration, integration build and training usually outweigh year one licence. > Total cost
     
  • Script your demos so every vendor runs your scenarios, not theirs. > Running the selection
     

    Software you run, or a service that runs payroll for you

    Before comparing products, settle the model. The two routes look similar in a sales conversation and are very different to live with.

    With payroll software, your team runs payroll. You hold the knowledge, you make the calculations happen, you check the output and you submit to HMRC. You keep direct control over timing, corrections and how exceptions are handled, which matters if your pay rules are unusual or your deadlines are tight.

    With a managed service, a provider runs the processing for you. You still own the data going in and the decisions about pay, but the work of running the cycle sits elsewhere. Some providers offer a middle option, often called a bureau service, where they process from data you supply but you retain more of the checking.

    What does not change either way is where the obligation sits. You remain the employer, responsible for paying people correctly and for what goes to HMRC in your name. Software and services both help reduce the risk of getting it wrong, through current calculations, validation and specialist support, but accuracy still depends on the quality of the data you put in. No product or provider removes the duty.

    If you are still weighing the two models, start with in-house payroll vs outsourcing. If you have decided on a service, choosing a payroll provider covers the service questions this guide does not. For smaller employers the economics differ enough that payroll software for small businesses and payroll services for small businesses are better starting points.

    Everything that follows assumes software your own team will run.

      Start with your payroll, not the feature list

      The most common mistake in a software selection is comparing products before documenting requirements. Every vendor's feature list is designed to look complete, and lined up side by side they all do. The differences only become visible when you test them against the specifics of your own payroll, and you cannot do that until those specifics are written down.

      This is also the step that protects you later. A documented requirements list becomes your RFP, your demo script and your scoring criteria. Without it, you end up scoring vendors on how well they presented.
       

      What your payroll actually has to do

      Work through your own operation and write down what you find. Most organisations discover at least one thing they had forgotten they do.

      • Headcount, structure and growth. How many people, across how many legal entities and PAYE schemes, and where you expect to be in three years.
      • Pay frequencies and pay groups. Monthly, weekly, fortnightly, four-weekly, and who sits in each. Multiple frequencies are common and not every product handles them equally well.
      • Pay elements. Overtime at different rates, shift premia, standby and callout, allowances, commission, bonuses, expenses paid through payroll. List every one, with the rule that decides it.
      • Statutory payments. Sick, maternity, paternity, shared parental and parental bereavement pay, and how each interacts with your own enhanced schemes.
      • Salary sacrifice and benefits. Pension sacrifice, cycle schemes, cars, and anything else changing gross pay before tax.
      • Deductions you do not control. Student and postgraduate loans, attachment of earnings orders, Scottish earnings arrestments, union subscriptions.
      • Where your people are taxed. Scottish and Welsh taxpayers need the right bands, and people move mid-year.
      • Holiday pay. How you calculate it, and for which groups, since the method is not the same for everyone.
      • Data sources, approvals and reporting. What feeds payroll, who signs off and when, and what finance, auditors and pension providers need out of it.

      In practice: a 600-person housing association running monthly payroll on locally installed software found during this exercise that it was processing three pay frequencies, not one. Monthly for most staff, weekly for a small maintenance team, and an annual payment run for board members under a separate PAYE scheme. None of that was in the original brief to vendors, and two shortlisted products handled it awkwardly.
       

      Who uses the system, and what they need from it

      Payroll software is rarely used only by payroll. Each group has different needs, and ignoring one of them is how adoption problems start.

      • Payroll needs calculation accuracy, exception handling, correction routes and audit trails.
      • HR needs to make starter, leaver and change data flow in without rekeying.
      • Finance needs journals in the right shape, cost centre splits, and reporting that reconciles.
      • Line managers need to approve what they are asked to approve, quickly, usually on a phone.
      • Employees need payslips, P60s and the ability to update their own details without emailing payroll.

       

      Sorting must-have from nice-to-have

      Score every requirement before you see a single product, while you are still honest about it. Three bands work:

      1. Must have. Payroll cannot run correctly or legally without it. A product that fails here is out, whatever else it does well.
      2. Should have. A real operational benefit. A product failing several of these is a weak fit even if it clears every must-have.
      3. Nice to have. Genuinely useful, but you would not pay extra or compromise elsewhere for it.

      The discipline matters because vendors are good at making nice-to-haves look like must-haves. Fixing the bands in advance means a slick demo of something you do not need cannot quietly reorder your priorities.

        The compliance capabilities every UK payroll system needs

        Compliance is the one area where "most products handle it" is not good enough. Most products handle the common cases. The differences show up in the specifics, and the specifics are what generate corrections, penalties and unhappy employees.
         

        HMRC recognition and real time reporting

        Recognition means HMRC has tested that a product can submit PAYE information online. That is all it means. HMRC is explicit: it cannot recommend one product or service over another, and recognition says nothing about calculation accuracy, security, support or suitability. Treat it as a filter, not a finding. Every product on your longlist should be recognised, and a free recognised product is only an option for employers with fewer than 10 employees.

        What matters more is reporting in practice. A Full Payment Submission is due on or before payday unless an exception applies, and an Employer Payment Summary by the 19th of the following tax month. Late filing penalties are monthly and scale with headcount, from £100 for employers with up to nine employees to £400 for those with 250 or more, and if you run more than one PAYE scheme you can be charged for each.

        What to ask: how does the system validate a submission before it goes, what does it do with a rejection, and how are corrections and earlier year updates handled. For more on recognition itself, see HMRC-recognised payroll software.
         

        Auto-enrolment and pension output

        Automatic enrolment is not a one-off setup. Workers are assessed against the age and earnings thresholds, and anyone who is not an eligible jobholder at one assessment has to be reassessed as their pay and age change, pay reference period by pay reference period. Re-enrolment comes round every three years, with a re-declaration of compliance required whether or not anyone needs putting back in. Minimum contributions are 8% in total, with at least 3% from the employer.

        The part most buyers skip is output. Your pension provider needs a file, in its format, on its schedule. Some systems produce it natively, some use the PAPDIS standard, some expect you to build it. What to ask: which providers are already supported, and what happens when you change provider.
         

        The statutory detail that catches systems out

        This is where products diverge, and where a demo of standard monthly payroll tells you nothing.


         

        Requirement What the system has to do
        Scottish and Welsh taxpayers Apply the right bands from the S or C prefix on the tax code. Scotland has six taxed bands against three elsewhere in the UK, so this is a different band structure, not just different rates. What to ask: how is a mid-year move between Scotland and the rest of the UK handled, and what happens to the year to date position.
        Itemised payslips Where pay varies by time worked, section 8 of the Employment Rights Act 1996 requires the payslip to show hours, as a single total or split by rate (ACAS guidance covers the mixed case). What to ask: can the payslip do this without customisation.
        Payrolling benefits in kind From 6 April 2027, company cars, car fuel, vans, van fuel and employer-provided medical benefit must be reported through payroll in real time, with most remaining benefits following in April 2028. Loans and living accommodation stay on existing end-of-year reporting. What to ask: what is on the roadmap, and when will it land.
        Attachment of earnings and arrestments Priority orders carry a shortfall forward to the next payday, non-priority orders do not, and both are limited by the protected earnings rate given in the order. Scotland operates earnings arrestments instead, with their own thresholds under the 2024 regulations. What to ask: does the system apply priority order automatically where someone has more than one.
        Student and postgraduate loans Each plan type has its own threshold and rate, with Plan 5 introduced from April 2026. Only one student loan plan operates at a time, but a postgraduate loan can run alongside it, and both are started and stopped by HMRC notices. What to ask: are start and stop notices applied automatically from the HMRC feed.
        Multiple PAYE schemes Running more than one requires a formal election to HMRC, and each is then treated as a separate employer for most purposes. What to ask: can one user see across all schemes, and how are people moved between them mid-year.
        Retrospective pay Backdated awards, late starters and corrected hours all need recalculating across closed periods, automatically rather than by hand.
        Holiday pay The 12.07% accrual method applies only to irregular hours and part-year workers, and only for leave years starting on or after 1 April 2024. For everyone else, nothing changed. If you have both groups, your system needs both methods. What to ask: can they run side by side without manual intervention.
        Year end The final submission is due on or before the last payday of the year, with P60s to employees by 31 May and expenses and benefits reported by 6 July.


         

        Key takeaway: take your three most awkward pay cases into every demo. If a product handles your standard monthly run beautifully and your awkward cases need a workaround, you have found the cost of ownership nobody quoted you.
         

        How legislative change reaches your system

        Rates and rules change every April, and sometimes mid-year. Every vendor will say they keep the system current. That is not the question. The question is how, and when.

        What to ask: are April changes delivered before 6 April or after. How are mid-year changes handled, and how are you told what changed. What happens if a change is confirmed late in the Budget cycle. Can an update be rolled back if it causes a problem. Is the vendor involved in the consultation that shapes these changes.

        A vendor that answers those precisely is telling you something real about how it operates. A vendor that answers "we handle compliance" is telling you something too.
         

        Security, data protection and control

        Where you use a hosted product, you are the controller and the vendor is a processor. UK GDPR requires a written contract between the two, and the ICO sets out eight specific obligations it must cover, from documented instructions through to what happens to your data when the contract ends.

        Beyond the contract, look for role-based access matching how your team works, segregation of duties so the person who changes a bank account is not the person who approves the run, and an audit trail recording who changed what and when. Certifications such as ISO 27001 and ISAE 3402 are useful because someone other than the vendor has tested them. You should also know where your data is held, and that minimum wage records must be kept for at least six years.

          Features worth comparing, and the ones that are table stakes

          Every product in this market calculates gross to net, produces payslips and files to HMRC. Comparing products on those is comparing them on nothing. The useful distinction is between what varies and what does not.


           

          Table stakes Where products genuinely differ
          Gross to net calculation, PAYE and National Insurance, payslip production, RTI submission, statutory payment calculation, basic reporting, HMRC recognition Pay rule flexibility: whether unusual elements are configured or need custom work. Retro processing: automatic recalculation across closed periods, or manual. Reporting: whether non-technical users can build what they need, or every new report is a request. Self-service: what employees and managers can actually do unaided, and how it behaves on a phone. Multi-entity handling: reporting and user access across schemes and companies. Correction routes: how a mistake found after submission is fixed. Workflow: whether approvals match your sign-off chain or you adapt to theirs. Year end: how much is automated.


           

          Deployment model is worth settling early but is rarely the deciding factor now. Most new UK payroll products are cloud-hosted, with on-premise and hosted options narrowing. If you are replacing locally installed software, the move itself has implications for access, updates and disaster recovery that are worth understanding: cloud payroll software covers them.

            Integration: the part most buyers underestimate

            Payroll never operates alone, and integration is consistently the most underestimated part of a software project. It is underestimated in effort, in cost, and in how long it keeps costing, because an interface is not built once and forgotten. It has to keep working as both systems change.
             

            What payroll has to talk to

            • HR system. Starters, leavers, changes to pay and hours. The highest-value integration for most organisations, because rekeying is where errors enter.
            • Time and attendance. Approved hours, absence, shift premia. Essential if any significant part of pay is variable.
            • Pensions. Assessment results and contribution files, in each provider's format and on its schedule.
            • Finance and the general ledger. Journals, cost centre splits, accruals. Ask what the journal looks like before assuming it fits your chart of accounts.
            • Banking. Payment files in the format your bank accepts, including BACS where you use it.
            • Benefits and expenses. Salary sacrifice arrangements, deductions, and anything reimbursed or taxed through payroll.

             

            File transfer or API, and why it matters

            Scheduled file transfer moves a file on a timetable: simpler, well understood, and adequate where data changes predictably. API integration passes data directly, closer to real time, with fewer timing gaps but more to build and maintain.

            Neither is automatically right. Match the method to how often data changes and how quickly payroll needs it. A monthly payroll taking HR changes once a cycle may be well served by a file. A weekly payroll driven by approved hours from a time system usually is not.
             

            Who builds it, and who keeps it working

            This is the question that decides your real cost.

            What to ask: is this a standard integration the vendor already supports, or a build. If it is standard, what exactly does it cover and what does it not. If it is a build, who does the work and who pays. When either system is updated, who is responsible for making sure the interface still works, and is that covered by the contract or chargeable. How are failures detected, and who tells you.

            Where payroll and HR come from one supplier, some of this falls away, which is one of the real arguments for a single platform over separately chosen products. There are trade-offs in both directions: integrated HR and payroll software covers them, and you can also read about payroll integrations.

              What it costs over the life of the contract

              The monthly licence fee is rarely the biggest number, and comparing products on it will mislead you. Costs cluster in year one and then settle, so a product that looks cheap per employee can be the more expensive choice across a five-year term.
               

              How payroll software is priced

              Most UK products use one of a few structures, sometimes in combination.


               

              Structure How it works and what to watch
              Per employee per month A rate per active employee each month. Predictable and scales with headcount. Check: whether leavers still count in the month they leave, and whether there is a minimum charge.
              Tiered or banded A price band covering a headcount range. Stable within a band. Check: where the next band starts, because growth can trigger a step change.
              Per payslip Charged per payslip produced. Check: how this behaves if you run multiple frequencies or issue supplementary payments, since a weekly payroll produces far more payslips than a monthly one for the same people.
              Modular A core licence plus priced modules. Flexible. Check: which of your must-haves sit outside the core.


               

               

              The costs outside the licence

              • Implementation and configuration, usually the largest single line in year one.
              • Data migration, including year to date figures and anything you must retain.
              • Integration build, per interface, plus ongoing maintenance.
              • Training, for payroll and for everyone else who touches the system.
              • Your own team's time, a real cost that never appears on a quote. Parallel running in particular is work your team does, not the vendor.
              • Annual uplift, and how it is calculated.
              • Exit, covering data extraction and the format you get it in.

               

              Costing it over three to five years

              Build a simple model rather than comparing quotes. Take the contract term you expect, apply your projected headcount year by year, add the one-off costs in year one, apply the stated uplift to the recurring costs, include an estimate of internal time, then compare totals.

              The exercise usually reorders a shortlist, because a product with a low monthly rate and a heavy implementation lands differently over five years than one priced the other way round. For how this compares against an outsourced model, see payroll outsourcing costs.

                How to run the selection

                A structured process beats a feature comparison, every time. The aim is evidence rather than impressions, and being able to show how you reached the decision.
                 

                From longlist to shortlist

                Build a longlist of eight to fifteen products from vendor research, peer recommendations, professional networks and your own market scan, then filter against your must-haves to a shortlist of three to five. More than five and you cannot give any of them proper attention. Fewer than three and you have no real comparison.
                 

                The RFP

                A written request gives you comparable answers you can hold a vendor to later. Build it from your requirements list rather than a generic template, and ask for specifics rather than yes or no. "Describe how your system handles a mid-year move from Scotland to England" tells you far more than "do you support Scottish income tax". A payroll RFP template is a useful starting structure, and our RFP template includes more than 250 questions to cut down from.
                 

                Scripted demos: make every vendor run your scenarios

                This is the single most valuable thing you can do, and almost nobody does it. A standard vendor demo shows a clean payroll with tidy data, chosen to show the product at its best. It tells you very little.

                Instead, write a demo script, send it to every shortlisted vendor in advance, and use the same script for all of them. Include your awkward cases, not your easy ones:

                1. A mid-month starter on a non-standard pay element, with a backdated correction the following period.
                2. An employee moving from Scotland to England mid-year, showing the year to date position after the move.
                3. A variable-hours worker's payslip, showing hours split by rate.
                4. Someone with two court order deductions where earnings are too low to satisfy both.
                5. A pay award backdated three months across a closed period.
                6. The pension contribution file as your provider actually requires it.
                7. A pay run submitted and then found to be wrong.
                8. The month end journal, in the shape finance needs.

                Ask to see each one performed in the system, not described, and note where a vendor has to come back to you. In our experience, the buyers who learn most from a demo are the ones who supply their own awkward scenarios in advance, because it moves the conversation from what the product can do in principle to what it does with your payroll.

                Where a trial or sandbox is available, take it, and have the person who will run payroll use it rather than the person leading the project.
                 

                Reference calls and what to ask

                Ask every shortlisted vendor for references from organisations of similar size and complexity, and speak to at least three: one recently implemented, one who has been with them longer.

                What to ask: what did implementation involve from your side, and how did it compare to what you were told. What took longer than expected. How quickly are support queries resolved, and does the person answering understand UK payroll. How did the last April change go. What do you wish you had asked before signing.
                 

                Migration, and what to ask about it now

                Migration belongs in the selection because it is where projects go wrong, and because the answers differ by vendor.

                What to ask: what does the vendor do and what does your team do. How is year to date data brought across and validated. How many parallel runs do they recommend, and what does your team do during them. Can you go live mid-year, or is April the only sensible cutover. What happens to historical records in the old system. In our experience, the most common cause of overruns is incomplete or undocumented data in the outgoing system, worth investigating before you commit to a timetable rather than after. The detail of running the project sits in payroll implementation.
                 

                Scoring and making the decision

                Score against your requirements, not your impressions, in a way that survives being questioned.

                • Weight each requirement band before scoring anything: must-haves heaviest, should-haves roughly half that, nice-to-haves light enough to break a tie but not decide an outcome.
                • Score each product against each requirement on a short scale: met as standard, met with configuration, met with custom work, not met. The configuration and custom work distinction matters, because custom work costs money and makes upgrades harder.
                • Score the vendor separately from the product. Support, UK payroll expertise, implementation approach, roadmap and financial stability belong in their own section.
                • Add total cost as a separate line, using the three to five year figure, so a cheap product cannot quietly win on price alone.
                • Record why, not just the number. The written rationale is what you need when someone asks in two years why this product was chosen.

                Settle the commercial terms before signature: contract length and notice period, how the annual uplift is calculated, what support includes and what is chargeable, what happens if headcount moves significantly either way, and what data you get back on exit and in what format.

                  Download the RFP template

                  Why SD Worx

                  We have been running payroll for 80 years, and today we serve more than 90,000 customers worldwide and process over six million payslips every month, with a UK payroll accuracy rate of 99.97%. Our payroll professionals are CIPP-certified, and our technology is HMRC-recognised and GDPR-compliant, certified to ISO 27001, ISAE 3000 and ISAE 3402 Type II.

                  We help shape UK payroll legislation, not just follow it. SD Worx representatives sit on UK Government consultation panels including the Rep Body Group and the Employer Payroll Group, and we are active in BCS (PSG), IReeN and the CIPP. Our UK Compliance Director, Simon Parsons, is a recognised authority on UK payroll legislation and fronts our annual Payroll Legislation Guide and monthly Payroll Question Time. That matters for the question in this guide about how legislative change reaches your system, because we are in the room when those changes are consulted on.

                  Briggs Equipment has run its payroll on our software since 2007, across seven companies, and its own payroll team drives the automation and self-service behind it.

                  We are also clear that payroll software is not the right answer for every organisation. If your team is stretched or your payroll expertise sits with one person, a managed service may serve you better, and we would rather tell you that early.

                    Frequently asked questions

                    What should I look for in payroll software?

                    Look for four things in order: that it handles your pay rules and statutory obligations correctly, that it integrates with the systems feeding it, that support comes from people who understand UK payroll, and that the total cost over the contract term works. Fit matters more than features, because almost every product does the common things well and the differences only appear in your own edge cases.

                     

                    How do I compare payroll software?

                    Compare against a documented requirements list rather than vendor feature lists, which are written to look comprehensive. Score each product on whether a requirement is met as standard, through configuration, through custom work, or not at all. Then add a three to five year total cost, and score the vendor separately from the product.

                     

                    Does payroll software have to be HMRC recognised?

                    Any software you use to report PAYE must be able to submit to HMRC, which in practice means recognised software. Recognition confirms the product can file online and nothing more: HMRC states it cannot recommend one product over another. Treat it as a minimum filter, not a mark of quality.

                     

                    How much does payroll software cost in the UK?

                    Pricing is usually per employee per month, in headcount bands, per payslip, or a core licence plus modules. The recurring fee is rarely the largest cost: implementation, migration, integration build and training usually outweigh the first year's licence, so compare across three to five years rather than monthly.

                     

                    What questions should I ask a payroll software vendor?

                    Ask how your most awkward pay cases are handled, and to see them demonstrated rather than described. Ask when April legislative changes are delivered and how you are told what changed. Ask what is standard in an integration and what is a chargeable build, who maintains it afterwards, and what data you get back if you leave.

                     

                    What is the difference between payroll software and payroll outsourcing?

                    With software, your team runs payroll and the product provides the engine. With outsourcing, a provider runs the processing while your team supplies the data and approves the output. You remain the employer under both models, so the choice is about where the work and the expertise sit, not where the obligation sits.

                     

                    Can I switch payroll software part way through a tax year?

                    Yes, and plenty of organisations do, but it is more work. A mid-year move means bringing year to date figures across accurately and validating them, because everything from tax to statutory payments depends on them. An April cutover avoids that, though it falls in payroll's busiest period.

                     

                    Do I need different payroll software for Scotland, Wales or Northern Ireland?

                    No. One UK system should handle all four nations. What it must do is apply Scottish and Welsh rates correctly from the tax code prefix HMRC issues, and handle people moving between nations mid-year. Scotland has more income tax bands than the rest of the UK, so check how a product handles that rather than assuming it does.

                      Ready to talk through what would fit your payroll?

                      Every payroll is different, and the right answer depends on your pay rules, your systems and your team. Talk to us about what you are trying to solve and we will be straight with you about whether software or a managed service is the better fit.

                        Explore payroll software