MYOB Advanced Businesshelp.myob.com.au/advanced/releasenotes/MYOB Advanced Business... · The 2015.3.5 release includes fixes to many areas of the system. The following sections provide

MYOB Advanced Business Release Notes 2015.3.5

MYOB Advanced Business 2015.3.5 Release Notes Page 2 of 15 Copyright 2016 MYOB Technology Pty Ltd.

Contents Introduction 3

What’s New in this Release? ............................................................ 3

Installing this Release ...................................................................... 3

New Features 4

Sending Remittance Advice ............................................................. 4

Matching Multiple AP Payments ..................................................... 6

AP Payment Processing Improvements ........................................... 7

Branch Parameter on Tax Reports ................................................... 7

Resolved Issues 8

Known Issues 15


Introduction Welcome to the 2015.3.5 release of MYOB Advanced Business.

What’s New in this Release? The 2015.3.5 release includes fixes to many areas of the system. The following sections provide details of the changes included in this release.

Installing this Release The 2015.3.5 service pack is automatically deployed to all production accounts.

Note: An updated licence is required to enable configuration options for the new features. While accounts in our managed environment will have their licences updated automatically, a local installation must be updated manually by navigating to the Licence Maintenance (SM.20.15.10) form and clicking the Update Licence button.


New Features Sending Remittance Advice This release adds the ability to process the sending of payment remittance advice, via print or email. A new Send Remittances button is available on the Batch Payments form (AP.30.50.00). Clicking this button opens the new Print / Email AP Remittance Advice form (MB.AP.50.53), which also is available in the Process section of the Accounts Payable module.

Two actions are available on this form:

• Email Remittance: Emails to each supplier will be generated and queued for sending, with remittance advice attached as a PDF. A record of the email will be stored in the activity history for each supplier.

• Print Remittance: Remittance advice reports will be generated and displayed for all selected payments, so that they can be printed out and sent to suppliers.

Remittance advice is displayed on the new Remittance Advice report (MB.AP.60.00). When printing remittance advice, the report is launched directly from the Print / Email AP Remittance Advice form; when emailing advice, reports are generated and attached to the emails.


New Print and Email Settings properties on the Payment Settings tab of the Suppliers form (AP.30.30.00). These settings affect whether or not the supplier will be appear on the Print / Email AP Remittance Advice form. For example, if a supplier does not have the Send Remittances by Email option ticked, payments for them will not appear on the form when the Email Remittance action is selected.

Defaults for these settings can be set on the Supplier Classes form (AP.20.10.00). New suppliers will inherit remittance settings from their class.

A new “SupplierRemittanceAdviceNotification” Notification Template has been added on the Notification Templates form (SM.20.40.03). This template, along with the Remittance Advice report, is specified on the Mailing Settings tab of the Accounts Payable Preferences form (AP.10.10.00), so that they will be used when emailing remittance advice from the Print / Email AP Remittance Advice form.

You can customise the content of the notification template from the Notification Templates form (SM.20.40.03).


Matching Multiple AP Payments It is not uncommon for AR or AP payment batches to be reported as a single line on the bank statement when importing for reconciliation. In previous versions, it is not possible to reconcile one bank statement line against multiple AP payments that were paid as a single payment batch, which required the user to do a lot of manual steps to complete the reconciliation.

In 2015.3.5 it is now possible to reconcile such a batch in the same way the user is able to reconcile a bank deposit. A Match Bank Transaction to Batch Payments check box has been added on the header of the Cash Accounts form (CA.20.20.00):

With this check box ticked, if you process imported transactions on the Process Bank Transactions form (CA.30.60.00) you will see any valid batch payments when attempting to match a bank transaction to an Accounts Payable batch; when selected and processed, the system clears the batch and closes all payments included in this batch. Match criteria for Batch Payments are the same as for payments. Batch Payments must be in the “Released” status.

With the Match Bank Transaction to Batch Payments check box cleared, all payments are displayed on the Match to Payments tab of the Process Bank Transaction form (CA.30.60.00) as separate lines, as per existing behaviour. If any payment from a batch payment is matched and processed while in this mode, the entire batch payment will not be displayed if the user then ticks the check box to use the new feature.


