(A new wiki page is under construction, click here to see if it's available.)

Overview

WebWorkbench integrates with MYOB AccountRight Live Plus and AccountRight Live Premier versions using the MYOB API (AccountRight Premier V19 does not have an API service).  This replaces the previous approach of creating export files which were manually imported into MYOB.
 

The MYOB AccountRight Live instance maybe deployed on a local server, or in the cloud. We highly recommend to set up using local instance. It provides better performance especially for large batches.

A WBInterface database is used to stage the data which is exported from, and imported to, Workbench.

The WebWorkbench application uses the MYOB API to transfer data into and out of MYOB AccountRight Live.

Implementation

Prerequisites

1. Server Edition instance (which includes the  API service) is installed and configured (Client version doesn't work with WebWorkbench) or MYOB AccountRight Online (no need to install AccountRight SE instance).
2. A Workbench database is installed and all required control parameters has been set.
3. Web Workbench minimum version 4.2 (this version doesn't require Interface DB anymore)
4. The latest version of workbench requires .net 4.5.2 and it needs to be installed on a server prior the upgrade. You can download it from here: http://www.microsoft.com/en-nz/download/details.aspx?id=42642

For multiple FinCos on a single Workbench database, multiple MYOB will need to be set up on MYOB Integration screen.  

MYOB export scripts are installed with Web Workbench.

MYOB Integration Setup in WebWorkbench

At this point you need to decide if setting up 

MYOB Online Instance or MYOB Local Instance.

MYOB Online Instance

 

1. Navigate to the Configuration -> MYOB Integration
2. Click Authorize (a new page will be opened in a new tab)
3. Login to the MYOB. Request client's own account to MYOB (email address and password). This is different to the login and password needed on MYOB Integration screen.
4. If successfully logged in you will see a page with a message from MYOB asking you to authorise Workbench to access MYOB. Click on Allow Access.
   
   
   
5. On next page, choose company from the list (If MYOB File is not available, request client to create it first in MYOB or check that the login is valid) and click Next
   
   
   
6. Manually copy values on this page back on WebWorkbench MYOB Intergartion screen (Access Token, Refresh Token, Company ID and Hash)
   
   
   
7. Click Next and close the tab.
   
8. Back on MYOB Integration screen in Workbench, choose a financial company for the imported transactions from the dropdown.
9. On the integration screen Logincode and Password must be a user that does not have my.MYOB account.
   
   It should be a just User name and Password. See example on the screenshot below. (this is Password for a Company File locally - See MYOB company file help for more details). These is what MYOB refers to as Offline login username & Offline password. If the company file is only used online, enter Login: Administrator and no password. 
   If a user and password are being used on the company file, this is set on MYOB Setup Menu/ User Access (note that not all users have access to this menu)
     
   
   
   
10. Provide a 'MYOB Category' and an 'AP Suffix' for exported transactions (See MYOB categories for more details). 
    Most of our clients MYOB category is: WBI
                                  AP Suffix: WB 
11. Click Save
12. Click Test to test connection

MYOB Local Instance

1. Tick MYOB Local Instance checkbox.
2. The Validate option will open a new tab with a list of MYOB instances, each showing a unique Company ID.This Internal Address url is the server where AccountRight API has been installed + /AccountRight. If it shows localhost/AccountRight, but the server is not the server where the WebWB application is installed, then this needs to be changed to the real server name, and not 'Localhost'.
   
   
   
   
    
3. Copy the company ID of your company file and paste it in the setup screen.
   
   
   
4. If your MYOB instance is not shown, it may be necessary to respecify the MYOB Library Location, using the MYOB Set Library Location function.

Try exporting a batch. If you get the error on the screenshot 'Encountered a communication error (http:/localhost...', please follow the steps on this MYOB link to fix it.  The services will need to be restarted after the myob config file has been changed. 

Make sure the API has been updated to the current MYOB version. If it is still pointing to the old version, it will not work. The services will need to be restarted after the change.