What is already confirmed for payroll software in 2027, and what still depends on choices

Payroll software in England is heading into 2027 with several confirmed operational changes already visible. Benefits reporting is moving into real-time payroll, recent statutory sick pay rules need to be embedded correctly, and labour-supply chains carry new PAYE accountability. Artificial intelligence is appearing in tax software discussions, while security and supplier evidence remain serious purchasing concerns.

None of that justifies a precise prediction about market size or a claim that one type of platform will win. The more useful outlook is a set of dated facts, plausible scenarios and triggers that tell an employer when to revisit its plan.

What is confirmed for 2027

From 6 April 2027, employers must payroll Income Tax and Class 1A National Insurance contributions for a specified group of taxable expenses and benefits. HMRC's interim guidance on mandatory payrolling currently names company cars, car fuel, vans, van fuel and employer-provided medical benefits. It says employers will be able to payroll some other benefits voluntarily.

This is more than a reporting switch. A payroll team may need earlier and more dependable data from fleet, benefits, HR and finance colleagues. Software must deal with changes, corrections and employee explanations. Class 1A calculations and reconciliations need visible evidence. The precise effect varies with the employer's benefits, so a buyer should use its own cases in demonstrations and acceptance tests.

The rule is confirmed, while some implementation detail may still change. HMRC's August 2026 Employer Bulletin says final phase-one guidance is expected in autumn 2026. Treat that publication as an update trigger rather than filling gaps with assumptions.

The 2026 baseline still matters

Software selected for 2027 must already handle rules that took effect in 2026. Statutory sick pay changed from 6 April 2026. HMRC's February Employer Bulletin explains that the lower earnings limit and waiting period were removed. It states that an eligible employee receives 80 per cent of normal weekly earnings or the current flat rate, whichever is lower.

Employers should test ordinary sickness, low earnings, linked absence information and retrospective corrections. The expected result must come from current guidance and be reviewed by someone with payroll competence. Merely seeing a supplier's release note does not prove that local settings, integrations and dates produce the right outcome.

Umbrella-company arrangements also gained a significant PAYE rule. HMRC's labour-supply-chain guidance says the agency holding the contract with the end client, or the end client where there is no agency, is responsible for ensuring the umbrella company operates PAYE correctly. HMRC can recover an underpayment from that agency or end client.

No software feature transfers that legal responsibility away. Systems can support a controlled process through clearer records, reports and evidence retention. Organisations in such chains should define what data they obtain, how it is checked and who responds to an exception.

Integration will be judged by exceptions

Payroll is often described as becoming more integrated. The practical question is whether connected systems transfer complete and timely information while exposing failures. A long connector catalogue is weak evidence if a missing starter or retrospective benefit change disappears silently.

Test real business journeys with synthetic workers. Include duplicate identifiers, invalid dates, blank fields, interrupted transfers and changes made after an ordinary cut-off. Reconcile employee counts and money, then trace each exception back to its owner. Keep the source input, import result, correction and approval.

More connections can reduce repeated entry, but they also create dependencies. The contract should say which supplier investigates a failed hand-off, how quickly it responds and how the employer can operate if the link is unavailable. Integration value is therefore a balance of saved work, data quality and recoverability.

Artificial intelligence should remain accountable

HMRC published guidelines for generative AI in commercial tax software in January 2026. The guidance expects transparent use, reliable sources, human oversight, security, privacy and ethical operation. It also says HMRC does not endorse or approve a developer or product.

Those principles suggest credible applications and firm limits. An assistant might organise a support request, summarise documentation or explain a software exception. It should not create an unreviewed instruction for a disputed deduction or alter a payment simply because its answer sounds confident.

An employer evaluating AI should ask what model is used, which data it receives, what sources ground an answer and how material updates are tested. Users must be able to correct results and refer complex cases to a competent person. A safe fallback should restore the ordinary process without placing payday at risk.