AP Payment Processing Improvements The following interface and workflow changes have been made to improve the processing of AP payment batches:

• After clicking Export on the Batch Payments form (AP.30.50.00), a Save As dialog now appears immediately, so that the export file can be saved without having to go through the Files menu.

• The term “Cheque” has been renamed to “Payment” on various forms, to make the system more uniform in its presentation and to reflect that payments of type “cheque” are both cheques and electronic payments.

Note: If you want to use the AP payment workflow feature, you must to tick the AP - Suggest Next Number option and set the AP Last Reference Number field to “000000” for all Cash Accounts and Payment Methods, so that the system can auto-fill the mandatory Next Check Number field on the Process Payments / Print Checks form (AP.50.50.00).

Branch Parameter on Tax Reports Australian and New Zealand tax reports can now be generated per branch; a Branch ID parameter has been added to the following reports:

• Business Activity Statement / GST Return (MB.TX.60.11) • GST calculation worksheet for BAS (MB.TX.60.10) • Goods and services tax return (GST101A) (MB.TX.60.00) • GST adjustments calculation sheet (IR372) (MB.TX.60.01)


Resolved Issues The following table details the issues that are addressed by this release.

Problem ID Description

123155178826 123094359946 123820746129 123764072802 123764072798 123764072794 123764072776 123764072771

This release improves system performance when logging in to MYOB Advanced.

123421210730 123519711271 123378721360

The Now() and Today() functions in reports returned the date and the time in the server’s time zone. This has been resolved; these functions now return the date and the time in the user’s time zone.

123256390198 123252436116

It was not possible to delete a branch – the delete action on the Branches form (CS.10.20.00) would appear to succeed, but the branch would still exist, and would still be visible on returning to the Branches form. This has been resolved.

124503328830 124346611371

After converting an Opportunity to a Sales Order, it was not possible to save the Sales Order with the type “QT”; the type would be set to “SO”. This has been resolved.

124418451794 124346611301

The NZTaxRegistrationID was incorrectly displayed on the Branch form (CS.10.20.00) for Australian sites. This has been resolved.

123264509324 123213557331

In some cases, a user could not add records to the table on the Relations tab of the entry forms in the Customer Management module because the Contact selector returned incorrect results. This has been resolved.

115807289547 115738140191

The Void action on the Reconciliation Statements form (CA.30.20.00) did not require any confirmation, so reconciliation statements could be voided with a single click. This has been resolved; a confirmation dialog box is now invoked when a user clicks the Void action.

123828353902 123826759013

In some cases, a released reconciliation statement could disappear. This has been resolved; additional verification has been introduced to ensure that released reconciliation statements cannot be deleted.

122384037291 121719907441

Copying and pasting sales orders with a large number of lines took a long time and sometimes resulted in a timeout error. This has been addressed; the copying and pasting of sales orders is now approximately three times faster.

122942484237 122514710616

Prepayments that were applied to a sales order and then voided still reduced the order’s open balance. This has been resolved.

123753503045 123713345942

Publishing a customization project on the partner portal affected the main site because the UseSharedCustomization option was used for instances with multiple nodes on the portal and on the main site. This has been resolved; the SharedCustomizationGroup option has been implemented in the web.config file, which allows for multiple shared customizations in one database


123694459896 123603874762

In generic inquiries, if a Sort Order was applied to selector columns, they would always be sorted by numeric value instead of sorting by text. This has been resolved.

124086012213 123834685281

When a user tried to copy a company by using the Copy Company action on the Companies form (SM.20.35.20), system company 1 was offered as a destination company. This has been resolved.

123421210730 123519711271 123378721360

Incorrect times were appearing on reports that displayed a date and time, despite the time zone being set correctly in the Site Preferences. This has been resolved.

123869303166 MySQL Timeout errors could occur when looking up inventory in a Purchase Order Line or adding inventory to a Sales Order line. This has been resolved.

