Skip to main content
Skip table of contents

2021.2.2 Release Notes - August 2022

New features

New API endpoints

We've added new API endpoints for:

  • timesheets
  • data maps
  • entitlements
  • posting classes
  • General Ledger purposes
  • pay item liabilities
  • pay items
  • pay details
  • organisation employee (employee and employee class).

For more information, see Integrating customer data with REST API.

Originally available as a limited release in 2021.1.400

New Leave Balances Liability report (NZ)

Shows the leave balances and liabilities for all active employees, including the payment rates at a date selected by the user.

Run this report at least once every month to check the rates and balances, and to help with auditing and financial reporting (e.g. end of financial year).

Entitlement Balances report employment date filtering

 We've added three optional columns to the Entitlement Balances report so you can filter employees based on their employment dates and status:

  • Employee start date
  • Employee end date
  • Employee current status
Timesheet pay schedule improvement pilot (NZ)

For those using the employee work schedule within Advanced Payroll (rather than 3rd party software) we're piloting new features to allow you to populate the schedule based on pay items imported from timesheets.

If you want to participate in the pilot please reach out to your MYOB Advanced Workforce Management partner or the MYOB customer service team.

Default pay group change

We've added a warning message to let you know when an employee doesn't have a default pay group set.

Advanced Payroll currently sets the first pay group the user adds as the Default Pay Group on the pay details Pay Groups tab.

Payroll expense allocation improvements

When the Cost Codes feature is enabled on the Enable/Disable Features (CS100000) screen, the cost code value for the new projects records added on the Projects Transactions screen defaults to the default cost code from the Cost Codes screen. This avoids the “'Cost Code' cannot be empty” error when releasing a payroll expense allocation batch.

On the Payroll Preferences screen (MPPP1100), when you select the Allocation Type = "ACC/WorkCover" checkbox with no corresponding row in the main tn system and try to save, you'll get an error "Updating 'Setup' record raised at least one error. Please review the errors.

Payslip generation improvements

To make it faster to process large pay runs, we've added a separate process for generating payslips.

  • A new “Process Payslip” screen is now available for end users which displays list of payrun IDs, employees and status of payslips if generated or not. New screen have list of actions as mentioned below under “Action” dropdown:
    • Email Payslips - When selected will generate (if not generated earlier) and then emails payslips.
    • Email Notification - When selected will generate (if not generated earlier) and then sends email notifications.
    • Print Payslips - When selected, will run the report (wont use saved report if exists) for selected payrun ID and prints the report for it. The user needs to select the Payrun ID from the Summary.
    • Generate Payslips - when selected generates payslips for Payrun IDs where Payslips were not generated. If they've already been generated, then it overrides the previously generated payslips with new ones.

      When generating payslips using the Generate Payslips action on the Payrun Details screen, if at least one employee received a payslip, the following message appears:

    • Schedule option (already available on the previous version of the Process Payslip screen (MPPP5210)) is now available for users on the new Process Payslip screen (MPPP5215) screen, to let you automatically schedule the actions for the list of payruns in the grid. When a schedule is set up it will automatically perform the selected action for all unprocessed payruns in the grid.

Data displayed in grid can be filtered using optional filters like “Payrun ID” , “Pay Group”, “From” & “To” Date Ranges. Further “Show all” checkbox helps to display all payrun ID irrespective of whether payslips are generated or not. Further a dialogue box shows the success/failures of items being processed for the selected action.

  • On Payroll Preferences screen (MPPP1100), under GENERAL SETTINGS - PAYSLIP Settings: a new dropdown “Generate Payslip during” got added which lists “Payrun Completion” which is default option selected and “Payslip Processing”. These options makes payslip generation as option on completion of Payrun which helps to control Payslip generation. When the Payslip Processing option is selected, the system shows the Text “Payslips are only available once they are generated via the Process Payslips screen” next to the dropdown.
  • When user selects new Payslip in Payroll Preference screen and tries to perform below actions, then user is redirected to new “Process Payslip” screen.

    • MPPP3120 Pay Run Details screen Process\Preview Payslips action.

    • MPPP3400 Batch Payments screen Payslips action.

  • In the ESS Payslips screen MPES3014 when the Payslip is not generated for the period and user clicks the hyperlink related to that people then a pop-up with the error “Payslip could not be found for given paydate.” gets displayed.

 Want quick access to the new screen? Use the Edit menu to add the new Process Payslip (MPPP5215) screen into the MYOB Advanced Quick Menu (Site Map).

Until you make this change, the Quick Menu will still have the older Process Payslip screen (MPPP5210).

Allow duplicate TFNs for records for separate companies within a tenant

When user creates Employee Record and go to Pay Details enter the TFN Number system throws an error saying this TFN Number is already in use. System now supports Employees working in more than one company in the same tenant i.e. employer now have the ability in MYOB ADVP system to have multiple employee records in the same tenant but assigned to separate companies since the employee works in 2 companies. These pays can now be processed successfully and reported to ATO via STP successfully.

The TFN and ABN number combination will need to be unique. The TFN can be used for multiple entities as long as it is unique per ABN. There will be two employee records with the same pay distribution details linked to different branches. There will be a bank file for each branch. There is a customization in play to consolidate the bank export files into 1 file, in which case there will be two line items for the employee. This should not impact the validation.

Streamlined superannuation fund switching (Australia)

We've added an option to switch all employees to a new fund, to make it easier when fund names or other details change. This also changes the super fund information for completed pays that haven't been put in a pay super batch. This functionality is for APRA, SMSF funds and also applies if Super is sent via SAFF.

