Payroll software planning for 2027: Xero features and HMRC benefits dates

Payroll software planning for 2027 should distinguish product functions from changes to employer duties. Xero Payroll offers a concrete feature baseline: flexible-hours salaried payroll, migration support and employee self-service. HMRC's benefits-payrolling timetable adds dates to that buying decision, while supplier security deserves a separate evidence check.

Start by recording the employer's required workflows, rather than treating a future-year label as a buying recommendation. Keep documented functions, implementation dates and trial results separate in the payroll software planning record. Decide which requirements need a demonstration and which need a dated document before selecting a product.

Xero Payroll: the documented feature baseline

Xero Payroll supports salaried employees with flexible working hours. An automated data-mapping wizard makes it easier to transition to Xero Payroll from another provider. These are specific functions to consider when assessing working patterns and migration, rather than a general promise that every employer's payroll requirements are covered.

Xero payroll provides reports for internal use and helps users meet HMRC requirements each month. Employees can receive self-service access to view payslips, request leave and submit timesheets directly from Xero. Assess those functions against the tasks employees and payroll staff need to complete, using representative example records.

Xero's documented feature set therefore covers flexible-hours salaried payroll, migration support and employee-facing tasks. Consider it against those requirements, then test the employer's benefits workflow separately. If the decision involves a move, plan how to switch payroll software and retain evidence that transferred records match the intended inputs.

HMRC benefits-payrolling dates for 2027

From April 2027, employers will not need to register to payroll mandatory benefits in kind: company cars, car fuel, vans, van fuel and private medical benefits, under HMRC's mandatory payrolling guidance. Match the employer's benefit records to those named categories before preparing a software trial.

HMRC will automatically remove benefits in kind from employees' tax codes ready for mandatory payrolling to start on 6 April 2027. Put that date into the operating workflow. Assign responsibility for checking benefit inputs and reviewing the resulting payroll records, rather than assuming a product feature settles the whole process.

The service to register to payroll non-mandatory benefits in kind from April 2027 will go live in November 2026. The deadline to register voluntarily is 5 April 2027. Keep this voluntary route distinct from the mandatory benefits that do not need registration, and record the employer's intended approach.

For an illustrative example, use a private medical benefit in a trial record for April 2027. Request evidence showing the benefit category, the period and any amendment made during the demonstration. Keep the input record and resulting output together so another reviewer can inspect the same case without relying on a verbal assurance.

Keep the Class 1A transition visible

In July 2027, employers will still pay Class 1A National Insurance for benefits provided in the 2026 to 2027 tax year under the P11D system, while starting real-time Class 1A payments for benefits provided from April 2027 onwards. Keep those benefit periods distinct in the planning record.

Use the budget template to separate the earlier-year payment from payments associated with benefits provided from April 2027. Ask for a demonstration or report that identifies the relevant period. Label each entry clearly, and agree who checks it before approving the employer's payment plan and related payroll records.

Supplier security: request concrete evidence

The voluntary Software Security Code is designed to help software vendors and their customers reduce the likelihood and impact of software supply chain attacks and other software resilience incidents. Use that purpose to frame supplier questions, rather than treating the Code as a compulsory certification or a product endorsement.

The Code's principles are relevant to any type of software for business customers. For a payroll review, ask how access is controlled, how changes are checked and how incidents are handled. Request dated documents, and identify the product and service each document covers before accepting it as relevant evidence.

Possible evidence to request includes a written access policy, a sample change-approval record, a recovery-test report and an incident-response procedure. Check each document's scope and date before drawing a conclusion. Keep the documents with the vendor due diligence record, and record any unanswered question for follow-up with the supplier.

Turn the planning priorities into a buying decision

Build the shortlist around the employer's required functions and the benefits timetable. Xero supplies a named feature baseline for flexible-hours payroll, migration and self-service. Use the same employer scenario to assess those functions and the benefits workflow, then review security documents as a separate part of the decision.

Retain a concise supplier comparison showing the requirement, the evidence inspected and the decision. Prefer a conclusion such as "the demonstrated self-service tasks match our requirements" over an unrestricted claim of suitability. Approve the purchase only after the employer's priority workflows and implementation responsibilities have been checked and recorded.