Skip to main content
Skip table of contents

2018.1.10 Release Notes


The 2018.1.10 release includes updates to the Payroll module and Secure Authentication onboarding process. It also resolves issues identified in previous releases.

These Release Notes are also available as a PDF document: MYOB Advanced Release Notes_2018_1_10.pdf

New Features

Updates to Payroll

This release includes several updates to the Payroll module.

Automatic STP Status Updates

Australia only

The system now automatically refreshes the status of STP submissions, where previously, submission statuses had to be refreshed manually using the Check submission status button on the Manage STP Submissions screen (MPPP5019). This is does using the standard MYOB Advanced scheduling functionality.

The Check submission status button is still available on the Manage STP Submissions screen, so users can refresh statuses manually if they want to.

Pay Item Selector

The Pay Item selector window now displays the Pay Item Type, making it easier to find the Pay Item you’re looking for. The selector is available on the following screens:

  • Configure Pay Item (MPPP2210)
  • Employee’s Current Pay (MPPP3130)
  • Pay Details (MPPP2310) > Standard Pay tab

Secure Authentication Templates

The system now dynamically selects the Notification Template to use for the onboarding emails sent out when a user registers for Secure Authentication:

  • The “User Onboarding with IDS” template is used for emails to internal users on sites that have been registered for Secure Authentication.
  • The “User Onboarding via InApp” template is used for emails to users of the customer portal, external/guest users and users of sites that have not been registered for Secure Authentication.

This ensures that users receive an email containing the information they need to complete the onboarding process.

Resolved Issues


Problem ID 


168533295343 168294287981

When adding stock items to an opportunity on the Opportunities screen (CR304000), the unit price would be the item's default price, regardless of whether or not there was a sales price. This has been resolved.


The system processed the steps of an approval map in the wrong order if a user took a document off hold, did not save the changes when the document was assigned the “Pending Approval” status, but applied the Approve action to the document right after that. This has been resolved; the document should be saved right after it has been taken off hold.


When a user specified any notification template in the TemplateID box of MailSettings in the Report Designer, the template wasn’t processed correctly on the report processing forms in MYOB Advanced. This has been resolved.


The message “The record has been processed successfully” was not localized on the Validate Account Balances screen (CA503000). This has been resolved.


Systems that integrated with Salesforce did not process incoming notifications about record changes when a real-time synchronization was initiated by an automation schedule on the Salesforce Sync screen (SF205030). This has been resolved.


The Related Entity selector on certain CRM screens displayed entity records even if they were restricted for the current user by row-level security rules. This has been resolved.


On the Users screen (SM201010), when a user filled the fields added by a customization into a notification template, these fields were not displayed in emails. This has been resolved.


When a user of a Self-Service Portal searched for any string in the Search box, the search results displayed sales orders, contracts, and projects related to other business accounts. This has been resolved.


On the Opportunities screen (CR3040PL), stage names in the Stage column could not be localized.


Problem ID 


171954692042 171933732903

 The error message “AuthorizationNotificationTemplateID cannot be null” appeared when saving changes on the Cash Management Preferences screen (CA101000). This has been resolved.

169552621591 169492722471

On the Quick Cheque screen (AP304000), a confirmation message incorrectly appeared when saving if the Payment Ref field had been filled in automatically. This has been resolved.


 A user could change the decimal precision of a currency on the Companies (CS101500) and Currencies (CM202000) screens even if released documents that used that currency existed in the system. This has been resolved.


A P+ transaction for a migrated asset was not marked as released if no Last Depr. Period was specified for a book on the Balance tab of the Fixed Assets screen (FA303000). This has been resolved.


On the Release FA Transactions screen (FA503000), an uninformative error was displayed if a user attempted to release depreciation transactions in a non-chronological order. This has been resolved.


In some cases, after a user edited tax report settings and selected the check box in the Detail by Tax Zones column on the Reporting Settings screen (TX205100), the related tax groups became associated with incorrect lines which led to wrong amounts in the tax report. This has been resolved.


