UK Statutory Sick Pay: Employer’s Guide for 2026

You're probably dealing with this already. An employee calls in sick. Their manager logs it in Teams. HR updates a spreadsheet. Payroll gets a late email with unclear dates, and someone then has to work out whether the absence qualifies for SSP, whether waiting days apply, and what should be paid in that pay run.

That process breaks down fast when you've got part-time staff, rotating shifts, multiple payroll cut-offs, or an occupational sick pay policy layered on top of the statutory minimum. The problem isn't usually the principle of UK Statutory Sick Pay. It's the operational detail.

For a Head of People, SSP sits at the point where compliance, employee experience, manager capability, and payroll accuracy all meet. If any one of those parts is weak, the issue lands back with HR.

Why Getting SSP Right Is More Than Just Compliance

Most organisations don't struggle with SSP because the concept is difficult. They struggle because the work is fragmented. Absence is recorded in one place, contracts sit somewhere else, payroll rules live in a separate process, and managers often don't understand the difference between “off sick”, “eligible for SSP”, and “paid under company sick pay”.

That creates two risks at the same time. The first is compliance risk. The second is trust. Employees rarely know the technical rules, but they know when their pay is wrong, when communication is vague, and when HR appears uncertain.

Why the employee impact matters

SSP is often treated as a payroll mechanic. In practice, it's part of your employment offer. It affects how safe people feel taking genuine time off, how fairly they believe illness is handled, and whether managers escalate issues properly.

That matters because SSP is a limited safety net, not full income protection. Citizens Advice reports that only about half of employees are paid their full wages when sick, while up to 1 in 4 rely on SSP alone, and a full-time worker on the minimum wage would lose more than 70% of earnings if forced to live on SSP. For many employees, getting the statutory position wrong isn't a small admin error. It has an immediate effect on household income.

Practical rule: If your SSP process depends on someone remembering a manual step, you don't have a reliable SSP process.

What usually goes wrong in real organisations

In day-to-day HR operations, the biggest problems are rarely exotic legal disputes. They're ordinary failures of process:

• Dates are captured badly. Managers record the first missed shift, but not the first day of incapacity.
• Qualifying days are misunderstood. Payroll pays a neat weekly amount when the statutory position requires day-based treatment.
• Policies conflict. Contractual sick pay says one thing, payroll applies another.
• Evidence handling is inconsistent. One manager asks for a fit note too early, another never requests one at all.

SSP also sits inside a wider duty-of-care framework. If your business is trying to improve absence handling more broadly, sickness pay can't be separated from reporting lines, manager training, return-to-work practice, and wellbeing support. That's why duty of care in employment is closely tied to how sickness absence is administered, not just how it's documented.

A mature organisation doesn't treat SSP as an isolated payroll task. It treats it as a repeatable people process that has to be fair, explainable, and auditable.

SSP Explained The Core Rules for UK Employers in 2026

SSP is a statutory payment for eligible employees who are off sick. The mechanics matter because small date errors lead directly to underpayments or overpayments.

A useful way to think about the current statutory model is as a timer. The timer starts on the first day of sickness absence. It doesn't start on the day payroll is told, and it doesn't start when a fit note arrives.

The current statutory baseline

The current framework has a few fixed points. The Humaans SSP guide notes that SSP was created in 1983, extended to its current maximum of 28 weeks in 1985, is structured as a flat-rate benefit, was £116.75 per week in the 2024/25 tax year, and GOV.UK's live guidance shows £123.25 per week for the current period. The same source also confirms that entitlement begins only after 4 consecutive days of sickness, which means the first 3 waiting days are unpaid under the statutory scheme.

That gives you three practical anchors:

1. It's flat-rate under the current structure. Salary level doesn't change the statutory weekly amount.
2. It doesn't begin immediately under the current rules. Waiting days matter.
3. It has a statutory cap. You can't treat SSP as open-ended.

What HR and payroll must identify correctly

The first technical distinction is between consecutive sick days and qualifying days.

Consecutive sick days tell you whether the sickness period is long enough to trigger SSP entitlement under the current rules. Qualifying days tell you which days are payable. If someone is sick over a weekend but doesn't normally work weekends, those days may still matter for determining a sickness period, but they aren't automatically payable days for SSP.

A lot of SSP errors happen because teams count absence in calendar terms but pay it in working-pattern terms without joining those two views together.

A clean way to assess an absence

Use this sequence every time:

• Step one: Confirm the first day the employee was incapable of work.
• Step two: Confirm whether the sickness lasted long enough under the current statutory trigger.
• Step three: Identify the employee's qualifying days. In other words, the days they would normally have worked.
• Step four: Apply the statutory rate only to payable qualifying days, subject to the waiting-day rules and your own contractual scheme.

If you skip straight to “how much do we pay?”, you usually miss a rule.

What does and doesn't work

A manual approach can still work in a small business with stable working patterns and very low absence volume. It stops working when you introduce shift work, linked absences, new starters, multiple employments, or a blended company sick pay policy.

The strongest process is one where absence entry, working pattern, statutory rules, and payroll output all sit in the same operating model. That's the difference between a rule the business knows and a rule the business can apply.

Calculating SSP Worked Examples for Payroll Teams

In practice, theory often fails to deliver. Payroll doesn't need another definition. It needs a method that can be applied consistently every time.

For worked examples, the key principle is simple. SSP is paid against qualifying days, not as a casual weekly estimate. The weekly figure has to be translated into the employee's actual payable pattern for the relevant week.

If you need a quick refresher on current weekly rates before building your payroll logic, this guide on how much SSP is paid per week is a useful companion.

Example one full week of payable sickness

Assume an employee normally works five qualifying days in a week, Monday to Friday. They are off sick for long enough that SSP becomes payable, and the relevant week is fully payable under the statutory rules.

In that situation:

• Weekly basis: Start with the current statutory weekly SSP rate used by your payroll process.
• Daily conversion: Divide that weekly amount by the number of qualifying days in that week.
• Payment result: Pay SSP for each payable qualifying day in the week.

For a standard five-day pattern, that produces a daily statutory figure for that employee's payable days. The exact amount should be generated from the current rate configured in payroll, not typed into a spreadsheet from memory.

Example two partial week with a mid-week return

Now take an employee who normally works Monday to Friday but returns to work part-way through the week. The common mistake is to pay the full weekly SSP amount because the absence “covered most of the week”.

That isn't the right method.

Use this approach:

If the employee only has two payable qualifying days in that week, pay two day-equivalents of SSP. Don't smooth it across the month unless your payroll system is still preserving the underlying statutory calculation.

Payroll discipline matters: always calculate from days upward, then roll into the payslip. Don't start with the week and work backwards.

Example three monthly pay with sickness across two pay periods

Manual handling becomes risky when a monthly-paid employee goes off sick near the end of one month and remains absent into the next. HR often records one continuous absence, but payroll has to split payment across two separate payroll periods.

The right approach is to separate absence recording from pay period treatment.

• The absence record should stay continuous.
• The statutory analysis should remain based on the actual sickness period and payable qualifying days.
• The payroll output should allocate the relevant payable days into each pay period.

That prevents two common errors:

1. restarting the SSP logic at the start of the next month, and
2. losing visibility of waiting days or payable qualifying days already used earlier in the same absence.

What payroll teams should standardise

The strongest payroll teams usually fix this with three controls:

• A single source of working pattern data so qualifying days are not guessed.
• A locked SSP calculation method so every payroll administrator applies the same logic.
• An exception workflow for unusual cases, including returns to work, linked absences, and corrections after payroll cut-off.

Once those controls are in place, SSP becomes far less dramatic. It turns into a governed calculation rather than an argument between HR, line managers, and payroll.

Employer Obligations Beyond Payment

Paying SSP correctly is only one part of the employer's duty. The other part is process discipline. If records are weak, medical evidence is handled inconsistently, or communication is late, even a correct payment can still sit inside a poor compliance process.

The non-negotiable admin checklist

A sound SSP process should cover the following:

• Absence records: Keep a clear record of when the employee reported sick, the first day of incapacity, the days they would normally have worked, and the payment outcome.
• Evidence handling: Allow self-certification for the early stage of sickness absence, then move to medical evidence when the absence reaches the point where a fit note is appropriate.
• Payroll traceability: Make sure the payslip outcome can be matched back to the absence record and the rule applied.
• Employee communication: Tell the employee what's being paid, under which scheme, and whether company sick pay changes the calculation.

Fit notes need consistent handling

In practice, fit note handling is where line manager inconsistency causes trouble. The usual rule of thumb is straightforward. For the first 7 days, employers generally rely on self-certification. After that point, a fit note may be required.

The issue isn't whether a fit note exists. It's whether your managers know what to do with one.

A fit note does not merely say “off sick” or “back at work”. It may indicate that the employee may be fit for work if adjustments are made. That means HR and the manager need a process for considering temporary changes such as altered duties, adjusted hours, or a phased return.

