Troubleshooting MYOB Error Messages
[[BusinessEvent_DateOccurred_InLockPeriod; DateOccurred:(PurchaseEvent); BusinessEvent_DateOccurred_InLockPeriod; InventoryDateOccurred:(PurchaseEvent)]]
Translation: Locked Period in MYOB
If you are trying to export to a locked period, you will be presented with this message.
Please check your MYOB file to ensure that you are not trying to export a bill dated in a locked period.
[[UID/DisplayID not found; Supplier.UID/DisplayID]]
Translation: An issue with the Accounting Supplier Card
Something in relation to the supplier card may have changed e.g. A Supplier Card that has been set up as a Company in MYOB may have been changed to an Individual. Please note, Lightyear only imports Supplier Cards that have been set up as a Company from MYOB, thus only exporting to these Supplier Cards as well.
Perhaps you have selected a supplier card that no longer exists, has a duplicate or is made inactive. You'll want to:
- Head over to Accountancy Software Settings > Supplier Cards > Import from MYOB (to make sure you have the most recent list)
- Check that you don't have duplicates in this section
- If you do have duplicates, please delete both supplier cards (Don't worry - you're not actually deleting anything from within MYOB here)
- "IMPORT FROM MYOB" again to make sure you're bringing through the freshest record from MYOB
- Go to Lightyear Suppliers (truck icon) > Find the supplier > Edit > Reselect the Accounting Supplier card > Update
- Try and export the bill again - it should go through successfully at this point.
If you have recently upgraded your MYOB file or perhaps connected to an incorrect file, please contact our team via chat/email to assist further.
[[The Account with UID of 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' cannot be found.; UID]]
Translation: An issue with the selected GL Code on this bill
MYOB refers to GL Codes as Accounts, so this error message relates to an issue with a specific GL code selected for this bill.
Send the bill back to Approval/Review to make amendments. Perhaps you have selected a GL code that no longer exists, has a duplicate or is made inactive.
- Head over to Accountancy Software Settings > GL Codes > Import from MYOB (to make sure you have the most recent list)
- "IMPORT FROM MYOB" again to make sure you're bringing through the freshest record from MYOB
- Check that you don't have duplicates in this section
- If you do have duplicates, please mark one as "In Use", and leave the other as "Not In Use".
- Head back to Signed Off and move the bill back to Review/Approvals (depending on your setup) and amend from here to try and export the bill again.
- If this doesn't work, return to step 4, and mark the "Not In Use" GL Code as "In Use".
If you have recently upgraded your MYOB file or perhaps connected to an incorrect file, please contact our team via chat/email to assist further.
[[Term_Out_Of_Range; NumberOfDaysForBalanceDue:(PurchaseEvent)]]
Translation: Issue with Due Date
The usual culprit here is when the Due Date. Please check your bill and ensure the Due Date is after the extracted Bill Date.
If you need to change this, send the bill back to Review/Approvals and update the date from these tabs before Signing Off to export again.
[[Connection to the API has timed out; Maximum call time is :120 Seconds]]
Translation: We've run out of time and we're not getting a response back to let us know if the data made it.
As it states, there is a 2minute gateway for us to send data to MYOB when the connection is established and the export button has been clicked. In this case, we're flagging that we've tried to send data, but we haven't received a response hence the "timed out" reference. You'll be best to check your MYOB file to see if they have actually made it through before trying to export again.
If they have arrived in MYOB, you can opt to Archive your documents instead of Exporting. If they haven't arrived in MYOB, you can try to export again. Just to be safe, you might want to refresh your page to avoid any potential duplications.
[Internal Application error: Please contact Technical Support]
You have found this article because you are trying to export bills to MYOB Essentials / Account Right but they are presenting this error message. Please note, this is the error message we are receiving back from MYOB which is presented in your Activity > Activity tab.
It's a process of elimination to reach a resolution. Here are some of the tips that have worked to resolve it.
Check Data details
Have a look at your data to ensure that they are in valid formats to ensure that is not stopping you from exporting successfully. Things to look out for :
- Date is in a valid format
- Bill number is not a long number/string of characters
Amend the data as required and try to export again.
A Duplicate Bill exists in MYOB
If you have the setting turned on in MYOB to disregard duplicates, then we aren't able to send bills across. Perhaps you have previously manually entered the bill in directly to MYOB or for some reason you may have exported the bill from Lightyear previously and require it to go through. If you really need it, then you can uncheck the setting in MYOB to allow these bills to go through.
GL Code is a Header Account in MYOB
Whilst Lightyear is able to bring back your Header Accounts as part of the GL Code set up, the API does not allow for exports to the Header Codes.
Please make sure the GL code you have selected is not a Header Code in your MYOB file. Correct it if it needs to be or select a different GL code in Lightyear before trying to export again.
Categories
If you're using Categories in MYOB, please note you can only select ONE Category per bill.
You will see this error message if you happen to assign multiple categories across a multi line item bill, you will see this error message appear.
Set the category all to the same category before trying to export again.
If after trying all these techniques and you're still experiencing an issue, please reach out to us via support@teamlightyear.cloud
Check out our
to stay up to date
Related Articles
Troubleshooting Xero Error Messages
Lightyear has a ton of built in validation checks to ensure the data is correct in Lightyear before trying to send the Bill and information to Xero. However, there are occasions when the Export fails and Lightyear displays the reason for the error - ...Error Messages Returned from iplicit Upon Export
Lightyear has a ton of built in validation checks to ensure the data is correct in Lightyear before trying to send the bill and information to iplicit. However, there are occasions when the export fails and Lightyear displays the reason for the error ...Error Messages Returned from Sage Business Cloud upon Export
Lightyear has a ton of built in validation checks to ensure the data is correct in Lightyear before trying to send the bill and information to Sage Business Cloud. However, there are occasions when the export fails and Lightyear displays the reason ...Error Messages Returned from QuickBooks Online
Lightyear has a ton of built in validation checks to ensure the data is correct in Lightyear before trying to send the Bill and information to Quickbooks Online. However, there are occasions when the Export fails and Lightyear displays the reason for ...Error Messages Returned from accountsIQ Upon Export
Lightyear has a ton of built in validation checks to ensure the data is correct in Lightyear before trying to send the bill and information to accountsIQ. However, there are occasions when the export fails and Lightyear displays the reason for the ...