A new Working Hours column is now available in the Absence & Leave data set within Custom Reporting.

Who is this for: HR administrators reporting on hourly leave

For organisations where employees book leave in hours rather than days, the existing Working Days column did not provide sufficient information. The new Working Hours column displays the hours value recorded against each absence and appears to the right of the existing Working Days column.

How to access:

1. Navigate to Access Reports > Custom Reporting

2. Create or edit a report using the Absence & Leave data set

3. Select the Working Hours column from the available fields

Holiday records now display consistently across the rota for all employees, regardless of whether leave was booked in days or lieu days.

Previously, employees who booked holiday using lieu days were shown differently in the rota view compared to employees on standard holiday bookings — in some cases showing no hours and a different icon. The display logic has been corrected so that all holiday records render consistently.

Area: Rotas > [Rota Week] > Bonus tab

In the Bonus tab within a rota week, column content was misaligned in the UI, making the tab difficult to read and use. This affected customers with the Bonus tab feature enabled.

The layout has been corrected and all columns in the Bonus tab now display in alignment.

Area: Reports > Standard Reports > Rota Hours

Running the Rota Hours report for certain date ranges or sections was returning a 500 Internal Server Error, preventing the report from generating. The issue was reproducible for specific rota sections and date ranges.

The server-side error has been resolved. The Rota Hours report now runs successfully for all accessible sections and date ranges.

Area: Self Service > Timesheets

When an employee performed a timesheet copy operation, the page became unresponsive and crashed due to a JavaScript binding conflict. The user was required to refresh their browser, losing any unsaved work. This was particularly disruptive for employees with recurring schedules who use the copy function regularly.

The root cause — a JavaScript binding being applied to an element that already had bindings from the previous render — has been corrected. The timesheet copy operation now completes without crashing the page.

Area: Timesheets / Borrowed Employees

When an employee was borrowed into multiple departments and shifts were entered across those departments, the system correctly warned of a shift conflict on initial entry. However, when the timesheet was subsequently updated, the conflict check was not re-applied, and overlapping shifts could be saved, resulting in overstated hours.

The overlap validation check is now enforced consistently on timesheet update as well as initial entry. The system will prevent overlapping shifts from being saved for borrowed employees across departments.

Area: Recruitment > Vacancies

Users assigned a role with only View permissions on Vacancies were able to edit and delete vacancy records, despite the Edit and Delete controls appearing as disabled (shown with a red cross) in the UI. This was a permissions enforcement gap between the UI state and the underlying actions permitted.

Permission enforcement for Vacancy management has been corrected. Users with View-only permissions can no longer edit or delete vacancies.

Area: Recruitment > Vacancies

When attempting to change a vacancy from Internal to External, two error messages were displayed and the change could not be saved. Attempts to close the vacancy via the advert duration field or the ‘Close Vacancy’ button were also unsuccessful.

The error preventing internal-to-external vacancy changes has been resolved. Vacancy type changes and vacancy closure now work as expected.

Area: HR > Absence > Leave Admin permissions

Users assigned a role with only ‘Can View’ and ‘Can Delete’ Leave Admin permissions were able to add and amend leave records on behalf of other employees via the Absence tab. The expected behaviour is that adding or amending another employee’s leave requires the explicit ‘Can Add’ or ‘Can Update’ permission to be enabled.

Permission enforcement for Leave Admin has been tightened. Users without ‘Can Add’ or ‘Can Update’ permissions can no longer add or amend leave records on behalf of others.

Area: HR > Mail Merge Templates

In mail merge templates that included both Additions1_AdditionDeductionDescription and Additions2_AdditionDeductionDescription fields, the Additions2 field was returning the same value as Additions1 rather than the description for the second addition line. This resulted in incorrect salary statement output for employees with more than one addition to basic pay.

The field mapping for Additions2_AdditionDeductionDescription has been corrected. Both fields now return their respective values independently.

Area: HR > Mail Merge Templates

When using the Latest Effective Salary field in a mail merge template, the merge was returning the correct effective date from the most recent salary record, but the salary amount was being pulled from the previous salary record rather than the one associated with that date.

The salary lookup for the Latest Effective Salary field has been corrected. The effective date and salary amount now correspond to the same record, and the most recent salary value is returned correctly.

The ‘Get Balance’ calculation used during the termination process has been updated to ensure that final holiday pay is calculated accurately for employees with a future leaving date.

Previously, when an employee’s termination date was set in the future, the system calculated accrued holiday only up to the current date rather than to the leaving date. This caused the final leave adjustment to under-report the balance the employee would have earned by the time they left. The calculation now pro-rates accrual accurately to the exact leaving date, regardless of when the button is pressed or whether the overnight accrual job has run.

Employees who have already left and employees on zero-hours contracts are unaffected by this change.

Area: Mobile App > Rota View / Absence

Final Holiday Pay absence records — which carry no specific dates — were being displayed to employees on the mobile app rota view, appearing against any day where no shift was scheduled. This was confusing and misleading for employees who had a future position end date but had not yet left.

Final Holiday Pay records are now suppressed from the employee-facing mobile app, desktop, and mobile site views, as intended.

Area: Self Service > Expenses

When attempting to change the category of an existing expense entry, the page threw a JavaScript error and the operation failed. As a workaround, employees were having to delete and re-create expense entries to correct the category, causing delays to expense processing.

The missing JavaScript function reference has been restored. Expense category changes now work correctly.

This version will be automatically applied from 14th August 2026.