Don't ask managers to interpret medical documents alone. Give them a workflow, an escalation route, and standard wording.

What employers can and can't do

A practical compliance line looks like this:

SSP1 and end-of-entitlement management

If an employee isn’t eligible for SSP or their SSP is ending, the employer may need to issue an SSP1. This is one of those tasks that gets missed when absence administration is mostly manual.

The operational point is simple. Don’t wait until someone asks for it. Build a trigger into your process so HR or payroll is prompted when an absence reaches the relevant point. That’s especially important in long-running sickness cases, where the employee’s next steps may depend on prompt documentation.

The best employers don’t just pay SSP. They manage the full administrative journey around it.

Navigating Common SSP Scenarios and Edge Cases

Generic SSP guidance often sounds simple because it’s written around a straightforward full-time employee on a fixed pattern. Real organisations aren’t that tidy.

The edge cases that cause the most confusion usually involve part-time patterns, multiple jobs, and annual leave collisions. Those aren’t rare exceptions. They’re routine for many UK employers.

Part-time workers don’t get a “part-time SSP rate”

This is one of the most common misunderstandings. Teams often assume a part-time worker must receive a reduced weekly SSP amount because they work fewer days.

That isn’t the right starting point. LITRG explains that SSP is payable for the full qualifying days a worker would normally have worked, that part-time staff can still receive the full weekly SSP amount if they meet the eligibility rules, and that employees with more than one job may receive SSP from each employer.

The compliant approach is:

• identify the employee’s qualifying days,
• apply SSP only to those days, and
• avoid inventing a separate “part-time entitlement” rule that doesn’t exist.

Employees with two jobs may have SSP in each employment

Another frequent mistake is treating the employee as if they have one combined SSP entitlement across all work.

They don’t. Multiple employments should be assessed separately. If the employee is employed by more than one employer, each employment can carry its own SSP position. That means one employer can’t assume another employer is dealing with the statutory payment.

HR teams need discipline with records and communication. Your organisation should decide eligibility and payment based on the employment relationship you hold, not on assumptions about the employee’s wider working life.

Separate job, separate assessment. That’s the safest operating principle unless a specific internal arrangement says otherwise.

Sickness during annual leave needs a policy response, not a shrug

The misconception here is usually manager-led. Someone is on annual leave, becomes unwell, and the manager decides it should stay as holiday because the leave was already booked.

That approach is risky. If an employee is sick during annual leave, you need a clear policy route for reporting the sickness, providing evidence where appropriate, and deciding whether the leave should instead be treated as sickness absence. The practical point is consistency. Managers shouldn’t improvise this.

A useful internal checklist looks like this:

• Reporting route: The employee must know how to report sickness during leave.
• Evidence standard: Apply the same evidence expectations consistently.
• Payroll and leave correction: Annual leave records and sickness records must be updated together.
• Manager guidance: Don’t leave case-by-case decisions to local custom.

Where edge cases usually fail

These situations go wrong when organisations rely on memory, email threads, or manager judgement without system support. The law may be nuanced, but the operational answer is usually simple. Keep one absence record, one rules engine, and one source of truth for work pattern and entitlement.

Operationalising SSP in Microsoft Dynamics 365

Manual SSP administration usually starts with good intentions. A shared spreadsheet tracks absences. Payroll has a reference tab for statutory rates. HR keeps fit notes in a folder structure. Managers submit updates by email or Teams message. It feels workable until the first complex absence exposes the gaps.

The issue isn’t only the risk of a wrong payment. It’s that no one can see the whole case in one place. Dates, evidence, working pattern, policy layer, and payroll output sit across different tools.

What a better operating model looks like

In a properly configured Microsoft environment, SSP should be the outcome of connected data, not a manual reconstruction exercise.

That means:

• employee records sit centrally in Dataverse,
• absence is entered once,
• working patterns are already known,
• document management is controlled,
• payroll receives clean output rather than free-text explanations.

A specialist HR layer inside Dynamics 365 is particularly useful. A modern implementation can tie absence management, employee master data, workflow, documents, and reporting into one operating model rather than forcing HR and payroll to bridge gaps manually.

The capabilities that matter in practice

For SSP specifically, the most valuable capabilities are usually the least glamorous:

A strong Dynamics setup can also support fit note handling, approval routing, and return-to-work tasks without HR having to chase every step manually.

Why native Microsoft integration changes the workload

