Strategy
Part of Payroll software strategy and planning 2027: a framework
A payroll software planning record that ties customer evidence to commercial gates
Use this England payroll software planning template to connect customer evidence, PAYE scope, pension workflows, testing, operations and commercial gates.
Complete this template for one release, buyer group and tax year. A plan that hides uncertainty will fail precisely where payroll needs a clear decision owner.
What to take away
- Replace every bracketed prompt with evidence or mark it unknown.
- Avoid a single pensions supported tick that conceals untested tasks such as join, leave and provider exchange.
- Set dated commercial gates and name the person able to stop launch at each one.
- No pilot should quietly become production because a deadline arrives.
Outcome and audience
Target user: [role and operating model]
Payroll context: [employee range, pay frequencies, PAYE schemes, pension providers]
Observed problem: [event, frequency, consequence and current workaround]
Promised outcome: [measurable result]
Unsupported cases: [territories, worker situations, integrations and service tasks]
Attach anonymised evidence from recent payroll cycles. HMRC's running payroll overview can help map the standard tax-month sequence, but the customer's actual approvals and systems must come from research.
Reporting and calculation scope
| Area | Supported version | Evidence | Owner | Next review |
|---|---|---|---|---|
| PAYE tax | [tax year] | [test reference] | [name] | [date] |
| National Insurance | [tax year] | [test reference] | [name] | [date] |
| Student loans | [tax year] | [test reference] | [name] | [date] |
| FPS and EPS | [schema or rule] | [acknowledgement] | [name] | [date] |
| Statutory payments | [scope] | [case set] | [name] | [date] |
Use the HMRC software-developer collection to locate current specifications. The 2026 to 2027 test-data page covers supplied test scenarios for PAYE, National Insurance, student loans and statutory payments for that tax year, and explains that the examples support developers' own testing. Passing supplied cases does not replace wider product, integration and regression tests.
Pension workflow
Assessment performed: [yes, no or partial]
Contribution basis and tax-relief method: [verified configuration]
Provider exchange: [scheme, format, version and rejection route]
Join, leave and communication scope: [tasks and owner]
Records retained: [content, period and access]
Check the plan against The Pensions Regulator's payroll software task list, which covers automatic enrolment tasks including assessment, joining, contributions, leaving and provider exchange. Avoid a single "pensions supported" tick that conceals untested tasks.
Data, access and continuity
Record controller, processor and sub-processor roles; data categories; lawful instructions; retention; user roles; administrator authentication; logging; exports; backups; restoration and incident ownership. Include service dependencies and the tested recovery time for payroll-critical functions.
If the product interacts with HMRC services, review the current web-services access policy. Do not design a workaround around collecting another party's sign-in details.
Delivery and commercial gates
Set dated gates for design review, specification freeze, test completion, parallel payroll, customer acceptance, support readiness and release approval. For each, name the evidence required and the person able to stop launch.
Worked example (illustrative only): a 250-employee monthly payroll. The specification freeze gate on 15 May requires signed scope and zero open design queries; the stop owner is the payroll manager.
The parallel payroll gate on 10 June requires a reconciliation difference at or below £1 per payslip; the stop owner is the payroll manager. Customer acceptance on 30 June requires signed acceptance from the payroll manager; support readiness on 5 July requires two trained support staff.
Model pricing against observed onboarding, support, exception and maintenance costs. List assumptions for active employees, extra runs and migration. Review actual cohort margin after several cycles.
Pricing unit (illustrative only): annual cost = (per-payslip rate x payslips per run x runs) + (per-employee rate x active employees x 12) + (exception charge x exception runs).
For illustration, at £1 per payslip, a 250-employee monthly payroll costs £250 per run, or £3,000 per year before onboarding, support and exception charges.
Onboarding is typically a one-off fee or 10 to 20 implementation hours; support is 1 to 3 hours per month; an exception run is 2 to 5 hours or a fixed charge per run.
Finish with unresolved decisions, dependencies and expiry dates. The template is complete only when a reviewer can see what is supported, what remains uncertain and what evidence permits the next step.
Pilot and acceptance record
Authoritative live process: [existing system and owner]
Parallel cases: [ordinary, boundary and exception scenarios]
Reconciliation result: [differences, causes and resolution]
Stop conditions: [events that prevent progression]
Customer acceptance: [role, date and evidence]
No pilot should quietly become production because a deadline arrives. State which system calculates the live payroll, who may submit information and how test records are isolated.
Measurement and review
Define completed payroll, accepted submission, correction, support incident and active billed employee before reporting them. Record product outcomes separately from leads and trials. Review after each run during the pilot, then set a cadence appropriate to the release.
At review, compare actual support, infrastructure and maintenance work with the pricing assumption. Retire metrics that do not influence a decision. Preserve the signed version of the plan so later teams can see which scope and evidence governed the release.
Before you act
- Replace every bracketed prompt with evidence or mark it unknown.
- Check each dated gate has named evidence and a stop owner.
Common questions
What should happen to bracketed prompts I cannot fill in?
Unresolved items must stay visible. Record what is unknown, who owns the question and when it will be reviewed, rather than guessing or leaving it blank.
Does passing HMRC test data prove my payroll product is ready?
No. HMRC's 2026 to 2027 test-data page covers supplied examples that support developers' own testing. You still need your own coverage before release.
How should I handle pricing and margin after launch?
Model pricing against observed onboarding, support, exception and maintenance costs, and list assumptions for active employees, extra runs and migration. Then review actual cohort margin after several cycles, comparing real support, infrastructure and maintenance work with the pricing assumption.