126228637435 126147129781 124145704014 122628923261 128228327145 128136397661 128145313593 127951968371 126987726399 126586781151 125992192684 125938222432 124145704014 122628923261 121072682234 119756666751

The records in the CATran table could become corrupted if two processes added payment documents simultaneously or if the next reference number in the payment numbering sequence was used by another document. This has been resolved.

124812292585 126092842346 125422846782 124806132177

Stock Item records created by the API could have an invalid GUID for the CreatedByID field. This has been resolved.

120030443518 121238022314 119865002486 119705797341

This release improves the bank reconciliation process by adding the ability to match bank transactions to batches of AP payments—see page 6.

123440385735 123254176672

After using the Copy Company features, accessing the Branches form (CS.10.20.00) on the destination company generated the error message “The specified key does not exist.” This has been resolved.

121705536037 121615990111

This release adds a Branch ID parameter to Australian and NZ GST reports (see page 4).

124177849546 124103626941

When printing statements with consolidated balances on the Print Statements form (AR.50.35.00), the printed statement did not display figures in the aging columns at the bottom of report. This has been resolved.

124812970283 124346611021

An error occurred when making a Discount Code/Sequence combination inactive on the Discount form (AR.20.95.00). This has been resolved.


124812292585 126092842346 125422846782 124806132177

When creating stock items via the Advanced API, invalid GUIDs could be inserted into the CreatedByID field. This has been resolved.

120030443518 121238022314 119865002486 119705797341

Using the Auto Match function on the Process Bank Transactions form (CA.30.60.00) failed for payments that included multiple vendors. This has been resolved.

119199966510 121278384031 118182347881

Quantities specified in project transactions that had been entered on the Transactions (CA.30.40.00) form were not reflected correctly on the Project Transactions (PM.30.40.00) form.

124582450431 124494141601

Notification events did not capture email addresses correctly. This has been resolved.

124925770937 124619163021

The error message “Object reference not set to an instance of an object” could appear when running an import scenario on the Import by Scenario form (SM.20.60.36).

123753503045 123713345942

Customisations published to the Customer Portal also affected the main site, which could cause errors. This has been resolved.

124254102582 123759848116

When the Set Start Date of Tax Year option was ticked on the Tax Agency Settings tab on the Suppliers form (AP.30.30.00), the Start Date of Tax Year field always displayed dates in the US format (MM/DD/YYYY), regardless of the local settings. This has been resolved.

125975362086 125938222261

The error message “Batch Number is not valid!” appeared selecting an existing journal on the Batch List tab of the Recurring Transactions form (GL.20.35.00). This has been resolved.

124812970283 124346611021

Unticking the Active option on the Discounts form (AR.20.95.00) resulted in an error when the discount was saved. This has been resolved.

124658158210 124605286461

An error occurred when releasing a Purchase Receipt with the type “Return” that included a Kit item. This has been resolved.

124626154268 124605286351

In certain circumstances, the system could hang when selecting a Purchase Order on the Purchase Orders form (PO.30.10.00). This has been resolved.

119982188388 119982188386

It was not possible to use the Cross Reference functionality on the Non-Stock Items form (IN.20.20.00) if the item did not have a sub-item. This has been resolved.

124177849546 124103626941

Consolidated statements run from the Print Statements form (AR.50.35.00) did not display the figures in the aging columns at the bottom of report. This has been resolved.

125470868175 125379507461

The error “Another process has updated 'INUnit' record.” could occur on the Stock Items form (IN.20.25.00) when creating a stock item, then saving and changing to another item class. This has been resolved.

126511358656 126021131181

An “Object Reference” error occurred when entering a Purchase Order prepayment in a foreign currency.

125585420568 125347766131

The Automatic Notification form (SM.20.50.40) could be used to created notifications for the confirmation of a shipment, but no notifications would be generated when a shipment was confirmed. This has been resolved.


121164761087 120503747891

Due to improved tax processing by the system, sales orders are now generated faster than they were previously. These improvements also address an issue where processing shipments on the Process Shipments form (SO.50.30.00) with the Prepare Invoice option selected in the Action box could cause a timeout error if it was performed on a large database.