Previously, when the details of a super fund changed, Pay Super created a new fund record in the services fund lookup, with a unique SCFI code. This meant you had to relink all employees using that fund to the new record. You also couldn't add the new fund if it shared a USI, so you'd have to change them to a third fund first. This also meant you couldn't update completed pays before putting them in a batch for pay super without adjusting all the related pays.

Continuous overnight timesheets

Previously, the shifts for employees working overnight were incorrectly split into two.

New changes in system would allow end user to join partial shifts as one single continuous shift based on “treat overnight settings: startsOn/EndsOn/Majority/Portion.” in system as shown below and further a flexibility to consider midnight timesheets as continuous'.

Trigger date changes for AWE/OWP rate lookback (NZ)

Following the Holidays Act 2003, we've removed the dependency on lookback periods start date for AWE/OWP average weekly calculations.

This means that for employees with less than 12 months of continuous employment, the system now looks back at a maximum of 52 weeks until the employee start dates (but not until trigger date) for AWE rate calculations, and at a maximum of 4 weeks until the employee start date (but not until trigger date) for OWP rate calculations.

Improved security

We've made some security improvements to fulfil the requirements of the ATO Digital Service Provider Operational Framework:

  • The number of months in the “Keep Audit History For” field on the Security Preferences screen cannot be set to less than 12, thus preventing any user from deleting the recent audit history from the Access History page.

  • The default number of months for a new site will be set to 84

  • Audit history about published customisations is now always turned on by default and made read-only.

  • The button “Log in as user” on the Users screen that allowed user impersonation is now hidden.

Originally available as a limited release in 2021.1.6.

Resolved issues

List of resolved issues

This table lists resolved support issues and bugs for MYOB Advanced Payroll only. Contact your partner for information about resolved support issues and bugs for other MYOB Advanced modules.

RegionIssue IDsDescription
AU & NZCE00023366After 2020.5 upgrade, changing the Export Scenario setting under Settings for Use in AP tab wiped out supplier payment settings. Issue is now fixed.
AU & NZCE00018929Decimal places displayed for rates for Pay items on Employee’s current pay and Payslip (MPPP6011) do not match. Issue is fixed now and rates should be displayed consistently rounding up to 4 decimal places.
AU & NZCE00024996Change to rates in pay group tab of Pay details screen is not updating current pays - issue is now fixed.
AU & NZCE00022166When employee rate is changed in Pay details screen, pay groups tab and user opens a new pay run then the old rate is being used in current pay rather than picking up the latest rate - issue is fixed.
AU & NZCE00024220After upgrading to 2021.1.3, the default pay group box was not ticked by default. This caused errors when processing payroll and then importing timesheets, adding public holidays and annual leave, and populating the work schedule for employees using the work calendar. Issue is now fixed.
AUCE00020276 Payroll Expense Allocation cannot be released when Project Cost Code is enabled. The improved expense functionality released with this version resolved this issue.
AU -

Customer wasn’t able to Allocate Superannuation Expenses by GL Account but instead system allocates the expenses by Sub Account. Further Hours spent working for different departments for each employees were not been able to be Allocated for Superannuation accounts by department (already selected in Payroll Preferences as time allocation). Issue is fixed.

AUCE00019899 Error Object not set to a reference in the Payroll Expense Allocation tab in the Employees Screen despite successful previous allocations especially for an employee with fixed allocation set-up for expense allocation. Issue is resolved now.

For Reversed pays , users were not able to post/release/back reconcile GL Batch successfully.

Users had GL batches for reversed pays showing posted but on the Bank Reconciliation screen it says the “Unreleased Document cannot be added to the Bank Reconciliation. In few instances GL batches were not even being released. Issue is fixed.

AUCE00017568 Issue where Annual leave accrual is not showing on payslip is fixed.
Entitlement Balances Report now displays the right balances. Further a new Leave Balances Liabilities report has been added into system for checking employee leave balances & leave rates at a point in time.
NZCE00025652Average weekly earnings is not picking up the pay history (i.e. imported pay data) when taking leave - Issue is now fixed.
NZCE00025764Filter on date when user selects Leave Summary report when clicking Leave Summary button from Employee’s Current pay screen was not working - Issue is fixed now.
NZCE00024466Employment Details Return CSV file has incorrect date format for Kiwisaver Opt Out date - issue is fixed.
NZCE00026617Leave summary only displayed either ADP or RDP, not both anymore after the 2021.1.500 upgrade for Public holidays - issue is fixed now.


There was an issue where multiple partial days worked was not returning the correct result of Alternative days. The public holiday worked & related alternative holiday accrued should be based on number of days of public holidays worked. This is now resolved.

When customer is importing Timesheets from 3rd party system, all waged items must be cleared from Standard Pay if they want to use OWP Standard or the higher of Standard and OWP4 weekly rates. This also impacted user’s ability to use Standard Pay as an option for RDP.  Issue is fixed now by stopping the standard pay items automatically loading into current pay and in addition providing users with two new options -

  • Add to Employee’s Current Pay on Pay items screen under the Standard Pay heading. Users can uncheck employees who are paid for this item is paid from timesheets.

  • New setting in the Standard pay items grid Add to Current Pay

NZCE00023186 Very difficult workflow for employees using work schedule for DOW, especially those with highly variable work patterns. Improved timesheet functionality has been introduced in thie release to resolve this issue.





JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.