Tools and providers
Choosing payroll software and suppliers with HMRC evidence and scenario testing
Select payroll software and suppliers for an England employer in 2027 through current HMRC evidence, scenario testing, due diligence and controlled implementation.
There is no payroll product that is best for every employer in England. Selection depends on the precise pay-cycle workflow, employee situations, pension arrangement, accounting environment, access model and support need. A credible comparison must use the same scenario and current evidence for every supplier.
The evidence check for this guide was completed on 5 September 2026. Named product features and availability are first-party statements unless explicitly described as independently tested. Prices, plans, integrations and HMRC recognition can change, so reopen all decisive sources before a 2027 purchase or publication.
Define the job before listing suppliers
Start with the employer, not a generic feature matrix. Record:
- legal employers and PAYE schemes;
- active and seasonal employee ranges;
- weekly, fortnightly, four-weekly, monthly or other runs;
- salaried, hourly, variable and director cases;
- starters, leavers and statutory-payment needs;
- workplace pension scheme and tax-relief method;
- time, HR, accounting and payment systems;
- payroll operator, approver, submitter and support roles;
- required reports and audit evidence;
- implementation deadline and risk tolerance.
HMRC's find payroll software guidance tells employers to consider features such as payslips, pension deductions, pension payments, different pay periods and specific reports. It also warns about continuity of payroll IDs when changing software.
Convert the employer facts into essential, useful and irrelevant requirements. A missing essential item can eliminate a candidate. Do not let an attractive non-essential function compensate for inability to complete the core payroll.
Understand the recognised-software list
HMRC's recognised payroll software directory contains free and paid products that can report PAYE online. At the date checked, it included a broad range of employer, bureau and wider business products.
The page is not a ranking. HMRC states that it cannot recommend one product or service over another and is not responsible for problems with purchased software. A listing does not prove:
- suitability for the employer's pay pattern;
- support for the chosen pension provider;
- accessible operation;
- secure configuration;
- reliable customer support;
- fair contract terms;
- successful migration;
- acceptable total cost.
Capture the exact product and date. Do not infer that every product from the same supplier is recognised or that recognition applies to functionality beyond online PAYE reporting.
Six tools worth researching for defined cases
The following entries meet a limited inclusion method: HMRC's own tool or a product represented on the recognised directory, plus a current first-party UK payroll page. They are not ranked and were not independently tested for this draft.
HMRC Basic PAYE Tools
HMRC's Basic PAYE Tools page describes free software for employers with fewer than ten employees. It can perform most payroll tasks, including tax and National Insurance calculations and sending information to HMRC.
The page says it is not designed for agents or bookkeepers. It also publishes operating-system and hardware requirements, explains updates and warns not to uninstall an existing version because payroll data would be lost.
This makes Basic PAYE Tools a research candidate for a very small employer with a comparatively simple process. Investigate payslips, automatic enrolment, multi-user work, remote access, backup and connected accounting separately. Check the current service-availability page before relying on a platform assumption.
BrightPay
BrightPay's current product comparison distinguishes desktop, desktop with Connect and cloud offerings. The supplier lists features for HMRC submissions, coding notices, automatic enrolment, pension connections, employee communications and accounting integrations, with differences between configurations.
The employer and bureau contexts should be evaluated separately. Verify the selected edition, operating-system needs, client or employee limits, migration, data hosting, pension providers, support and commercial terms. Treat usage and satisfaction figures on supplier pages as vendor claims until methodology and independent evidence are reviewed.
Sage payroll products
Sage's UK payroll software page describes a product family rather than one interchangeable tool. It positions offerings for smaller employers, payroll professionals, advanced needs and higher-volume organisations.
Identify the exact product before collecting evidence. A capability described for Sage 50 Payroll or Sage People Payroll should not be attributed to another edition. Ask for plan limits, deployment model, batch functions, employee self-service, pension support, accounting connection, migration, implementation and full contract cost.
Xero Payroll
Xero's UK payroll features page describes PAYE reporting, different pay frequencies, statutory leave and payments, workplace pensions, payroll reports, employee self-service and links with Xero accounting and other tools.
This may be relevant where an employer wants payroll inside an accounting platform. Compare the whole required plan, per-person allowance, add-ons and implementation. Test the named pension connection and every required employee situation. Supplier wording about automation or compliance still needs a defined scenario and observed evidence.
QuickBooks Payroll
Intuit's UK payroll page describes HMRC submissions, statutory payments, accounts integration, time-related functions, pensions and employee self-service. Its linked plan comparison distinguishes Core, Premium and Elite features, including pension connections and user allowances.
Select one plan for assessment. Capture what requires the accounting subscription or another module. Test the promised automated steps, support route, payroll corrections, migration and export. Do not combine the strongest capability from every tier into one comparison row.
FreeAgent Payroll
FreeAgent's payroll feature page describes payroll integrated with its accounting product, covering RTI submissions, pay and deduction calculations, payslips, P60s, pension contributions and reporting.
The supplier's filing-support article identifies circumstances where payroll functionality is unavailable, showing why account type and use case must be checked. Confirm pay frequencies, pension tasks, statutory cases, corrections, employee access and migration for the employer.
Build a like-for-like comparison
Create one reference scenario and send it to every shortlisted supplier. Use a structured evidence table:
| Requirement | Source | Test | Result | Limitation | Expiry |
|---|---|---|---|---|---|
| Exact HMRC-listed product | Official directory | Listing checked | [result] | Point in time | [date] |
| Required pay frequencies | Product record | Calendar setup | [result] | Scenario only | [date] |
| Pension-provider exchange | Supplier and provider | Accepted test file | [result] | Named scheme | [date] |
| Migration | Implementation record | Parallel reconciliation | [result] | Test population | [date] |
| Permissions | Security documents | Role exercise | [result] | Configured edition | [date] |
| Support | Contract and service page | Test escalation | [result] | Stated hours | [date] |
| Exit | Terms and export guide | Complete export | [result] | Format tested | [date] |
Distinguish "supplier stated" from "buyer tested" and "independently verified". A demonstration is useful evidence of what the presenter showed, not proof that an ordinary operator can complete the same task.
Score requirements before testing. Weighting after seeing results invites the team to favour a familiar or commercially attractive supplier.
Evaluate automatic enrolment as a workflow
The Pensions Regulator's payroll-software checklist asks whether a process can assess staff, hold required data, calculate contributions using the correct tax-relief method, generate provider information, support communications, handle worker requests and retain records.
Apply those prompts to the named pension scheme. Test:
- assessment at relevant ages and earnings;
- new starters and changing eligibility;
- contribution bases and rounding;
- employer and worker contribution results;
- opt-in, join and opt-out cases;
- postponement and re-enrolment where in scope;
- provider file or connection;
- rejection, correction and reconciliation;
- record and communication responsibilities.
A product may handle calculation while the pension provider handles another step. The contract and operating guide should make the boundary visible.
Perform vendor due diligence
Verify the contracting entity and distinguish vendor, reseller, implementer and service provider. Obtain evidence for the exact hosted or desktop product.
For personal data, determine controller, processor and sub-processor roles. Review locations, transfers, retention, access, logging, incident support, export and deletion. The ICO's controller-processor contract guidance provides a current prompt for the processing details and terms that may be required.
Security review should cover development, vulnerabilities, dependencies, authentication, privileged support, encryption, customer separation, monitoring, backup and restoration. Request evidence proportionate to payroll risk. A certificate can support diligence but does not answer every architecture or operating question.
Review service dependencies and financial continuity. Ask how customers are notified of incidents, tax-year releases and end-of-life decisions. Match support hours and escalation to the employer's pay schedule.
Calculate the full cost
Use a twelve-month scenario and, where appropriate, a multi-year view. Include:
- base subscription;
- employee or employer charges;
- extra pay runs;
- accounting, HR, time or pension modules;
- setup and migration;
- training and implementation support;
- payment or document-delivery charges;
- internal operator and reviewer time;
- contract renewal and price-change terms;
- exit and transition assistance.
State VAT treatment and promotional expiry. A discounted first period is not the recurring cost. Quote-only information should remain unknown until a written offer is obtained.
Measure support burden during a pilot. A nominally cheaper product can cost more when setup and repeated manual work are included, while a broader bundle can be wasteful if the employer does not need its other functions.
Run a controlled implementation
Once a supplier is selected, preserve the old system as authoritative until acceptance. Clean and validate source data, agree opening figures and restrict migration access. Take particular care with payroll identifiers.
HMRC's software guidance warns that changing an employee's payroll ID without handling the change indicator correctly can create duplicates or affect the PAYE bill. Follow current guidance for the actual migration and obtain appropriate payroll expertise.
Configure the tax year, employer references, calendars, statutory settings, pensions, roles and integrations. Use synthetic tests before controlled customer data.
Run parallel payrolls containing ordinary employees, variable pay, starters, leavers and corrections. Reconcile gross pay, deductions, employer liabilities, net pay, pensions and report outputs. Investigate every difference and record approval.
Test submission acknowledgements, failed responses, pension rejection, accounting journals, employee documents, backup restoration and a full export. Prepare rollback and support escalation before the first live run.
Plan for change and exit
Payroll products change through tax-year releases, integrations, supplier strategy and technology support. Assign owners to monitor HMRC recognition, release notes, pension connections, service incidents and contract notices.
The contract should define supported scope, customer responsibilities, service, changes, payment, liability, renewal, termination and transition. Ensure the order form records the precise plan and employer assumptions.
Before purchase, test how to export employee records, payroll history, reports, pension information, audit logs and documents required for continuity. Clarify post-termination access, retention and deletion. A supplier is easier to trust when leaving is technically and contractually understood.
Publish or buy with visible limits
A comparison should disclose who conducted it, how products were included, the reference scenario, evidence date, commercial relationships and tests not performed. Avoid presenting supplier pages as independent verification.
Recheck every volatile fact on the decision date. If the employer's workflow changes, rerun the assessment rather than carrying forward the old winner. The appropriate 2027 choice is the product whose current, tested scope fits the employer with acceptable risk, support and full cost. It is not a permanent title held by one brand.
In this guide
- Write the employer scenario first, then let payroll software prove it can handle itSelect payroll software for an England employer by testing PAYE, pensions, pay patterns, migration, data controls, support, exit and full cost.
- From HMRC Basic PAYE Tools to QuickBooks, payroll starting points with their use-case limitsReview six payroll software starting points for England using HMRC and first-party sources, with use-case limits instead of an unsupported best-product ranking.
- Comparing payroll suppliers on one scenario, current HMRC status and full costCompare payroll software suppliers for England with one scenario, current HMRC status, product-level evidence, controlled testing and full-cost analysis.
- Due diligence on a payroll vendor, from entity identity to a clean exitPerform payroll software vendor due diligence in England across entity, product scope, PAYE, pensions, security, resilience, support, contracts and exit.
- Implementing payroll software with reconciled migration, parallel runs and a rehearsed cutoverImplement payroll software for an England employer with governed data, reconciled migration, pension testing, parallel runs, support and rollback.