The FA Balance by GL Account report (FA643000) displayed a double balance for any asset that had been previously transferred. This has been resolved.


The Include Reclassified check box on the Account Details screen (GL404000) is now selected by default to improve system performance.


On the Trial Balance screen (GL303010), users could not upload a trial balance of a branch that belonged to a company with branches not requiring balancing, if there were transactions posted to the same actual ledger by other companies. This has been resolved.


If the “Inter-Branch Transactions” feature was deactivated, the system allowed users to apply a bill created under one branch to a debit adjustment from another branch when the branches were linked to different actual ledgers or to the same ledger, but the consolidating branch was not specified for the ledger. This led to a discrepancy between Accounts Payable and the General Ledger in each of the branches involved in the transaction. A similar issue happened in the Accounts Receivable module. These issues have been resolved.


Problem ID 


169960277007 172266540031 172068921361 171931967981 169762106584

In some cases, releasing a sales order invoice could generate the error message “Unable to process unconfirmed shipment”. The related shipment should have been confirmed but would still show the status of “Invoiced”. This has been resolved.

142062901644 141862717951

When you are viewing a lot/serial tracked stock item on the Inventory Summary screen (IN401000), if there was expired stock, the total wouldn't be shown in the Expired column unless the Expand By Lot/Serial Number option was ticked. The Expired amount was also not deducted from the Available amount. This has been resolved.

171979346771 171899283161

The Inventory Valuation report (IN615500) could time out before generating the error “error 0: Lost connect to MySQL server during query”. This has been resolved.

170877169239 170479489281

After updating a stock item’s Valuation Method to “Standard”, running the Update Standard Costs process (IN502000) would pick up the wrong inventory account for the item. This has been resolved.


As a result of a simultaneous run of the release process for invoices and inventory transactions through the Process Invoices and Memos screen (SO505000), inventory registers could retain the Balanced status even though the lines were released. This has been resolved.


When the “Inventory” feature was disabled on the Enable/Disable Features screen (CS100000) or restricted by licensing, sales orders were not cleared when a user selected Prepare Invoice from the Action dropdown on the Process Orders screen (SO501000), if the Amount Billed was reduced during the SO invoice creation. This has been resolved.


On the Update Standard Costs screen (IN502000), the update procedure used an incorrect inventory account for an item, if the Valuation Method and Inventory Account had been changed for the item on the Stock Items screen (IN202500). This has been resolved.


If a lot or serial number was allocated for an item in the Allocations dialog box on the Sales Orders screen (SO301000) and a shipment was created but not confirmed for the line, the validation process on the Validate Inventory screen (IN505000) caused an incorrect calculation of the Available Qty. for this item, because the allocation of the sales order and the shipment decreased the item quantity twice. This has been resolved.


Problem ID 


The following error was displayed when a user attempted to approve a purchase order on the Purchase Orders screen (PO301000): “Cannot insert the value NULL into column ‘Type’, table ‘PMBudget'; column does not allow nulls. INSERT fails. The statement has been terminated.” This has been resolved.

An error occurred on the Expense Claim screen (EP301000) if a user attempted to release an expense claim that contained a modified withholding tax amount while the “Net/Gross Entry Mode” feature was disabled on the Enable/Disable Features screen (CS100000).

This has been resolved; expense claims can now be released without errors. Tax details are copied to the resulting accounts payable bill as is. Expense claims that were created before the update should be deleted and created again.


Problem ID 


172210476618 172273818809 172273818801 172246551071 172231848981 172125981521

If an employee’s Payment Summary Type was updated from “Not Required” to “Individual Non-Business” on the Taxation tab of the Pay Details screen (MPPP2310), the employee would still be excluded from payment summaries for previous financial years. This has been resolved.

172185485934 172235789601 172228466081 172215963811 172183049435 172103900241

The error “Request Software ID failed.” could appear when attempting to send payment summaries to the ATO. This has been resolved.

