How UK payroll software pricing works
Two businesses running the same 20-person payroll can pay wildly different amounts for software, and the reason is rarely the feature list. It is the pricing model. A per-employee licence, a per-payslip charge and a flat annual fee produce very different bills for identical payroll, and the spread across providers can run into several hundred per cent for the same headcount. Meanwhile the floor is fixed for everyone: every UK employer must issue payslips [2] and file Real Time Information on or before payday [3].
Pricing pages tend to show a single number and leave the buyer to work out what it means at their own headcount and pay frequency. That number rarely tells the whole story. The true annual cost depends on how the model interacts with the shape of the payroll, and on a set of costs that never appear on the pricing page at all.
This article breaks down the three pricing models used across the UK market, shows how each one behaves as a business grows, and sets out the hidden costs, penalties and statutory updates, that decide whether a cheap-looking quote stays cheap across a full tax year.
Key takeaways
- UK payroll software is priced in three main ways: per-employee licence, per-payslip, and flat annual licence [1].
- Per-employee pricing grows with headcount and is charged even when a worker is paid nothing that month.
- Per-payslip pricing tracks payroll activity, which suits weekly pay and variable headcount.
- Late Real Time Information filing costs from £100 a month for a small employer, a cost outside any subscription [4].
- HMRC recognition is the baseline every serious product meets, not a paid extra [5].
The three ways UK payroll software is priced
Almost every UK payroll product uses one of three billing models, or a blend of them. The table below summarises how each is charged and where it fits.
| Model | Charged on | Best fit | Weak spot |
|---|---|---|---|
| Per-employee licence | Each active employee per month | Stable monthly headcount | Cost rises with every hire |
| Per-payslip | Each payslip produced | Weekly pay, seasonal staff | Frequent pay runs add up |
| Flat annual licence | One fixed yearly fee | Predictable larger teams | Poor value at low headcount |
The choice is not academic. It is usually the single biggest driver of what a business pays, ahead of the feature set or the brand. Reading a quote means translating the model into the payroll the business actually runs, not the payroll on the vendor's example page.
Per-employee licensing
The most common model charges a fee for each active employee each month, frequently on top of a fixed base charge [1]. It is easy to compare between providers because the unit is obvious, and it is predictable for a business with steady headcount and monthly pay [13].
The weak spot is growth. The bill rises with every hire, and a per-employee licence is usually charged whether or not that person was paid in the month. For a business with dormant or occasional staff, that means paying for seats that produced no payslip. As employer costs already climbed with the National Insurance rate reaching 15% above the £5,000 Secondary Threshold from 6 April 2026 [7], a licence that scales purely on headcount adds a second cost that grows in the same direction [8].
Per-payslip pricing
A per-payslip model charges each time a payslip is produced, so the cost follows payroll activity rather than the number of seats held [2]. This suits weekly payrolls, seasonal workforces and any business where headcount moves month to month [13]. A worker who is not paid in a given period generates no charge for that period, which a per-employee licence cannot match.
The trade-off is pay frequency. A weekly payroll produces roughly four times as many payslips as a monthly one for the same people, so the model rewards businesses that pay monthly and needs checking for those that pay weekly. For most SMEs on monthly pay, per-payslip pricing tends to track cost to value more closely than a seat licence, because the meter only runs when payroll actually runs.
Flat annual licence
A flat annual licence charges one fixed fee for the year regardless of headcount. For a predictable team of reasonable size it can be the cheapest option per head, because the fixed fee is spread across many employees [1]. It also makes budgeting simple, since the number does not move as staff join or leave.
The weakness is the opposite of per-employee: it is poor value at low headcount, where a handful of employees carry the whole fixed fee. It can also mask feature tiers, where the low advertised licence excludes auto-enrolment assessment or statutory pay handling that the business is legally required to perform anyway [10]. A licence that looks flat but tiers the compliance features is not as flat as it appears [12].
What a monthly payroll bill actually includes
A payroll subscription is not just a calculation engine. At minimum it should cover the statutory chain that every UK payrun touches. That chain runs from gross pay through income tax bands [16] and National Insurance thresholds [8], across the National Minimum Wage floor [17], student loan deductions [14] and pension contributions, then out to HMRC as a Full Payment Submission [3].
When a quote looks unusually low, the first check is whether it includes all of that or only part. A tool that files Pay As You Earn but leaves the employer to produce payslips and assess auto-enrolment by hand has simply moved cost off the invoice and onto the payroll administrator. The free HMRC tool is the clearest example: genuinely free, but capped at nine employees, with no payslips and no auto-enrolment assessment [6]. Comprehensive SME payroll software folds the whole chain into one fee, which is what makes a like-for-like price comparison possible.
How the same payroll costs different amounts at scale
The three models diverge as a business grows, which is why a quote that wins at five employees can lose badly at fifty. The pattern below shows the direction of each model rather than fixed prices, because the actual figures vary widely by provider.
| Headcount | Per-employee licence | Per-payslip (monthly pay) | Flat annual licence |
|---|---|---|---|
| 5 employees | Low, but base fee dominates | Low, tracks 5 payslips | Highest per head |
| 20 employees | Rises steadily | Rises with pay runs | Competitive per head |
| 50 employees | High and linear | Moderate on monthly pay | Often lowest per head |
| 100 employees | Highest of the three | Moderate to high | Lowest per head |
The takeaway is that no single model wins at every size. A micro-business paying monthly is often best served by per-payslip or a low per-employee tier, while a larger predictable team can find a flat licence cheaper per head. The mistake is choosing a model at one size and never revisiting it as headcount changes. A business planning to grow should price the model at its target size, not just today's [15]. For larger and multi-entity payrolls, enterprise payroll needs are different again, and the per-head economics shift with volume.
The costs that never appear on a pricing page
Two significant costs sit entirely outside the subscription, and both can dwarf the monthly fee.
Penalties for late or wrong submissions
A late Full Payment Submission carries a monthly penalty that scales with headcount, starting at £100 for a scheme with 1 to 9 employees and rising for larger schemes [4]. A scheme is charged only one late-filing penalty per month regardless of how many returns are late, and the first default in a tax year is usually penalty-free, but the exposure is real for any employer whose software makes filing awkward [3]. Software that automates the submission at the end of every payrun removes the most common cause of a late FPS, and that avoided penalty belongs in any honest price comparison [5].
Keeping pace with statutory change
Payroll rules change every April, and mid-year reforms happen too. Statutory Sick Pay changed on 6 April 2026, with waiting days removed and the earnings test scrapped under the Employment Rights Act 2025 [20]. An employer using software that has not been updated for that reform underpays or overpays sick leave and carries the correction cost [12]. The same applies to year-end obligations, where a P60 must reach every employee still on payroll and the deadlines are fixed [19]. A subscription that includes automatic legislative updates is buying down a real risk, not padding the invoice.
Pricing when an accountant runs many payrolls
For an accountant or payroll bureau, the pricing question changes shape. The unit is no longer one business but tens or hundreds of client schemes, each with its own filing obligations to HMRC [18]. A per-employee licence multiplied across every client can become the largest line in the practice's software budget, while a per-payslip model lets the cost scale with the payroll actually delivered [13].
Bureau economics reward a model that scales down as well as up, so that a dormant client scheme costs little and an active one costs in proportion to its output. A payroll bureau platform built for multi-client work prices on activity across the book rather than on seats bought upfront. For software vendors and platforms that want to embed UK payroll into their own product rather than resell a licence, an HMRC-recognised payroll API shifts the pricing question again, from seats to calls, so cost follows usage inside the host product [1].
Conclusion
Payroll software pricing is a question of model, not just number. The same payroll can cost several times more under one billing model than another, and the model that wins at five employees may be the wrong one at fifty. The buyer who reads past the headline figure, checks what the fee actually includes, and prices the model at their target headcount ends up with a bill that reflects the payroll they run.
The costs that decide value are often the ones the pricing page omits: the penalties avoided by reliable filing, and the corrections avoided by software that keeps pace with statutory change. As employer National Insurance and statutory pay continue to move, the products that price on activity and update themselves automatically look cheaper over a full year than a low headline figure that leaves compliance work on the employer's desk. A pricing decision made on total annual cost, set out clearly on a transparent pricing page, is the one that survives the next round of rule changes.
Frequently asked questions
Is per-employee or per-payslip payroll pricing cheaper for a small business?
It depends on pay frequency and how much the headcount moves. Per-payslip pricing tracks payroll activity, so a business paying monthly with variable staff often pays less than under a per-employee licence, which charges for each seat whether or not the person was paid [2]. A business paying weekly produces far more payslips, so the per-payslip model needs checking at that frequency [13].
What should be included in a UK payroll software subscription?
At minimum, payslip generation, income tax and National Insurance calculation, student loan deductions, auto-enrolment assessment and Real Time Information filing to HMRC [3]. A quote that omits any of these has moved a legal duty off the invoice and back onto the employer, who must still meet it by hand [10]. The free HMRC tool, for instance, produces no payslips and no auto-enrolment assessment [6].
Does cheaper payroll software risk HMRC penalties?
Only indirectly. The penalty comes from filing late or wrong, not from the price paid [4]. A late Full Payment Submission costs a small employer from £100 a month, so software that makes filing awkward or unreliable raises the risk regardless of its subscription cost [5]. Software that files automatically at the end of each payrun removes the most common cause of a late return.
How does payroll pricing work for accountants running many clients?
The unit becomes the client scheme rather than the single business, and cost multiplies across the book [18]. A per-employee licence applied to every client can become the practice's largest software cost, while a per-payslip model scales the cost with the payroll actually delivered [13]. Bureau-focused platforms price on activity across the whole client book so that dormant schemes cost little.