121906191728 121719907816

The Add Order button on the Invoices form (SO.30.30.00) was active for released documents, which could lead to data corruption. This has been resolved.

123009403622 122221104604

If a user applied a debit adjustment to a bill (or a credit adjustment) that was subjected to withholding tax, the tax amount to be posted by the application was set by default to the withholding tax total calculated for the bill (or credit adjustment), which prevented the application from being released. This has been resolved; when a debit adjustment is selected for an application on the Checks and Payments form (AP.30.20.00), the withholding tax amount is set to zero by default for the selected bills and credit adjustments.

123116844889 123116844886

The Refresh Currency Rates form (CM.50.70.00) now uses the UTC version of the effective date.

124467103035 124435904531

It was not possible to assign an item category to an inventory item, if the item had not been saved yet. This has been resolved.

124582450431 124494141601

Automation notifications for expanse claim approval did not pull the addressee email address from the related notification template. This has been resolved.

125585420568 125347766131

When a user tried to add an automated notification for the Confirm Shipment action by using the Shipment Confirmation report, the system did not generate the notification on MySQL. This has been resolved.

124925770937 124619163021

In some situations, clicking Prepare & Import on the Import by Scenario form (SM.20.60.36) caused the error message “Object reference not set to an instance of an object.” This has been resolved.

124269680172 124252535091

This release addresses performance issues that could occur when loading a customer’s details on the Customers form (AR.30.30.00).

123009403622 122221104604

Credit Adjustments could not be applied against Debit Adjustments with withholding tax applied—when attempting to do so, an imbalance/unapplied balance equal to the value of withholding tax would appear. This has been resolved.

123869303166 Under certain conditions, invoking the Copy/Paste or Enter PO Receipt action for a purchase order could lead to a Lost connection to MySQL error or could cause the application to hang. This has been resolved; optimizations have been applied to improve the performance and reliability of these actions.

- If a business account was created from a lead, the first and last names were not transferred from the lead to the default contact in the Main Contact section on the Details tab of the Business Accounts form (CR.30.30.00). This has been resolved.

- Opening the Add Order pop up window on the Invoices form (SO.30.30.00) could cause a timeout if there were a large number of sales orders. This has been resolved.

- The GST101A report (MB.TX.60.00) calculated the amount in Box 11 incorrectly. This has been resolved.


- Bank statements in the OFX format could not be imported if the newline character was missing at the end of the file. This has been resolved.

- The ability to exclude and preserve sensitive snapshot data from company snapshots not working. This has been resolved.

- The default GL control accounts that are included with in the NZ and AU company templates have been extended from two digits to four digits to ease implementation.

- The default financial years in the NZ and AU company templates have been updated. To ease implementation, the financial years set up on the Financial Year form (GL.10.10.00) no longer include an adjustment period and the Belongs to Next Year setting is automatically ticked.

- Released payments that had been partially applied to invoices appeared in the AR Edit (AR.61.10.00) and AR Edit Detailed (AR.61.05.00) reports. This has been resolved.

- The site map did not refresh on the portal after it was modified from the MYOB Advanced site without recycling or reinitialising of the IIS worker process. This has been resolved.

- It was not possible to create a shipment for a sales order if the order included lines with non-stock items that were marked for purchasing, i.e. that had the Mark for PO checkbox selected. This has been resolved.

- When a line of a drop-ship sales order had been linked to a closed purchase order through the PO Link action, the sales order was not updated properly. This has been resolved.

- In certain cases, a discount code from the wrong item price class was applied to a sales order line. This has been resolved.

- When an Accounts Payable bill is created from a purchase receipt or purchase order, the transfer of document lines with a pro-rated discount from the purchase receipt or purchase order to the bill is now performed faster than in previous releases.

- A timeout error occurred on the Item Sales Categories form (IN.20.40.60) if a large quantity of items (more than approximately 80,000) was added to a tree. This has been resolved.

- The Line Nbr. column on the Sales Orders form (SO.30.10.00) was editable instead of being read-only, which could result in data inconsistency. This has been resolved.