158003525693 171990340561 167350990191 160427573191 156850396031

In some cases, deduction Pay Items that used the “PAYG” deduction category were using the wrong GL account. This has been resolved.

172183597010 172266540081 172218816941 172103252151

The error message “Phone 1 cannot be null or empty” could appear when attempting to send an STP Update, even though a phone number had been entered for the company. This has been resolved.

172246434087 172231166801 172245934804 172231166808

The message “Please go to payroll preferences screen -> SBR -> Registration tab to request the software ID.” could appear when attempting to send payment summaries to the ATO. This has been resolved.

172247561064 172273819645 172273819645

The error “Object reference not set to an instance of an object” could occur when attempting to send payment summaries to the ATO. This has been resolved.

172236013822 172087734811

In some cases, it was possible to submit Payment Summaries for a financial year after STP had been enabled for that year, resulting in data reported to the ATO being doubled up. This has been resolved.

172194373913 172125981701

In some cases, the system would time out after selecting a financial year on the Create Payment Summary Batch (MPPP5053). This has been resolved.

172236924614 172204088881 

Issues with employees’ Payment Summary Types could result in missing data on Payment Summaries, or prevent Payment Summaries from being created. This has been resolved.

172144081136 172059239831

The filters at the top of the Entitlement History screen (MPPP4400) did not always display the correct results. This will be addressed in a later release; a workaround is to use the filters on the column headers on the main table.

171987711870 171956236861

In some cases, GL postings from the Payroll module did not appear in the system. This has been resolved.

170909443998 170307447791

When an entitlement payment Pay Item used a custom tax rate, then when the Pay Item was used in a pay run, the entitlement movement was not transacted in the entitlement history. This has been resolved.

138976761679 138972289156

When setting up Net Pay Disbursement deductions, the selected General Ledger Purpose had to be of the type “Liability”, which was not suitable for some scenarios. This has been resolved; it is now possible to select General Ledger Purposes with the type “Expense” or “Asset” for deductions.


The settings for payslip password protection on the Payroll Preferences screen (MPPP1100) displayed incorrect formatting for the date of birth year. This has been corrected, so that it is clear that the year is four characters long.

Customer Portal

Problem ID 


171673998862 172277623043 172280586262 171577071811

In some cases, the My Invoices screen (SP402000) did not appear on the Customer Portal when it should have. This has been resolved.

171816153807 171801499741

Portal users could see details of companies or customers belonging to other users by using the global search function. This has been resolved.

System and Platform

Problem ID 


171637591479 171632776801 171597772761 171596663351

The error “Object reference not set to an instance of an object.” Could appear when attempting to export reports to PDF. This has been resolved.

171332164719 170899751612

It was possible for an automated notification message set up on the Automation Schedules screen (SM205030) to stop sending messages, even though the schedule was recorded has having executed. This has been resolved.


If tasks were imported through the Import by Scenario screen (SM206036), some related entities were not imported. This has been resolved.


The data from the extension tables of the BAccount table was deleted when a customer location was deleted. This has been resolved.


Searching in transactions and profiles could return incorrect results. This has been resolved; the logic of retrieving search results has been changed.


The system did not pass currency IDs to a credit card processing plug-in. This has been resolved.


For Version 2 of the interfaces for processing credit card payments, the GET HTTP method could not be used on the opening of a hosted form. This has been resolved.


If a new user had been added to Active Directory, this user was not displayed in the list of users opened by the Add Active Directory User button on the Users screen (SM201010) until an application pool for MYOB Advanced was restarted.

This has been resolved; new Active Directory users now appear in the list after a user clicks Reload AD Users on the toolbar of the Users screen.


Some pages were missed in ARM reports if a report was divided into multiple pages due to a large number of both columns and rows. This has been resolved.


If integration with Azure AD was configured in the system and the user name of an AD user contained the @ character, the system incorrectly assigned access rights to this user ignoring his or her membership in AD groups. This has been resolved.



JavaScript errors detected

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

If this problem persists, please contact our support.