header
Release Notes - Version 6.28
Release Date: 04/03/2020
Extended Leave Without Pay Functionality Released
In version 6.28 our new Extended LWOP functionality has been released. The aim of this new tool (which can be found on the Leave Summary Screen) is to manage the leave accrual adjustments required when employees are on LWOP past the 1 week grace period. Previously this has been an entirely manual process in DataPay, where payroll admins usually push out the employees Annual Leave Rule Template by the amount of LWOP past the 1 week grace period - however this was prone to error.
The new system simply requires admins to enter in dates of Extended LWOP and DataPay will calculate and make adjustments automatically.
For a full set of instructions and additional information on this new functionality, please see the DataHelp page for Extended LWOP.
Tax Changes 2020-2021
ACC Earners Levy | ACC Earners Levy maximum liable earnings threshold has been increased from $128,470 to $130,911 for Pay Runs with a DC date on or after 01/April/2020 |
Student Loan | Student Loan annual repayment threshold has been increased from $19,760 to $20,020 for Pay Runs with a DC date on or after 01/April/2020 |
Reversing & Adjusting from 2019-2020 Tax Year | When Reversing and Adjusting a Pay Packet from financial year 2019-2020, but with a DC date now in financial year 2020-2021, a warning message will display to tell the user to remove and re-add the Tax Details component to ensure that the correct tax rates and thresholds will be applied. |
New Functionality
Extended Leave Without Pay | New functionality to help payroll admins manage Extended LWOP has been released. For more information please see the main article on Extended LWOP. |
CitiBank Bank File | Citibank Bank Files generated from DataPay will now have a DC date specified for bulk direct credit amounts |
PAYE Intermediary Component | When companies switch to our PAYE Intermediary service, they occasionally need to Reverse & Adjust pay packets from before they started with this service. As the original Pay Packet did not have the PAYE Intermediary Deduction component, the Adjustment wouldn't either, resulting in a miss-match between the IR345 report and the amount paid to the PAYEI team and requiring manual intervention. Going forward the PAYE Intermediary Deduction will be automatically added to Adjustment Pay Packets if required, and the Original Deduction field set to the correct value. |
China Construction Bank | Bank account numbers from China Construction Bank are now accepted. |
Company Controls Listing Report | Improvements have been made to the Company Controls Listing standard report. A "Total Pay" column has been added, asterix ( * ) is now used to signify a component which Direct Credits, and a Banking Reconciliation section has been added to the bottom of the report. |
Fixes
Saving Permissions in DataHR | Changes to system level default template and document permissions have been disabled when there is a company defined (override) template in use. |
Unable to Open Pay Runs | An exception could be thrown when a user attempted to create a new pay run due to bad employee rule template data. The cause of this incorrect data has been corrected. |
Back Pay Row Ordering | Rows within the Back Pay calculator screen were not always in chronological order, which could make finding a particular period difficult in a large back pay. This has been corrected. |
Timesheet Hours | Hours in the timesheet could be wrong where multiple employees had pay rate changes mid period and hours were imported for those employees. |
MyPay Manager/Admin Timesheet Screen | The MyPay Manager / Admin timesheet screen was not loading if timesheet values were linked to components which had been made inactive. |
Adjustments of Adjustments | The Amount to Recover value in Reversal & Adjustments of Adjustment Pay Packets (a Pay Packet which had already been adjusted once before) would be incorrect, leading to over-payments to employees. |
YTD Values on Reports | TYD values for components on Standard Reports were being reset to $0 when the component was edited by modifying its attributes. This has been corrected. |
footer