- In certain cases, an inventory receipt could fail to be released and a timeout error could occur if the audit history was enabled for the INTran and INTranSplit tables. This has been resolved.

- No negative adjustment transaction was created after the physical inventory count was completed, if the total book quantity of a particular inventory item was zero for the selected warehouse. This has been resolved.

- If a user created a copy of a stock item by using the standard Copy and Paste actions on the form toolbar of the Stock Items form (IN.20.25.00), the data from the Vendor Details tab was not copied. This has been resolved.


- It was difficult to publish under MySQL a customization project created for MSSQL, because of the incompatibility of the SQL scripts. This has been resolved; scripts can now be forwarded to VmSQL (SQL interpreter). The main improvements made to the scripts and interpreter include:

• The –[ VmSql ] annotation has been implemented, which allows a script to be forwarded to the interpreter.

• The alter table statement adds a default value to a column that has a value that is not managed by the applied schema.

• The date format has been changed from d/m/y to the canonical yyyy-mm-dd. • Statements with temporary tables have been rewritten.

- The AP – Suggest Next Number option on the Allowed Case Accounts tab of the Payment Methods form (CA.20.40.00) did not work—the system did not automatically generate the next sequential number in the Payment Ref. box on the Checks and Payments form (AP.30.20.00)—if the Require Unique Payment Ref. check box was cleared for the related payment method on the Settings for Use in AP tab of the Payment Methods form. This has been resolved.

- The value of the Total Cost box on the Issues form (IN.30.20.00) was not calculated correctly for stock items with the Specific or FIFO valuation methods. Also, the value of the Unit Cost box (hidden by default) on the Shipments form (SO.30.20.00) was not calculated correctly for stock items with the Specific or FIFO valuation methods. This has been resolved.

- The currency rate type that was selected for a customer on the Customers form (AR.30.30.00) was not copied by default to an SO invoice. This has been resolved.

- It was not possible to create shipments (with the Receipt operation) for return orders with non-stock kits if the kit components were out of stock. This has been resolved.

- It was not possible to release the landed costs entered in an AP bill for a drop-ship receipt. This has been resolved.

- For a sales order that could not be shipped in full, the Create Shipment action on the Process Orders form (SO.50.10.00) changed the order status to Shipping even if no shipment had been created. This has been resolved.

- In some cases it was not possible to create Sales Order invoices using the API from multiple threads due to deadlock error. This has been resolved.

- A stock item was not listed on the Prepare Replenishment form (IN.50.80.00) if its replenishment source was set to Purchase and the replenishment method was set to Fixed Reorder Qty. This has been resolved.

- It was not possible to filter by the Customer Order parameter on the Process Shipments form (SO.50.30.00). This has been resolved.

- Poor performance of the AR Aged Period Sensitive report (AR.63.05.00) on large datasets was caused by excessive data retrieval of currency-related information. This has been resolved; the retrieval of currency information has been optimized in reports.

- When a user clicked the company logo, the system did not navigate to the home page configured in the user profile. This has been resolved.


- The next execution time was changing randomly on the Automation Schedules form (SM.20.50.20) when a user changed any other setting on that form. This has been resolved.


Known Issues The following Known Issues have been identified in this release.

Partner users visible on some forms User accounts with the licence type MYOB_Partner and the Admin account used exclusively by MYOB are hidden from all other users; they do not appear on user selection lists. However, these user accounts will appear in selection lists on the following forms:

• Event > Attendees (CR.30.60.30) • Role List (SM.65.10.00)

Screens not available in Advanced OnTheGo In the Advanced OnTheGo mobile app, it is not yet possible to drill down on Purchase Orders or Sales Orders awaiting approval from the Approval screen; a “Service not available” message will appear. These pages are not available as of MYOB Advanced 2015.3, and will be added in the next major release.

Documents

MYOB Advanced Businesshelp.myob.com.au/advanced/releasenotes/MYOB Advanced Business... · The 2015.3.5 release includes fixes to many areas of the system. The following sections provide