What's New
Notifications - configurable advance warning for age and service milestones
The notification setup screen now supports a two-part trigger: an offset from a milestone date (such as a birthday or service anniversary) and a separate advance warning period. This makes it possible to configure notifications such as "alert me 3 months before an employee's 18th birthday" for the first time.
Previously, the notification screen only supported a single instruction — a number of days, weeks, months, or years before or after a date field. This made it impossible to configure a notification that required counting forward from a date (for example, 18 years from date of birth) and then issuing an advance warning (for example, 3 months before that point).
A second field is now available on the notification setup screen, allowing the following types of notification to be configured correctly for the first time:
18th birthday for National Minimum Wage — alert 3 months before the employee turns 18.
21st birthday for National Minimum Wage — alert 3 months before the employee turns 21.
Length of service (5 years) — alert in advance of the 5-year service anniversary.
Length of service (10 years) — alert in advance of the 10-year service anniversary.
⚠️Important: Existing notifications of these types will need to be reviewed and reconfigured in Setup, click Content, then select Emails to take advantage of the new offset field.
Notifications that were previously set up with a single trigger against the raw date field (for example, date of birth) will not automatically update.
Bug Fixes
Payslip notification email – [Person.Firstname] field not populating
How to access:
Go to Setup, then click Content.
Click Emails, then select HR.
Click Security Details, then select Payslip Notification.
The [Person.Firstname] replacement field in the Payslips Notification email template was not being substituted with the employee's first name. Employees were receiving the notification with a blank space where their name should have appeared.
The field substitution has been corrected. Payslip notification emails now include the employee's first name as expected.
Final holiday pay – 'Get Balance' under-reporting for mid-week leaving dates
How to access:
Go to HR, then click Termination.
Click Get Balance/ Final Holiday Pay.
When processing a termination for an employee with a mid-week leaving date, the Get Balance calculation was under-reporting the accrued holiday balance. The system was reading from weekly leave accrual rows, which only exist for completed weeks, meaning any days accrued in the current part-week up to the leaving date were not included. The result was a final holiday pay figure that was too low, regardless of when the calculation was run.
The calculation has been updated. For leavers, if the leave accrual rows do not cover the termination date, the balance is now pro-rated to the exact leaving date. The final holiday pay figure is now consistent however many times it is recalculated, and no longer depends on the overnight accrual job having run.
Holiday entitlement round-up setting – rounded balance rejected on mobile app
How to access:
Go to the Mobile App, then select Absence.
Select Holiday Booking, then select Configuration.
Select Settings, then select Holidays and Leave Accrual.
When the Holiday Entitlement: Round Up setting was enabled, the system rounded an employee's available balance up to the nearest whole day (for example, 2.66 days shown as 3 days) in the People UI. However, when the employee attempted to book those 3 days via the mobile app, the request was rejected with a message stating their entitlement had been exceeded.
The entitlement check used during mobile leave booking was reading from an unrounded internal value rather than the rounded figure displayed to the employee. This has been corrected. When the Round Up setting is on, the entitlement check now uses the same rounded value the employee sees, and bookings up to that figure are accepted.
📌Note: Customers with the Round Up setting off are unaffected.
PDF payslip – Employers Contributions section rendering outside payslip table
How to access:
Go to Payroll, then select Payslips.
Click PDF View.
Where a payroll administrator had added an Employers Contributions section to the payslip configuration, the section was rendering outside the bounds of the payslip table in the PDF printable version. The heading was partially obscured by the table above it, and the content appeared in the lower right corner of the page rather than in the correct position within the payslip layout.
The PDF payslip template has been corrected. The Employers Contributions heading and its rows now render within the payslip table in the correct position.
Email notifications not sending for NMW and length of service milestones
How to access:
Click Setup, then select Content.
Click Emails, then select Notifications.
Automated email notifications for the following milestones were not being sent:
18th birthday for National Minimum Wage.
21st birthday for National Minimum Wage.
Length of service (5 years).
Length of service (10 years).
The root cause was a configuration limitation: these notifications were set to trigger a number of months before the employee's date of birth or continuous service date directly, rather than before the age or service milestone. Because no employee has a date of birth in the future, the daily search found no matching records and sent nothing.
This release adds the two-part offset field described in the What's new section above, which makes it possible to correctly configure these notifications. Existing notification records will need to be updated in Setup > Content > Emails to use the new offset configuration.
⚠️Important: See the What's new section for full details on reconfiguring these notifications.
How this version will be made available
Version 2.74 is deployed automatically. No action is required to receive this update.
If you have any questions about this release, please contact the Access Education People support team.