Version: v25.10.01
This release includes several important bug fixes to improve system stability and correct calculation errors,
Audience: Canadian Customers
👉 Please perform the 🔧 Key Actions After Updates: Understanding How Bundle Updates impact roles and Center Tab
Bug Fixes
Payroll Calculations We have fixed a critical issue introduced in a recent update that affected percentage-based calculations. This error caused some percentage-based deductions or contributions to be calculated at a rate 100 times smaller than intended (e.g., calculating 0.03% instead of 3.0%). This has been corrected, and all percentage calculations are now functioning as expected.
Important: We contacted customers we suspected could be impacted individually. It is still worth double-checking if you:
- Ran a PayRun on or after the weekend of 18/19th October 2025 for employees having a percentage based Pay Component Sub Type assigned (e.g. most common RRSP)
- Pay Runs from 24th of October after the update has been released will not be impacted - please check your bundle to see if the bundle has been updated before running a PayRun if you have these percentage based Pay Component Sub Types set up.
Payslip Processing (RRSP) We resolved an error where payslip processing would fail if an "RRSP Employer" pay component was used without an associated "RRSP Package" being set up. The system no longer requires an RRSP Package to be present in this scenario, preventing errors for customers who are not yet using the new RRSP Package feature due to be released later this year.
MyPay / Employee Self-Service (ESS) We corrected an issue where new subtypes related to the "Vacation as $ Amount" feature were appearing by default in the MyPay and ESS portals. These subtypes are now hidden by default. If you wish to make these visible to employees, you can manually update the "Show in ESS/MyPay" setting on the specific subtype record.
RRSP Beta Feature The new "RRSP Package" field on Pay Component records has been temporarily hidden. This field was released prematurely while the feature is still in beta testing and is not yet ready for use. It will be made available again in a future release when the feature is complete.