The following fixes we done relating to backpay with reference value when using timesheets.
Previously, we had a number of issues relating to users using reference values when paying employees, uploading a timesheet for the hours and backpaying the employees. Issues are:
Reference Values are dropped at the time the timesheets are imported, storing only the rate for the reference value. This means that the timesheet no longer knows the rate came from a reference value.
When pay reference values are updated using the import tool or the component setup screen, the pay rate saved to a pay packet will be dropped from the pay component and won't be updated properly - meaning it cannot be back paid correctly.
When backpay calculator is executed, the backpay lines are jumbled up and do not match.
Backpay calculator pulls default rate from the employee’s Details screen, instead of the relevant reference value rate the employee was paid at previously.
With the fixes done, the current behaviour when it comes to the above scenarios are:
Timesheets will store reference values. Note that once timesheet is imported, it is not possible to edit the reference values, hours and/or rate by opening the timesheet from within the pay run. If tweaks are needed, user will need to either remove timesheet, edit timesheet then re-import, or, remove the relevant pay component for the employee in the pay run, then add a new pay component with the correct hours, rate and/or reference value.
When a pay run has reference values manually added to a pay component, any updates to the pay reference values will update the manual pay component's reference value in backpay.
Note that if the values are manually entered in pay packet, the reference value will be dropped. However as the reference value will be picked up by default at employee level, the system will backpay based on the employee level reference value. This works the same for Leave payments.'Rate' will not drop off from components where the reference value is changed. When there is a rate change due to pay reference values updated using the import table, the pay packet will keep what was assigned at the time it was paid
When backpay calculator is executed, the backpay lines are no longer jumbled up and will match.
Backpay calculator will pull the relevant reference value rate the employee was paid at previously.
Note that any pay component paid before our changes, would not be loaded in backpay calculator even if the date ranges are selected as the reference values were already lost.
Existing behaviour:
