Introduction

Release Date: October 2025
Version: 2.4.0

• This release delivers powerful enhancements enabling support for multiple contractual sick pay schemes with variable benefit entitlements based on length of service

• Changes to authentication to allow bearers of a JWT created by CSI to access their own employee data using the hub endpoints. This supports MyPay integration

• Enhanced compliance for AHP imports based on customer feedback
   

Contents

• Occupational Pay Schemes (OPS)
• Average Holiday Pay (AHP)
   

New Features

Occupational Pay Schemes (OPS)

Overview

• This release supports Occupational Sick Pay schemes - Occupational Parental leave is coming soon

• OPS allow companies to pay all or part of an employee’s salary during periods of absence.

• Multiple schemes can be configured to suit different employee contracts.

• Employee entitlement within a scheme is determined by their length of service.

Key Features

OPS Management

• OPS can be created, viewed, and edited via the UI under Company Setup → Occupational Pay Schemes.

• Each scheme requires a name and supports a single Leave Type (e.g., Default, Sick Leave).

• Schemes define one or more entitlements.

Entitlements

• Entitlements specify the benefit paid during absence and are based on length of service (from start or continuous service date).

• Length of service can be measured in days, weeks, months, or years.

• The system prevents conflicting length of service settings (e.g., 52 weeks vs. 1 year).

• Entitlement behaviour can be set to calculate from the first day of absence or the actual day of absence, affecting eligibility during ongoing absences.

Sick Entitlement Payment Methods

• Four calculation methods: Rolling window, Fixed window, None, or All.

  • Rolling window: Payments depend on absence days within a set period (e.g., 12 months). A 12-month rolling window is common, granting entitled pay days in any 1-year period from absence start.

  • Fixed window: Absence days counted from a fixed date. This can be 1st January, Start of Company sickness Year, Start of tax year, start of school year etc

  • None: No OPS payments.

  • All: All absence days topped up to full pay.

• For rolling/fixed windows, benefits can be defined in weeks or days, and are converted based on the employee’s working pattern.

Statutory Payments

• OPS payments are in addition to statutory payments, but total payment is capped at the employee’s salary.

OPS Matching & Filters

• Multiple OPS can exist for the same leave type, supporting different contracts.

• Filters (pay frequency, department, analysis fields) determine which employees are matched to a scheme.

• Blank filters match any employee.

• Tie-breaking: The most precise match wins; a priority field can resolve equally weighted matches.

Date Range

• OPS can be enabled or retired on specific dates to support future changes.

Applying the Scheme

• When creating or editing an absence, the matching OPS is selected and displayed.

• Absences created via API are matched to OPS at creation or update.

• Existing absences are not updated automatically when a new OPS is created.

Limitations

• Currently, only sick absences are supported; parental leave support is coming soon.

• Employees must have an active salary during absence.

• Employee pay elements continue during absence.

• OPS that have been used can later be deleted.

Notable Discussions & Clarifications

• If both start and continuous service dates exist, continuous takes precedence.

• If an OPS is made active while absences are ongoing, existing absences are not updated.

• There is no explicit limit to the number of analysis fields, but usability concerns were raised for companies with many fields.

• Filtering currently supports Leave Type and Pay Frequency; Department and Analysis fields are not planned for filtering in this release.

• OPS that have been used can be deleted, but this may be reviewed in the future.

• If an OPS is enabled or retired during an absence, the effect depends on whether the start or end of absence is used for calculation.

Average Holiday Pay (AHP) 

Overview

• Average Holiday Pay (AHP) ensures employees can take holidays without financial penalty.

• AHP is calculated based on the average weekly earnings over the past 52 normal ‘worked’ weeks (up to 104 calendar weeks).

• Only weeks where the employee was paid and did not take holiday or receive statutory payments are considered.

Pay Elements Configuration

• Pay elements now have three configuration options affecting AHP:

  • Include: Payments are included in total earnings.

  • Exclude: Payments are not included in total earnings.

  • Veto: If present in a pay period, the entire period is excluded from the calculation.

• Changes to pay element configuration will affect all historic and future calculations.

Reporting Enhancements

• The Average Holiday Pay Report is available for each pay run, showing:

  • Employee details

  • Total eligible earnings per pay period

  • Weekly AHP rate at the time

• Pay periods with no value indicate non-normal periods (e.g., no earnings or vetoed payslips).

• The report is accessible from the payroll reports section or the pay run report tab.

Viewing Current AHP Rate

• Users can view the current weekly and daily AHP rate for an employee by clicking the AHP Rate button when editing payments.

• Rates are displayed based on the employee’s work pattern.

Paying AHP

• AHP payments can be made via UI, import, or API using a pay element with the Average Holiday Pay calculation type (default ID: ahp).

• Users provide only the quantity; the value is calculated automatically based on the current AHP rate and the employee’s working pattern.

Importing Historic Data

• Historic data can be imported to support AHP calculations:

  • Full Import: Per period earnings for every normal period.

  • Partial Import: Import the AHP rate as of the migration date and the number of weeks it applies to.

• System figures take precedence over imported data.

Non-Weekly Pay Periods

• For employees paid on non-weekly schedules (monthly, quarterly, semi-annual, annual), the system converts pay to a weekly value using specific formulas.

Limitations

• AHP rate calculation is not supported for employees who have moved between pay runs of different frequencies.

• Only one AHP scheme is currently supported, but there is potential for multiple schemes in the future.

• All AHP pay is made at the same rate; additional holiday at a different rate must use a separate pay element.