Issues resolved in EmpowerHR 2025.1



Forward balance enquiry error: ihelp 537963

iHelp: 537963, 531809 

EMP-9532

Reported by:  University of South Australia (UniSA)


Located at:  

Staff Management > Leave Balances


Issue

A null error occurs when you select a date and click Calculate.


Resolution

We removed a superfluous function call which caused the error so it no longer occurs.

Incorrect allowance amount for multiple employments: ihelp 525377

iHelp: 525377  

EMP-9465

Reported by:   The Kids Research Institute Australia 


Located at:  

  (Employee/Position Information)


Issue

When an employee has multiple employments, the allowance amount is incorrect on the Employee/Position Screen when using the Rate Per Hour field.


Resolution

We changed the calculation so the allowance amount is correctly totalled and multiplied by the employments separately.

Auto increments do not work with a position movement on the same date: ihelp 335680 #12830

iHelp: 335680 #12830 

EMP-5959

Reported by:   Department of Premier and Cabinet (DPaC) 


Located at:  

Tasks > Payroll > Payroll Processing > View Generation Incidents


Issue

Auto increments do not work when a position movement occurs on the same date of the increment.


Resolution

If the system cannot do an auto increment because a movement exists on that day, a warning message has been added to the gather incident messages.

Some averaged (schools) employees are not paid full year leave loading: ihelp 536674

iHelp: 536674 

EMP-9471

Reported by:   Catholic Education Diocese of Bathurst (CEDB)


Located at:  

Background Jobs > Payroll Processing > Pay Calculations > Pay Calculations Control

Tasks > Payroll > Payroll Processing > Pay Calculation Control

Tasks > Payroll > Pay Data Entry > Individual Gather & Pay Calcs


Issue

Some averaged employees who commenced during the school year, and who had less than 20 unpaid Term days, should be paid a full year of leave loading.  As part of the averaged employee's leave loading calculation, the Term Days worked is incorrectly reduced by the number of LWOP (Leave Without Pay) leave days taken in the year.


Resolution

Averaged employees who commenced during the year, and who have less than 20 unpaid Term Days, are now correctly paid a full year of leave loading.

Reversal of (schools) LWOP does not update Christmas scht/schl batch: ihelp 535662, 543297

iHelp: 535662, 543297 

EMP-9470

Reported by:   Diocese of Lismore Catholic Schools (DLCSL)


Located at:  

Background Jobs > Payroll Processing > Pay Calculations > Pay Calculations Control

Tasks > Payroll > Payroll Processing > Pay Calculation Control

Tasks > Payroll > Pay Data Entry > Individual Gather & Pay Calcs


Issue

The Unpaid Leave booking entered for an Averaged Employee receiving a formula payment prior to closing the Xmas Leave Pay Period (12), does not calculate the correct current pay values when the Leave Booking is changed in the next pay period (13).  The issue occurs when To Date is changed from the last day of Term 4 (for example, 20/12/24) back to the 13/12/24, or back to the end of the previous pay period 6/12/24.


Resolution

Now the Ordinary hours held in batch scht, and the Unpaid leave hours held in batch schl, are updated correctly when you change the leave booking and select Yes to Reverse the booking.  Pay Calculation now gives the correct result for the current pay.

LDAP and fallback sign on screens do not display correctly: ihelp 502693

iHelp: 502693 

EMP-8901

Reported by:  City of Greater Geelong, Department of Social Services (DSS)


Located at:  

Self Service sign on screens


Issue

After recent style improvements, Lightweight Directory Access Protocol (LDAP) sign on displays overlapping text, and fallback sign on screen has misaligned fields.


Resolution

We removed extra text from the LDAP sign on screen, and realigned fallback sign on screen fields.

Changing a LSL half-pay booking after close of Xmas leave period causes incorrect calculation: ihelp 543299

iHelp: 543299 

EMP-9539

Reported by:   Catholic Education Diocese of Bathurst (CEDB)


Located at:  

Background Jobs > Payroll Processing > Pay Calculations > Pay Calculations Control

Tasks > Leave > Leave Bookings > Long Service Leave Bookings


Issue

A LSL half-pay leave booking is entered until end of Term 4 for an Averaged Employee receiving a formula payment.  When changing this booking after closing the Xmas Leave pay period, the scht pre-written record is not updated correctly.  This results in an incorrect pay calculation.  For example, changing the TO DATE of the leave booking from 20Dec24 to either 06Dec24 or 13Dec24 calculates an incorrect result. 


Information This issue involves Long Service Leave Days functionality.


Resolution

Changing the LSL Half Pay Leave Booking after closing the Xmas Leave pay now adjusts the prewritten transaction records correctly. The leave booking calculates correctly for the current pay period.

