Resolved Issues
The 2024.2.1 release resolves a wide range of issues affecting payroll, workforce management and employee self service.
MYOB Acumatica
| Region | Description | Reference |
|---|---|---|
| AU & NZ | The archiving functionality released in version 2023.1 was not working properly. | N/A |
| AU & NZ | When signing in to theMYOB Acumatica mobile app, the MYOB ID option for two-factor authentication was labelled with the logo of a different authentication provider. Now, the MYOB ID option is labelled with a padlock icon. | N/A |
| AU & NZ | The wrong user could be shown as the billing contact on the Licence Maintenance form. | N/A |
| AU & NZ | The remittance advice functionality was preventing you from exporting a batch payment file prior to the batch being released. Now, you can process exports of batch payment files before releasing the batch transaction. | CE00053424 CE00036685 CE00053422 CE00054089 CE00054820 |
| AU & NZ | Users with the Manufacturing User licence type did not have access to the Multiple Production Clock Entry form. | CE00053310 CE00049534 CE00050192 |
| AU | When running the TPAR Summary report (MB.TX.60.40), the Supplier Address 2/City column could be empty even if you had correctly entered the supplier information. | CE00051500 CE00051499 |
| AU | When using TPAR in conjunction with company groups, it was possible for the company group to appear as a dropdown option on several TPAR reports. Company groups will no longer show as an option. | CE00049528 CE00032484 |
| AU | When Debit Adjustments were applied to Bills, and both were selected as applied to TPAR transactions, the debit adjustment would not appear as a line item on the TPAR Detail report (MB.TX.60.41). However, the total value was correctly reflected on summary reports. | CE00046669 CE00042987 |
| AU & NZ | Automated emails could be created and sent out with the password showing in plain text. The templates which allowed this have been replaced and the password will no longer be sent in plain text. | CE00045166 CE00042307 |
| AU & NZ | A consultant with the Partner Support user licences to access a site even if the Allow access to site checkbox wasn't selected. | CE00056066 CE00054994 |
| AU & NZ | An issue prevented you from adding more than one range of matrix items into PI Type. | CE00056624 CE00055731 |
| AU & NZ | When processing matched bank transactions, errors could occur: "Not all records have been processed, please review" and, in the Amount column, "Do you want the system to recalculate the account(s)". | CE00051347 CE00051344 |
| AU & NZ | There were performance issues when creating a batch pick list from the Create Pick Lists form (SO.50.30.50). | CE00050460 CE00050455 |
Payroll
| Region | Description | Reference |
|---|---|---|
| AU | For some employees, the Workcover rate was not calculating correctly when importing timesheets. | CE00052261 |
| AU | For terminated employees, their payslip could show incorrect leave values Accrual this pay and Taken this pay. | CE00050978 CE00050893 CE00053940 |
| AU & NZ | When adding a public holiday for an employee that doesn't work on that day, an error occurred: "Employee does not work on this day". To make resolving the error easier, we've added the employee ID and the non-working date to the error message. | CE00049662 CE00046518 |
| AU & NZ |
Split payments from superannuation batches were showing incorrect journal amounts. |
CE00052492 CE00052858 |
| NZ | After importing leave into a pay run, an employee's average
weekly earnings (AWE) and ordinary weekly pay 4-week (OWP) rates
could calculate incorrectly – e.g. it could be 700 instead of 900,
or it could be 0.00. This could cause an employee's annual leave to
be underpaid. Note:
This issue was originally resolved in the 2024.1.200
release. |
CE00052199 CE00051660 CE00052198 CE00052503 CE00053226 CE00053809 CE00054069 CE00054669 CE00054939 CE00054989 |
| AU & NZ |
If an employee's sick leave entitlement trigger date is earlier than the employee’s start date, then the sick leave entitlement rollover was not happening correctly. |
CE00048705 CE00048704 |
| AU & NZ | When making a GET call in the entitlement API, you could get an error message saying that a table doesn't exist. | CE00052775 |
| AU | When entering PaySuper login details, the password was displayed as regular text. To protect the password, it's now displayed as black dots. | CE00052345 CE00050802 CE00052884 |
| AU & NZ | When using import scenarios to bulk update payroll email settings, notification emails could be sent to the wrong users, instead of being sent to the employees whose settings were updated. | CE00052337 CE00052065 CE00052577 CE00053045 CE00053899 |
| AU & NZ | Users could receive notification emails about payroll setting changes even if business events for this were turned off. The notification emails said that changes were made by different users (including terminated employees) than those who had actually made changes. | CE00052055 CE00051348 CE00052574 CE00052689 |
| AU & NZ | When importing leave into a pay, the calendar on the Employees screen could be used when the calendar on the Pay Details screen should have been used. This could lead to incorrectly paid leave. | CE00051970 |
| NZ | On the Termination screen, the Less total paid in advance field wasn't including all normal payments taken in advance in the current open termination pay. This was because the wrong date was being used in the calculation. | N/A |
| NZ | For annual leave year-to-date (ALYTD) gross earnings, the Termination screen and YTD inspection header calculated the post-rollover contribution of the proportion pay run by using the current employee work calendar, instead of the calendar from the last annual leave anniversary rollover pay run. If the current employee’s work calendar differed from the calendar for the proportion payrun, the ALYTD gross earnings could be calculated incorrectly. | CE00052553 CE00051778 |
| NZ | Column headers on the Employment Info Batch Summary form could display incorrectly, and values could be missing from the columns. | N/A |
| AU & NZ | We've closed support requests for issues that didn't require
changes from MYOB:
|
CE00051883 CE00051038 CE00050730 CE00050731 |
| NZ | On the Employee Details Return form, you could edit some fields that should not be editable. We've made those fields read-only. | N/A |
| AU | On the Pay Details form, an error could prevent you from making changes to an employee's pay details "Could not determine the Tax Scale. Taxation is not properly configured for Employee". | CE00050945 CE00050944 |
| AU | In the SAFF file, termination dates for employees could be incorrect, with end dates earlier than their start dates. | CE00053188 CE00052892 |
| AU & NZ | On the Work Calendar form, unpaid break times weren't being deducted from the total hours per week an employee was paid for. This caused the wrong number of hours appearing in their standard pay. | CE00054995 CE00054824 CE0055983 CE00056317 |
| AU & NZ | Payroll expense allocation calculations could be incorrect. | CE00050031 CE00047610 CE00055155 |
| NZ | Average weekly earnings (AWE) were being miscalculated because pay runs overlapped and an employee's leave start date was incorrectly being used to determine the number of weeks the employee worked. | N/A |
| AU | Changes to payroll email settings were triggering emails but sending them to incorrect users. Additionally, security notification emails for payslip settings changes were not being triggered as expected. | CE00052337 CE00052065 CE00052577 CE00053045 CE00053899 |
| NZ | Overriding the entitlement trigger date to change it from the last rollover date could cause issues with entitlement rollovers. If leave was taken in advance, the calculation for the rollover value could be incorrect. | CE00054687 CE00054686 CE00054720 CE00054958 |
| NZ | Updating the employee leave summary could cause an error: "An unhandled exception has occurred in the function 'MoveNext'. Please see the trace log for more details." | N/A |
| AU | When generating payments for an adjusted pay run, you could get this message: "There are no top-up payments to generate. All employees have less Net Pay in adjusted Pay run PAY-XXXX than in PAY-YYYY." This occurred because MYOB Acumatica — Payroll was comparing the wrong pay runs. | CE00050443 CE00050073 CE00051716 CE00052565 CE00053291 CE00054426 CE00055054 |
| AU | On the Pay Details (MP.PP.23.10) form, we've increased the character limit of the Payment Reference field from 16 to 18. | CE00052921 CE00052712 |
| AU | The wrong number of characters in a payment method reference field was causing submission errors for superannuation batches. | CE00050095 CE00049890 CE00050491 CE00050955 CE00055089 |
Workforce Management
| Region | Description | Reference |
|---|---|---|
| AU & NZ | We've improved performance in workforce management when retrieving payslips from payroll. | N/A |
| AU & NZ | If there was an open pay run in payroll, historical payslips were unavailable in workforce management, including both the web browser and the mobile app experiences. | CE00050012 CE00049551 CE00054278 CE00053531 |
| NZ | When importing standard and scheduled hours from workforce management using the Employee Work Schedule Import screen, the values for the day before the imported date range were being cleared. | CE00051656 CE00051658 |
| AU | When exporting employees by scenario, an error could occur: "Type mismatch in the expression: 'Or'." | N/A |
Employee Self Service
| Region | Description | Reference |
|---|---|---|
| AU & NZ | In employee self service, the Team Calendar screen could take a long time to load. And for some users, the Company Tree Workgroup dropdown wasn't available. | CE00047808 CE00043560 |
| AU & NZ | In employee self service, the Team Calendar screen could take a long time to load. And for some users, the Company Tree Workgroup dropdown wasn't available. | CE00047808 CE00043560 |