Statutory sick pay in the UK changed in April 2026. The three-day waiting period went. Day-one entitlement arrived, and lower-paid employees became eligible for SSP calculated against earnings rather than excluded by the old earnings threshold. For multi-site employers in London running retail sites, hospitality venues, or distributed service teams across boroughs, those changes landed on absence processes that were already stretched.
The businesses most affected are those still running absence tracking through site-level spreadsheets or email chains. When payroll needs to apply the lower of the flat weekly rate or 80% of average weekly earnings across ten locations with varied contract types, fragmented records are not just inefficient. They are a compliance risk.
Why do the April 2026 SSP reforms create more pressure for multi-site employers?
Flat-rate SSP had one number applied everywhere. The April 2026 model works differently. Payroll teams now need to know whether the flat rate or 80% of average weekly earnings applies for each individual worker. Shift-based staff, part-time workers, zero-hours workers. All different. All requiring individual assessment.
Day-one entitlement removes the buffer the waiting period provided. Short absences that previously fell below the threshold now need to be recorded, assessed, and processed from the first day. For a retail group running ten London sites, that volume hits HR and payroll simultaneously.
HMRC can ask for accurate SSP records where evidence is needed. Manual spreadsheets split across locations make producing a clean audit trail slow and unreliable. Each site develops its own recording habits. Version-control problems follow. Discrepancies appear at payroll run, when fixing them costs more time than preventing them would have.
How does fragmented absence data create payroll and compliance risks?
When absence data sits in separate systems at each location, inconsistencies build over time. An absence logged at one site may not reflect an updated return-to-work date. Another location may have missed a fit note requirement. These gaps compound across a workforce of any significant size.
Sickness absence records can include health data, which falls under special category data under UK GDPR. Stricter obligations cover collection, storage, and access. Spreading that data across disconnected files and inboxes makes documenting data-handling practices harder and raises regulatory exposure.
Operational planning suffers too. A site manager making shift coverage decisions without visibility of absence levels across the wider business is working with incomplete information. That produces understaffing at some locations and unnecessary overtime costs at others. Both become easier to prevent when absence data is visible across the business.
What does a centralised absence management system actually do?
One platform replaces the spreadsheets. Absence data from every location sits in the same place. HR and payroll teams access it without chasing site managers, without downloading conflicting files, without reconciling versions that drifted apart.
For London employers navigating the post-April 2026 SSP landscape, absence management software gives HR teams one platform to manage absence records, SSP-related data, and payroll integration across all sites. Current employee data sits with the absence record, so payroll teams are not rebuilding SSP calculations from scattered files.
Audit trails are built in. Every absence entry, approval, and amendment is logged with a timestamp. When HMRC requests records or an internal compliance review requires documentation, the data is already structured and ready.
Holiday management software integrated with absence tracking prevents a specific problem that multi-site employers know well: annual leave requests that clash with existing sickness absences or leave gaps at individual locations. Clashes get flagged inside the system before the rota is affected.
How does payroll integration change the day-to-day for HR teams?
Approved absences feed into payroll calculations directly. No manual re-entry. Under the April 2026 SSP model, accurate absence and earnings data in one place reduces the manual checks payroll teams need to make around average weekly earnings for each individual worker.
Routine steps become easier to control. Absence notifications, fit note tracking, eligibility checks, payroll updates. HR teams that spent hours reconciling absence records across sites get that time back.
Finance managers gain real-time cost visibility. Sick leave updated at one site adjusts labour cost projections across all locations at the same time. For London businesses running tight margins across multiple boroughs, that visibility matters when decisions need to happen quickly.
What should London businesses consider when evaluating absence management software?
Employee absence management at multi-site level needs more than a basic leave tracker. GDPR-compliant data governance, configurable retention periods, role-based access controls, direct integration with existing payroll and HRIS systems. Operational requirements, not optional features.
Data migration, staff training across multiple locations, and support arrangements all determine whether the switch delivers value quickly or creates temporary disruption before it settles. Worth mapping before any platform decision is made.
For London employers managing shift workers, part-time staff, and zero-hours contracts across distributed teams, the case for centralised absence tracking strengthened in April 2026. The SSP changes were not just a payroll update. They were a prompt to check whether current absence processes can handle the complexity now sitting inside them. Businesses that fix those gaps early spend less time chasing records, correcting payroll and managing compliance pressure across sites.
Leave a Comment