Creation of views - deleted organisation codes appearing: ihelp 447521

iHelp: 447521  

EMP-8282

Reported by:   Penrith City Council

Issue

Deleted organisation codes are appearing in some views.


Resolution

We have changed views so deleted organisation codes are no longer included.

Crossboarding issues: EMP-9505

EMP-9505

Reported by:   Department of Fire and Emergency Services (DFES), Fusion5


Located at:  

Background Jobs > Bulk Data Take-On > Crossboarding > Crossboarding Process

Background Jobs > Bulk Data Take-On > Crossboarding > Crossboarding Approval/Error Fix


Issues

  1. Crossboarding via an API/Take-on file against an employee with one current employment fails if the current employment and position are not provided.
  2. The Crossboarding Approval/Error Fix screen does not remove a record that is successfully crossboarded.
  3. When crossboarding via an API/take-on file, EmpowerHR ignores the musts transaction rule.

Resolution

  1. Crossboarding looks for the current employment and performs the movement against it.
  2. The issue of Crossboarding Approval/Error Fix screen not removing a record that is successfully crossboarded has been fixed.
  3. EmpowerHR now checks the musts transaction rule.

Changing a LSL half-pay booking after close of Xmas leave period causes incorrect calculation: ihelp 543299

iHelp: 543299 

EMP-9608

Reported by:   Schools


Located at:  

Background Jobs > Payroll Processing > Pay Calculations > Pay Calculations Control

Tasks > Leave > Leave Bookings > LS Leave Hours Bookings


Issue

A LSL half-pay leave booking is entered until end of Term 4 for an Averaged Employee receiving a formula payment.  When changing this booking after closing the Xmas Leave pay period, the scht pre-written record is not updated correctly.  This results in an incorrect pay calculation.  For example, changing the TO DATE of the leave booking from 20Dec24 to either 06Dec24 or 13Dec24 calculates an incorrect result. 


Information This issue involves LS Leave Hours functionality.


Resolution

Now, changing the LSL half-pay leave booking after closing the Xmas Leave Pay correctly adjusts the pre-written transaction records.  The leave booking calculates correctly for the current pay period.

Calcs error listing (prrerrs) message is missing: EMP-6310

EMP-6310

Reported internally - Schools (Fusion5)


Located at:  

Background Jobs > Payroll Processing > Pay Calculations > Calcs Error Listing

Tasks > Payroll > Payroll Processing > View Calcs Incident Messages


Issue

The Calcs Error Listing is missing the message, Unable to Determine Loading Salary, which appears on the View Calcs Incident Message screen.


Resolution

The Calcs Error Listing now includes the message.

Cannot remove security template from employee: ihelp 526178

iHelp: 526178 

EMP-9459

Reported by:  David Jones


Located at:  

Administration > System Security > Operator Codes / Functions

Tasks > Employees > Employee Information > Employee Information


Issue

After deleting the operator via the Operator Codes / Functions screen, the associated template still displays on the Employee Information screen's Work Place tab (Operator Template field).


Resolution

This issue has been fixed so when you delete a user’s operator code, you can now change or delete the operator security template associated with the user.

Event notification not sending email to escalation email address: ihelp 538439

iHelp: 538439 

EMP-9502

Reported by:  City of Greater Geelong (COGG)


Located at:  

Background Jobs > Daily Processing > Auto Event Processing


Issue

The event notification does not send email to the escalation email address.


Resolution

Escalation is triggered by the following conditions:

  1. If the Include Escalation box is not selected, escalation triggers when the difference between processing date and due date is less than the number of days in the Escalate Days prior/post Event field (for example, every day, 7 days prior to, or 7 days after, the due date).
  2. If the Include Escalation box is selected, escalation triggers when the difference between processing date and due date is less than the number of days in the Escalate Days prior/post Event days field (for example, 7 days prior to, or 7 days after, the due date) but only for every x days entered in Reminder Notice in Days (rather than everyday).
Information If the Include Escalation box is selected, the Reminder Notice in Days has to be greater than 1 day, otherwise EmpowerHR does not generate escalation email.

Annual leave loading paid - termination pays again: ihelp 487784

iHelp: 487784  

EMP-9075

Reported by:  Catholic Schools Office Lismore Diocese 


Located at: 

Tasks > Payroll > Pay Data Entry  > Individual Gather & Pay Calcs 

Background Jobs > Payroll Processing > Pay Calculations > Pay Calculations Control


Issue

When an Averaged employee is terminated in the final weeks of Term 4, after the Xmas Leave Pay payrun is closed, the Set Up Termination screen incorrectly shows a Leave Loading value.  Leave loading is paid once for the school year and should not be paid again after the Xmas Leave Pay payrun.


Resolution

If an Averaged employee is terminated in the current school year, after the Xmas Leave pay period, EmpowerHR now displays the leave loading amount as zero $ on the Set Up Termination screen.  Pay Calculation does not calculate leave loading again for the terminated employee.

Error running GL interface (DET): EMP-9679

EMP-9679

Reported by:  Department of Training and Workforce Development (DTWD)


Issue:

The GL Interface DET (msidetgl) program crashes while trying to extract the last two digits of the financial year.


Resolution:

We have changed the coding to overcome the issue that was not found in EHR release 2018 or older.

Crossboarding issues: ihelp 541396, 540653

iHelp: 541396, 540653 

EMP-9530

Reported by:   Department of Fire and Emergency Services (DFES), Department of Education, Tasmania, and David Jones


Located at:  

Background Jobs > Bulk Data Take-On > Crossboarding > Crossboarding Process


Issues

  1. When doing crossboarding via API or bulk take-on, the Contract Reason and Contract Expiry Date does not work according to the transaction rule defol (default from previous movement), and the dati format of the Contract Expiry Date might not reflect the date format stored in the database.
  2. When doing a transfer via crossboarding, if the current class level is higher than 01 and the class level column is left blank, the class level of the new movement record is set back to 01 rather than staying the same class level as the previous movement.

Resolution

  1. The dati format field of the Contract Expiry Date is fixed to reflect the same date stored in the equivalent date format field.
  2. Column V (Contract Reason) and column W (Contract Expiry Date) have the following rules:

    1. If the transaction rule defol is set to n and the take-on file has blank data for the columns, then EmpowerHR creates blank Contract Reason and blank Contract Expiry Date for the new movement record, otherwise EmpowerHR populates the fields with non-blank data from the take-on file.

    2. If the transaction rule defol is set to y and the take-on file has blank data for the columns, then EmpowerHR populates the new movement record with the previous movement's Contract Reason and Contract Expiry Date, otherwise EmpowerHR populates the fields with non-blank data from the take-on file. 

    3. If the transaction rule defol is set to y and you still want to make the two fields blank (that is, not populate them from the previous movement's data), then set column V (Contract Reason) in the take-on file to 9999 and column W (Contract Expiry Date) to 99999999.
  3. The issue of the class level setting back to 01 is resolved.

Onboarding - fields not defaulting from class/level: ihelp 550793

iHelp:  550793

EMP-9646

Reported by:   Department of Fire and Emergency Services (DFES)


Located at:  

Background Jobs > Bulk Data Take-On > Position/Employee Data > Bulk Take-On Initiation

Background Jobs > Bulk Data Take-On > Position/Employee Data > Bulk Take-On Process


Issue

When an employee is being onboarded via the Bulk Take-On process, the salary amount and hourly rate in the remuneration table are not defaulting from the class/level, instead the values are set to zeroes.


Resolution

This issue has been fixed.

Error running employee personal data update via API & crossboarding take-on (Oracle): ihelp 545959

iHelp:  545959 

EMP-9690

Reported by:   Department of Premier and Cabinet (DPaC)


Issue

When doing an employee personal data update via API & Crossboarding take-on on an Oracle database, an error ORA-01722: invalid number occurs. 
Information This only occurs on an Oracle database.


Resolution

This issue has been fixed.

RDO request picks up previous year records when calculating balance: ihelp 546546 

iHelp:  546546 

EMP-9648

Requested by:  Department for Education, Children and Young People - Tasmania 


Located at:  Relief and Payments > Rostered Day Off Register


Issue

When an employee who is on the RDO (Rostered Day Off) Register creates a RDO request, the available balance calculation incorrectly includes the previous year's RDOs.


Resolution

To fix this issue, we have:

  • added a restriction so EmpowerHR only includes the current year's RDOs in the available balance calculation
  • removed a restriction so EmpowerHR now allows payment requests for employees added to the register in previous years 

Gender diversity feature: ihelp 534260, 520153 

iHelp:  534260, 520153 

EMP-9448

Requested by:  Department for Social Services, University of South Australia (UniSA)


Located at:  Personal Details > Gender Diversity tab


Issue

Employees are unable to save updates to their personal details when the Gender Diversity tab is turned off.  This occurs because EmpowerHR tries to add a null string value into the system instead of an empty string. 


Resolution

To fix this issue, we changed the default value for fields in the Gender Diversity tab form from null to empty string.








Next topic

EmpowerHR 2025.0.05 hotfix release notes



© 2023 Fusion5. All rights reserved.