Relevance: All users
Version release: Silicon 1.101
Planned release to test: 14/11/2025
Actual release to test: 14/11/2025
Planned release to production: 21/11/2025
Actual release to production: November
Overview
This release continues the fortnightly release cycle for moving fast with changes to Silicon, enhancing usability of the new base version.
This functionality will only apply to sites on the Silicon base version of elementTIME unless otherwise stated.
Timesheets
[FEAT] Change unpaid excess time to follow paid excess time pattern. In this release, you can now select the multiplier of the unpaid excess-time. This means it remains unpaid excess time, but you can now report on the value of the unpaid excess time if it had actually been paid. This is to help those councils with outside of award contracts and needing to ensure any changes meet the better off overall requirements.
[FEAT] Add a summary state to schedule modal for work patterns. It turns out sometimes too much information can be a bad thing. Luckily, you can put this information back in the box after you see it. This option reduces the number of fields shown when opening the schedule modal. You can see the summary and then expand if you need to.

[CHORE] Combine excess-time individual records when they are costed to the same cost centre and apply the same rule when not manually overwritten. This means instead of passing through multiple rows to some payroll systems that struggle with it, we can combine excess time rows where the costing and rule data are the same and then pass them through (see above re too much information).
[FIX] Fix issue where payrun details datasource is not getting overwritten by the user ext ID from role assignment, but always getting from user. Now it is using the role ID as it should.
[FIX] Fix period excess-time calculations when there are public holidays in the timesheet. For some users, excess-time calculations were not working when users also had public holidays. Now they do.
Leave
[FIX] Fix forecasting leave realisation when balance becomes available on anniversary. Okay, I will not subject you to another rant on whether staff can use a leave balance to take leave when it is available (because we all know I am right). Instead, I will just say that when forecasting leave, users with balances that ‘become listed as available’ on anniversary will now show as available.
Reports
[CHORE] Rebuild report “Terminated users by payrun range” on Silicon.
[FIX] Fix issue on report “Daily work costing report” where it fails on some days, also when running for all departments.




