MYOB AccountRight FAQs

Questions:

Invoices not turning up in MYOB even though export looks successful

Answer:
If the client can’t find the invoice in MYOB but the ExternalID of the invoice is populated in Workbench, it most likely means that an invoice with that number already existed in MYOB with that number (probably for another supplier). The integration will not export the Workbench invoice if it finds an invoice with a matching number already exists in MYOB because it assumes the invoice has been manually created by the client in MYOB.

Workbench needs to be the only source of invoices in MYOB, so the client shouldn’t be creating invoices manually.

If the client wants to try the export again they need to un-export the batch and then un-export the AR invoices (using utilities), and then either give the invoice in Workbench a new unused number, or delete the invoice with that number from MYOB.


Errors:

“BusinessLine_AccountHeaderNotAllowed”

 

Solution:
This means that the invoice lines have been coded with ‘header’ GL codes (i.e. it has children GL Codes). Only non-header GL Codes should be used (see highlighted below). header accounts such as 6-0000 and 6-1000 are just virtual GL codes that group together actual GL Codes, so they can't be used on transactions

 

'Please, specify at least one category in MYOB'

Solution:

This means that the MYOB API cannot find the Category specified in the Workbench integration screen on the MYOB instance that WB is connected to.

  1. Verify that the Category Name in WB and MYOB AR are the same.

  2. If it does exist and is exactly the same, then you have probably connected to the wrong Company File (MYOB Instance). Sometimes Company file names are confusing and the wrong one might be chosen to establish the connection to. Check that you have the right Company ID.

 

‘Timesheet for Employee No [XXXX] on [DD-MM-YYY].The PayrollCategory supplied is not acceptable for this operation. Encountered a validation error…’

Solution:

This means that the timesheet includes lines with non-wage payroll categories (e.g. ‘Personal Leave’, which as an entitlement payroll category). The integration only supports wage payroll categories. (See: https://webwbdoc.atlassian.net/wiki/spaces/DOC/pages/2202468357)

Fix/remove the payroll categories in Workbench and re-export.

Note: this could be an issue with caching, where Payroll Categories in MYOB got renamed or recreated, but the old IDs are still cached in Workbench. So if the error persists, delete the Financial Company’s setting value for the "MYOB Payroll Categories" Setting. This will cause the setting value to be repopulated with up to date Payroll Category IDs the next time the client export does an export.