
Immediate SSP increases payroll liabilities and compliance risk, while the earnings‑limit removal affects part‑time wage structures, making swift adaptation crucial for cost control and employee confidence.
The Employment Rights Act 2025 marks a watershed moment for UK payroll, overturning a decades‑old practice of three‑day waiting periods before statutory sick pay (SSP) kicks in. By mandating day‑one SSP and scrapping the lower earnings threshold, the legislation widens the pool of eligible employees, especially part‑time workers whose earnings previously fell below the cutoff. This shift not only raises the immediate financial exposure for employers but also forces a reevaluation of sick‑pay policies that have long been taken for granted.
From an operational standpoint, the new regime demands rapid upgrades to payroll technology and processes. Automated platforms must be reconfigured to calculate SSP from the first day of absence, integrate the revised eligibility criteria, and ensure accurate reporting to HMRC. Companies that rely on legacy systems risk compliance breaches and costly retroactive adjustments. Moreover, the removal of the earnings limit introduces complexity for multi‑jurisdictional firms, as they must reconcile UK rules with differing international sick‑pay frameworks, making a unified, compliant payroll architecture more critical than ever.
Strategically, embracing the change can become a competitive advantage. Organizations that swiftly implement day‑one SSP demonstrate a commitment to employee wellbeing, bolstering trust and retention in a tight labour market. Transparent, timely sick‑pay payments reduce absenteeism anxiety and reinforce a culture of care. Additionally, proactive compliance mitigates the risk of fines and reputational damage, allowing finance teams to focus on cost‑control initiatives rather than firefighting regulatory gaps. In short, the SSP overhaul is both a compliance challenge and an opportunity to strengthen payroll resilience and employee confidence.
Comments
Want to join the conversation?
Loading comments...