Payroll prompts may contain personal and financial information. Data minimisation, retention, processing location, subprocessors and access control belong in the initial review. The ICO's employment information resources provide an official starting point for worker-data responsibilities, but each employer still needs to understand its actual processing.

Security evidence will influence buying decisions

The payroll service must be available when needed without disclosing or altering sensitive records. Buyers should ask about authentication, privileged access, vulnerability reporting, security updates, audit logs, backups, restoration and incident communication. Answers need documents and test evidence where appropriate, not a collection of badges without scope.

The NCSC's Software Security Code of Practice is a voluntary UK government baseline for organisations that develop or sell software. Customers can use it to structure supplier discussions. It is not a guarantee that a particular payroll product is secure.

Continuity planning must include the employer's own dependencies. Decide what records are available during an outage, who can authorise a fallback payment, how later reconciliation works and how affected employees are informed. Rehearse the response with invented data instead of waiting for a live incident.

Human capability changes with the tools

Automation does not remove the need for payroll knowledge. Skills England's payroll administrator occupational standard describes software-based processing underpinned by the ability to perform manual calculations. It also covers statutory obligations, controls, systems, customer service and changing guidance.

The valuable 2027 skill set combines statutory reasoning with data and supplier challenge. Staff should be able to find the rule and effective date, reproduce a decisive calculation, reconcile interfaces, explain an outcome and recognise when specialist help is required. They also need to understand what information should not be placed into an AI tool.

Training should use cases and evidence. A completed module does not demonstrate that someone can investigate a failed import or explain a corrected payslip. Keep checked examples of calculations, exceptions, communications and recovery exercises, then target the gaps they reveal.

Three planning scenarios for employers

An integration-led scenario favours a connected HR, time, benefits and finance environment. The potential benefit is fewer manual hand-offs. The principal danger is an opaque failure that moves quickly across systems. Choose this path when ownership, reconciliation and fallback are strong.

An assurance-led scenario gives priority to permissions, auditability, resilience and export. It may involve more deliberate review and fewer automatic actions. This is appropriate where workforce complexity, regulated environments or weak historic controls make evidence especially important.

A service-led scenario places more processing or specialist support with a provider. It can improve access to expertise and operational cover, but the employer remains responsible for its duties. Scope, cut-offs, approvals, security, incidents and exit must be clear in the contract and daily process.

These are not mutually exclusive product categories. They are ways to examine a shortlist. An employer may want integrated inputs, strong assurance and managed support, then decide where trade-offs are acceptable.

A practical preparation timetable

First, map the current payroll, benefit and data flows. Record known manual work, corrections, late information, support failures and control gaps. Use that evidence to define requirements.

Next, follow HMRC updates for mandatory payrolling and turn confirmed detail into test cases. Ask the incumbent supplier what will change, when a test environment will be available and which customer actions are required. Compare the response with alternative options only after every supplier receives the same scenarios.

Before configuration, assign input owners and agree cut-offs, corrections and employee communications. Conduct security and privacy review for new processing. Run parallel calculations on synthetic or appropriately protected data, investigate every difference and obtain named approval.

After launch, watch the first cycles closely. Reconcile totals, record queries, examine adjustments and confirm that reports support later obligations. Preserve a route to correct errors without obscuring the original record.

What should trigger a reassessment

Review the decision when final government guidance changes a requirement, a necessary integration is withdrawn, workforce complexity rises, the supplier changes important subprocessors or an incident weakens confidence. Unexpected correction rates, support delays and repeated manual overrides are internal triggers.

Schedule a dated review even if no trigger fires. Recheck HMRC recognition where it is relevant, current product terms, prices, service evidence and export arrangements. Market claims should be refreshed from their original method and geography before reuse.

The sound outlook for 2027 is not that payroll will become effortless. It is that regular processing will carry more connected data and require clearer evidence of how decisions are made. Employers that prepare cases, controls and capable people can use new software features without surrendering accountability.