Troubleshooting Common MYOB Errors

Overview

Data being sent from your Astute portal to MYOB will need to meet particular requirements in order to send successfully. You may come across the below common warnings or errors when exporting data from Astute to MYOB. Please click on an error for more information.

• Future Dated Payroll/Invoice
• GL Code errors prior to export (Validation Errors)
• Workplace State Missing
• Error 50X
• Locked Period
• Access Denied
• Job Tracking
• Account Header Not Allowed

Future Dated Payroll/Invoice

The pay runs, invoices or credit notes that appear for export in your MYOB Integration screen will depend on the Report Settings that you have configured. To check these settings, click the Report Settings tab and update the dropdown fields as required.

Please note that if the Show tab is set to 'All outstanding up to today', no future dated pay runs or invoices will appear. 

GL Code errors prior to export (Validation Errors)

The Astute system will validate the data that is included in your filter criteria prior to you exporting. A list of Validation Errors displays at the bottom of the MYOB Integration screen, and will need to be amended prior to completing your export to prevent further issues.

Please note that Validation Errors will not prevent you from exporting data to MYOB. They are listed as a reference for you to amend any incorrect or invalid data prior to export. 

If they are not corrected and your data is exported, you will receive an error message at the top of the screen.

Example Invoicing Error Messages

Validation Error Format: 'Invoice #XX includes invoice items with invalid GL account codes'.

Error after exporting: No valid GL Code found for Pay Category [name of pay item] or No valid Account Code found using the GL Accounts groups. ([Name of Group]).

Example Payroll Error Messages

Error after exporting: Deduction [Name of Item] has a missing [code type] and it is not set in the [name of group] GL Group. (As set in job [name of Job] for employee [name of employee]).

Solution

To correct the error, you will need to add the relevant GL codes in Config > Payroll > GL Groups.

Please also ensure that the relevant GL Group has been allocated to the entity, employee or job (whichever option is being used).

Workplace State Missing

A workplace state is required for a Payroll Journal, regardless of the Payroll Tax liability status. If a workplace state has not been set for a workplace that is included in a pay run, you will receive an error.

This error will mention the first employee impacted, but can also include other employees. All missing workplace states will need to be amended before you can successfully send the journal.

Example error message

Format: Workplace State, used for Payroll Tax calculation, is missing for one or more jobs - including [name of employee] at [workplace].

Solution

Run the Payroll Tax (Historical Data) report for the month that relates to the pay runs you are exporting. 

Sort the report by Workplace State, then click the employee name and navigate to the Workplace Details tab to update their information for any employees who are missing information. At a minimum, you will need to record the Country, State and Postcode in the Workplace Address section. 

Error 50x

Most commonly, you'll see this error as Error 500 or Error 504, but the third digit can be any number. 

This error means that the data has tried to send into your MYOB portal but it timed out during transfer. MYOB only allows a certain amount of time to pass between the export of the data and their software accepting or rejecting it. 

The error may be caused by excess load on MYOB's API due to factors like time of day or high traffic volumes in MYOB.

Example error message

Format: Add GeneralLedger/GeneralJorunal API call for PR62 - failed: Server error response [status code] [reason phrase] [url]

Solution

Retry the export at a time where there is less traffic and MYOB has the resources available to accept the data. MYOB's API is a resource available to all their integrated partners worldwide, so attempting the export at around 4-5:00pm AET means that there is generally more success. 

Alternatively, you can review the size of the data you are exporting and send it in smaller allocations. For example, if you need to send a month's worth of payroll journals, you can break this into separate exports of a week at a time so that there is less information being sent at any one time for MYOB to receive. 

To do this, click Report Settings, and change the Show dropdown to a selected date range. 

Locked Period

The most common reason this error occurs is that a period in MYOB is locked. For example, you may be trying to push through a pay run or invoice from the previous period, but this has already been locked in MYOB so the data cannot be accepted. 

If your data doesn't fall in a locked period, you will also need to check that the data hasn't been manually entered into MYOB. If an invoice has been created manually in MYOB prior to an export which has the same invoice number as the data you are trying to export, this error will sometimes show. 

Example error message

Format: Add Sale/Invoice/Item AP call for [export number] - failed: ValidationError (BusinessEvent_DateOccured_InLockPeriod)

Solution

You'll need to check in MYOB that the period your data falls in is unlocked. If you are unsure on how to do this, please contact MYOB directly. 

If the data you're exported doesn't relate to a locked period, you will also need to check that it hasn't been manually entered in MYOB.

Access Denied

The Access Denied error message means that there is an incorrect password set up for your integration in your Astute portal. If you haven't changed anything in your Astute configuration, this is likely to be caused by the API administrator accounts password changing. 

This error is more likely to occur when you first start to use the integration, but can still occur at any time when you use the integration.

Example error message

Format: Get GeneralLedger/Account call failed: Access denied

Solution

Check the new password with your MYOB administrator and then go to Config > Company Management > select entity > Integration > MYOB Config, and enter the new password > Save. 

Job Tracking

This error indicates that the job tracking for the exported data has failed, with the syntax error indicating that there is invalid syntax associated with the tracking category assigned. 

Example error message

Format: Get GeneralLedger/Job call failed: 01OData Query Error - Please check your OData query. Syntax error

Solution

You will need to check which category you are tracking in Config > Company Management > select entity > Integration, then ensure that the data in your Astute portal and your MYOB portal are exactly the same. If there is a syntax error, you'll need to confirm with MYOB what characters are allowed so that you can update anything as needed (eg hyphens, apostrophes). 

For example, if you track based on sub-entity one (branches) in Astute, you will need to check how your branches have been configured for the entity (Config > Company Management > select entity > Reporting > Branches), and make sure that each branch name is set up the same in Astute and MYOB. 

Account Header Not Allowed

This error occurs when GL Codes in MYOB have been set to 'Header', which is not a compatible selection with the Astute integration

Example error message

Format: Add GeneralLedger/GeneralJournal API call for [export number] failed: Validation Error (BusinessLine_AccountHeaderNotAllowed)

Solution

Any GL Codes in MYOB that have been set to 'Header' will need to be set to 'Detail Account' in the Profile tab for the integration to work.