When the HR platform sits inside the wider Microsoft estate, the practical benefits are operational rather than cosmetic. Outlook notifications can prompt action. SharePoint can govern supporting documents. Power BI can surface absence patterns and overdue actions. Power Apps can simplify manager or employee input without introducing another disconnected product.

If your organisation is already in the Microsoft ecosystem, that matters more than adding another standalone HR tool with its own data model and integration burden.

For teams weighing options inside that environment, this overview of Dynamics 365 HR and the wider Microsoft HR landscape is a useful starting point.

What works and what doesn't

What works:

• Rule-based absence recording rather than free-text entries
• Configurable workflows for evidence, approvals, and return-to-work actions
• A payroll hand-off that preserves the statutory logic behind the figures
• Shared reporting so HR, payroll, and managers aren't looking at different versions of the same case

What doesn't work:

• one spreadsheet for dates and another for pay,
• policy PDFs with no system enforcement,
• fit notes stored in inboxes,
• manager discretion filling process gaps.

The wider point is strategic. SSP is only one statutory process, but it's a good test of how well-integrated your HR operations are. If your system can handle sickness absence properly, it usually means your broader HR architecture is in much better shape as well.

Conclusion Future-Proofing Your Sickness Policy

An effective SSP process comes down to a handful of practical disciplines. Capture absence accurately. Apply the rules consistently. Keep evidence and records in one place. Make sure payroll receives clean, traceable data. Train managers so they don't improvise. Most organisations know these principles already. The difficulty is making them work at scale.

That challenge becomes more urgent because the statutory framework is changing. ACAS states that from 6 April 2026, eligible workers can qualify for SSP from the first full day of sickness absence and the lower earnings limit has been removed by the Employment Rights Act 2025. Recent legal commentary also points to broader reform pressure around payroll design, policy wording, and support for lower-paid and irregular-hours workers, including expected changes highlighted by Thrive Law's review of the upcoming SSP reforms.

That means the old “we'll manage it manually” position is becoming harder to defend. Day-one qualification changes process timing. Wider eligibility changes payroll complexity. Policy wording, absence workflows, and manager guidance all need to keep up.

The strategic response

The right response isn't just to update the handbook. It's to build a sickness-management process that is configurable, auditable, and adaptable. If your business is also reviewing wellbeing and prevention measures, it helps to pair statutory compliance work with practical ways to lower staff absenteeism so the policy doesn't only deal with absence after it starts.

Good SSP administration is reactive by necessity, but good people operations are proactive by design.

Why now is the right time

You don't want to wait until a reform date is close and then discover your payroll logic, employee records, policy language, and manager processes all need changing at once.

The sensible move is to treat UK Statutory Sick Pay as a design issue now. Review how sickness is recorded. Review how statutory and occupational sick pay interact. Review whether your Microsoft environment is being used as a joined-up platform or just a collection of disconnected tools.

Organisations that fix this early will be in a stronger position. They'll be more compliant, easier to audit, and better able to support employees through a process that often arrives at a difficult moment.

DynamicsHub helps UK organisations turn complex people processes into workable systems inside Microsoft. We are DynamicsHub. Experience HR transformation built around your business. Hubdrive's HR Management for Microsoft Dynamics 365 is the premier hire-to-retire solution, more powerful, more flexible, and more future-ready than Microsoft Dynamics 365 HR. If you're preparing your sickness, absence, and payroll processes for the next phase of SSP reform, phone 01522 508096 today or send us a message.

Chris Pickles Director / Dynamics 365 and Power Platform Architect & Consultant

Chris Pickles is a Dynamics 365 specialist and digital transformation leader with a passion for turning complex business challenges into practical, high-impact solutions. As Founder of F1Group and DynamicsHub, he works with organisations across the UK and internationally to unlock the full potential of Dynamics 365 Customer Engagement, HR solutions, and the Microsoft Power Platform. With decades of experience in Microsoft technologies, Chris combines strategic thinking with hands-on delivery. He designs and implements systems that don’t just function well technically — they empower people, streamline processes, and drive measurable performance improvements. Known for his straightforward, people-first approach, Chris challenges conventional thinking and focuses on outcomes over features. Whether modernising customer engagement, transforming HR operations, or automating processes with Power Platform, his goal is simple: build solutions that create clarity, capability, and competitive advantage.

See Full Bio

Dynamics 365 Customer Engagement (CE) Dynamics 365 Sales Dynamics 365 Customer Service Digital Transformation Microsoft Power Platform Power Apps Power Automate Power BI Dynamics 365 HR / HR Systems Hubdrive HR Business Process Automation