Last Updated: April 16 2024

Submit Search

MYOB Desktop Troubleshooting

Overview

The following is a list of error messages you may see if you encounter an issue with the MYOB desktop accounting link:

Issue	Solution
Cannot Initialize MYOB Application specified does not exist Application specified does not have writing support Cause: MYOB is not installed correctly, or the accounting link is not set up with the correct MYOB program file.	In the accounting link, go to the Setup tab and check that the MYOB program file path matches the actual location of the MYOB program file.
Your Settings File has become corrupted. Please contact Support. (Reported Error: Object reference not set to an instance of an object.) Cause: The settings file has corrupted data.	Delete the settings file, and the accounting link re-creates it. If you need help finding the settings file, contact Simpro Premium support. You need to enter your Simpro Premium and MYOB settings again.
Not allowed to change the 'ConnectionString' property. The connection's current state is open Cause: The transaction exceeds the maximum file size.	Skip the affected transaction and manually enter it in MYOB. If you are receiving this error often, contact Simpro Premium support.
Attempted to read or write protected memory. This is often an indication that other memory is corrupt Cause: This is caused by the above error "Not allowed to change the 'ConnectionString' property. The connection's current state is open."	Solve the above error.
Error Posting: Invalid date Cause: The computer that MYOB is running on has a different date format to the transactions being sent by the accounting link.	Adjust the date format on the computer that is running MYOB.
Company file does not exist Cause: The company file selected in the accounting link does not exist.	In the accounting link, go to the Setup tab and select the correct MYOB company file. Company files usually end with .MYO
The company file selected is not supported by this version of ODBC MYOB ODBC does not support this company file version Cause: The company file selected was used with an earlier or later version of MYOB that used a version of the ODBC driver other than the one currently installed.	Contact MYOB and ask to update your company file to work with the current version of MYOB you have installed. Then, reinstall the ODBC driver.
This company file has not been registered for ODBC access Cause: The company file is not registered to allow third party applications, such as the accounting link, to integrate with it.	You need to activate your company file. Contact MYOB support.
Company file is corrupt. Unable to access the company file. Cause: The company file has bad or corrupt data.	Contact MYOB support to resolve the corruption.
Unable to launch MYOB - Database specified in the connection string is already opened by another application Unable to Establish a Connection with the ODBC Driver. Reason ERROR [HZ080] [MYOB ODBC] – Unable to launch MYOB – Database specified in the connection is already opened exclusively by another application. Error HZ080 [MYOB ODBC] An initialisation error has occurred with your application MYOB ODBC – Unable to launch MYOB database required. Connection string is already opened exclusively by another application Cause: Another user is already logged in to the MYOB company file in single-user mode.	All other users must log out of MYOB before the accounting link can be used to post data. To check who is logged in to a company file, in MYOB go to File > active workstations.
You do not have write access to this company file Cause: The MYOB login you have used for the selected company file does not have the correct permissions to send the payment.	Use a MYOB login that does not have any restrictions for the company file.
Connected to Cause: The MYOB username you have used for the selected company file is restricted.	Use a MYOB login that does not have any restrictions for the company file.
Login details are incorrect Cause: Your MYOB or Simpro Premium username and / or password are incorrect.	Go to the Setup tab and re-enter your username and password for both MYOB and Simpro Premium. If the error persists, log in to MYOB and Simpro Premium to check that the login details are correct.
FAILED StartIndex cannot be less than zero. Parameter name: startIndex Error Testing simpro Host 'demo.simpro.co': Root element is missing - the most likely reason for this error is that the Host entered: [demo.simpro.co] is not valid Cause: The Simpro Premium Server address in the accounting link is incorrect.	Go to Setup > Manage Simpro Premium Builds and check the Simpro Premium Server address. Contact Simpro Premium support if you need help confirming the address.
Could Not be Verified Unable to determine if import has finished Cause: The accounting link did not receive the expected response from MYOB.	Reinstall the ODBC driver, then send the transaction again to receive more information about what has caused the error.
Account number is too long Cause: The account number in Simpro Premium exceeds the nine character maximum allowed by MYOB.	In Simpro Premium, go to System > Setup > Accounts > Cost Centres and System > Setup > Defaults > Financial and make sure that all account numbers are nine characters or less. This includes spaces.
Account number not found in list of postable accounts Cause: The account number specified in the transaction doesn't match an account number in MYOB.	In Simpro Premium, go to System > Setup > Accounts > Cost Centres and System > Setup > Defaults > Financial and check that your account numbers match account numbers in MYOB.
Deposit Account must be a Bank Account Cause: The account you are posting to is not a bank-type account.	Unlock the payment in Simpro Premium and change the deposit account number to a valid MYOB bank account number.
First digit of account number must be 1,2,3,4,5,6,7,8 or 9 Cause: The account number does not start with a number between one and nine.	In Simpro Premium, go to System > Setup > Accounts > Cost Centres and System > Setup > Defaults > Financial and check that your account numbers do not start with a zero.
No account specified for tax paid GST account linked account is missing Cause: The linked account for Tax Paid has not been specified in the tax code in MYOB.	In MYOB, go to Lists > Tax Codes and open the affected tax code. Enter the correct linked account information. If you are not sure what linked account you need, consult your accountant.
Default Account for Freight charges not specified Cause: A linked account for freight is not specified in MYOB.	In MYOB, go to Setup > Linked Accounts > Sales Accounts / Purchases Accounts. Make sure the option I charge Freight on Sales/Purchases is selected and an account number is specified.
Validation Error :: Contractor Invoice (718887) Category [Cost Centre] 'XXXX' not found in MYOB Cause: Category tracking is enabled and there is a category in Simpro Premium that does not exist in the category list in MYOB.	Add the missing category in MYOB.
Payment :: (6050) :: Error Posting: Transactions dated before your "Lock Period" date may not be imported. Cause: The financial period in the accounting package has been reconciled and locked to prevent incorrect values being entered.	Either adjust the date on the transaction in Simpro Premium, and then post again, or unlock the locked period and send the transaction over, then lock the period again. You may wish to speak to your accountant for advice.
A category is required Cause: In MYOB, invoice category tracking is set to required.	You can either: Disable category tracking in MYOB under Setup > Preferences > System. To enable category tracking in Simpro Premium, go to System > Setup > Defaults > Financial, and enable category tracking in the accounting link. Learn more about category tracking in How to Use Accounting Categories.
Amount applied is invalid or blank Cause: The payment / supplier invoice / invoice has a value of zero.	Zero-value transactions cannot be posted to MYOB. Either flag the transaction to not send, or correct the value in Simpro Premium before posting again.
Customer not found. Sales invoice not imported. Customer not found. Receive payment not imported Cause: The customer does not exist in MYOB, or the customer ID in Simpro Premium does not match the ID in MYOB.	Make sure the customer exists in MYOB, and that the IDs match on the customer card in MYOB, and the customer card in Simpro Premium.
Payments are not allowed on quotes & credits Cause: The invoice number in Simpro Premium that payment is for is marked against a credit or quote in MYOB.	Change the invoice number in MYOB and post the invoice again, followed by the payment.
The card attached to the invoice is not the same as the card attached to the payment Cause: The customer on the invoice that the payment is for in Simpro Premium does not match the customer that this payment is for in MYOB. Alternatively, invoice numbers may be too similar, such as 000123 and 123.	Change the customer on the invoice in MYOB, then post the payment again. Alternatively, change the invoice number in MYOB and repost the payment, or apply payment the payment manually and then skip it in the accounting link.
Invoice # not found Cause: The invoice associated with the payment being sent does not exist in MYOB.	Find the invoice in MYOB and change the invoice number, then post the correct invoice from Simpro Premium to MYOB. Alternatively, if you have not yet sent the invoice to the customer, delete the invoice in Simpro Premium and re-create it to get another invoice number.
Customer not found. Receive payment not imported. Cause: The customer associated with the payment being sent does not exist in MYOB.	Find the invoice in MYOB and change the invoice number, then post the correct invoice from Simpro Premium to MYOB. Alternatively, if you have not yet sent the invoice to the customer, delete the invoice in Simpro Premium and re-create it to get another invoice number.
Customer not found. Sale invoice not imported. Cause: The customer associated with the invoice being sent does not exist in MYOB.	Find the invoice in MYOB and change the invoice number, then post the correct invoice from Simpro Premium to MYOB. Alternatively, if you have not yet sent the invoice to the customer, delete the invoice in Simpro Premium and re-create it to get another invoice number.
The card attached to the invoice is not the same as the card attached to the payment. Cause: The customer on the invoice in MYOB is different from the customer that is on the payment in Simpro Premium.	Find the invoice in MYOB and change the invoice number, then post the correct invoice from Simpro Premium to MYOB. Alternatively, if you have not yet sent the invoice to the customer, delete the invoice in Simpro Premium and re-create it to get another invoice number.
Transactions dated before the beginning of your financial year may not be imported. Cause: The financial period in MYOB is locked.	It is not possible to send a transaction to a locked period. Consult your accountant.
Supplier not found. Purchase order not imported. Cause: The supplier associated with the purchase order being sent does not exist in MYOB.	Send the supplier to MYOB, followed by the purchase order.
[HY000][MYOB ODBC] General error – Database keyword not present in the connect string. Cause: The MYOB company file address in the Setup tab is not correct.	In the accounting link, go to the Setup tab and enter the correct address that links to the company file.
Incorrect Username/Password specified (MYOB and Simpro Premium) Cause: Either the MYOB or Simpro Premium username or password is incorrect.	Enter your MYOB and Simpro Premium username and password again.
[HZ080] [MYOB ODBC] – Unable to connect for writing. No MYOB application has been specified. Cause: The MYOB company file address in the Setup tab is not correct.	In the accounting link, go to the Setup tab and enter the correct address that links to the company file.
Account number not found in list of postable accounts. Cause: The account number specified either does not exist or is not a postable account.	In Simpro Premium, go to System > Setup > Defaults Financial and System > Setup > Accounts > Cost Centres and check that the account numbers match postable accounts in MYOB. Also, make sure the account number is not a header account. In MYOB, header account numbers are in bold, and cannot be posted to from the accounting link as they are groups of accounts.

Issue

Solution

Cannot Initialize MYOB

Application specified does not exist

Application specified does not have writing support

Cause: MYOB is not installed correctly, or the accounting link is not set up with the correct MYOB program file.

In the accounting link, go to the Setup tab and check that the MYOB program file path matches the actual location of the MYOB program file.

Your Settings File has become corrupted. Please contact Support. (Reported Error: Object reference not set to an instance of an object.)

Cause: The settings file has corrupted data.

Delete the settings file, and the accounting link re-creates it. If you need help finding the settings file, contact Simpro Premium support. You need to enter your Simpro Premium and MYOB settings again.

Not allowed to change the 'ConnectionString' property. The connection's current state is open

Cause: The transaction exceeds the maximum file size.

Skip the affected transaction and manually enter it in MYOB. If you are receiving this error often, contact Simpro Premium support.

Attempted to read or write protected memory. This is often an indication that other memory is corrupt

Cause: This is caused by the above error "Not allowed to change the 'ConnectionString' property. The connection's current state is open."

Solve the above error.

Error Posting: Invalid date

Cause: The computer that MYOB is running on has a different date format to the transactions being sent by the accounting link.

Adjust the date format on the computer that is running MYOB.

Company file does not exist

Cause: The company file selected in the accounting link does not exist.

In the accounting link, go to the Setup tab and select the correct MYOB company file. Company files usually end with .MYO

The company file selected is not supported by this version of ODBC

MYOB ODBC does not support this company file version

Cause: The company file selected was used with an earlier or later version of MYOB that used a version of the ODBC driver other than the one currently installed.

Contact MYOB and ask to update your company file to work with the current version of MYOB you have installed. Then, reinstall the ODBC driver.

This company file has not been registered for ODBC access

Cause: The company file is not registered to allow third party applications, such as the accounting link, to integrate with it.

You need to activate your company file. Contact MYOB support.

Company file is corrupt. Unable to access the company file.

Cause: The company file has bad or corrupt data.

Contact MYOB support to resolve the corruption.

Unable to launch MYOB - Database specified in the connection string is already opened by another application

Unable to Establish a Connection with the ODBC Driver. Reason ERROR [HZ080] [MYOB ODBC] – Unable to launch MYOB – Database specified in the connection is already opened exclusively by another application.

Error HZ080 [MYOB ODBC] An initialisation error has occurred with your application MYOB ODBC – Unable to launch MYOB database required. Connection string is already opened exclusively by another application

Cause: Another user is already logged in to the MYOB company file in single-user mode.

All other users must log out of MYOB before the accounting link can be used to post data. To check who is logged in to a company file, in MYOB go to File > active workstations.

You do not have write access to this company file

Cause: The MYOB login you have used for the selected company file does not have the correct permissions to send the payment.

Use a MYOB login that does not have any restrictions for the company file.

Connected to

Cause: The MYOB username you have used for the selected company file is restricted.

Use a MYOB login that does not have any restrictions for the company file.

Cause: Your MYOB or Simpro Premium username and / or password are incorrect.

Go to the Setup tab and re-enter your username and password for both MYOB and Simpro Premium.

If the error persists, log in to MYOB and Simpro Premium to check that the login details are correct.

FAILED StartIndex cannot be less than zero. Parameter name: startIndex

Error Testing simpro Host 'demo.simpro.co': Root element is missing - the most likely reason for this error is that the Host entered: [demo.simpro.co] is not valid

Cause: The Simpro Premium Server address in the accounting link is incorrect.

Go to Setup > Manage Simpro Premium Builds and check the Simpro Premium Server address. Contact Simpro Premium support if you need help confirming the address.

Could Not be Verified

Unable to determine if import has finished

Cause: The accounting link did not receive the expected response from MYOB.

Reinstall the ODBC driver, then send the transaction again to receive more information about what has caused the error.

Account number is too long

Cause: The account number in Simpro Premium exceeds the nine character maximum allowed by MYOB.

In Simpro Premium, go to System > Setup > Accounts > Cost Centres and System > Setup > Defaults > Financial and make sure that all account numbers are nine characters or less. This includes spaces.

Account number not found in list of postable accounts

Cause: The account number specified in the transaction doesn't match an account number in MYOB.

In Simpro Premium, go to System > Setup > Accounts > Cost Centres and System > Setup > Defaults > Financial and check that your account numbers match account numbers in MYOB.

Deposit Account must be a Bank Account

Cause: The account you are posting to is not a bank-type account.

Unlock the payment in Simpro Premium and change the deposit account number to a valid MYOB bank account number.

First digit of account number must be 1,2,3,4,5,6,7,8 or 9

Cause: The account number does not start with a number between one and nine.

In Simpro Premium, go to System > Setup > Accounts > Cost Centres and System > Setup > Defaults > Financial and check that your account numbers do not start with a zero.

No account specified for tax paid

GST account linked account is missing

Cause: The linked account for Tax Paid has not been specified in the tax code in MYOB.

In MYOB, go to Lists > Tax Codes and open the affected tax code. Enter the correct linked account information. If you are not sure what linked account you need, consult your accountant.

Default Account for Freight charges not specified

Cause: A linked account for freight is not specified in MYOB.

In MYOB, go to Setup > Linked Accounts > Sales Accounts / Purchases Accounts. Make sure the option I charge Freight on Sales/Purchases is selected and an account number is specified.

Validation Error :: Contractor Invoice (718887) Category [Cost Centre] 'XXXX' not found in MYOB

Cause: Category tracking is enabled and there is a category in Simpro Premium that does not exist in the category list in MYOB.

Add the missing category in MYOB.

Payment :: (6050) :: Error Posting: Transactions dated before your "Lock Period" date may not be imported.

Cause: The financial period in the accounting package has been reconciled and locked to prevent incorrect values being entered.

Either adjust the date on the transaction in Simpro Premium, and then post again, or unlock the locked period and send the transaction over, then lock the period again. You may wish to speak to your accountant for advice.

A category is required

Cause: In MYOB, invoice category tracking is set to required.

You can either:

Disable category tracking in MYOB under Setup > Preferences > System.
To enable category tracking in Simpro Premium, go to System > Setup > Defaults > Financial, and enable category tracking in the accounting link. Learn more about category tracking in How to Use Accounting Categories.

Amount applied is invalid or blank

Cause: The payment / supplier invoice / invoice has a value of zero.

Zero-value transactions cannot be posted to MYOB. Either flag the transaction to not send, or correct the value in Simpro Premium before posting again.

Customer not found. Sales invoice not imported.

Customer not found. Receive payment not imported

Cause: The customer does not exist in MYOB, or the customer ID in Simpro Premium does not match the ID in MYOB.

Make sure the customer exists in MYOB, and that the IDs match on the customer card in MYOB, and the customer card in Simpro Premium.

Payments are not allowed on quotes & credits

Cause: The invoice number in Simpro Premium that payment is for is marked against a credit or quote in MYOB.

Change the invoice number in MYOB and post the invoice again, followed by the payment.

The card attached to the invoice is not the same as the card attached to the payment

Cause: The customer on the invoice that the payment is for in Simpro Premium does not match the customer that this payment is for in MYOB.

Alternatively, invoice numbers may be too similar, such as 000123 and 123.

Change the customer on the invoice in MYOB, then post the payment again.

Alternatively, change the invoice number in MYOB and repost the payment, or apply payment the payment manually and then skip it in the accounting link.

Invoice # not found

Cause: The invoice associated with the payment being sent does not exist in MYOB.

Find the invoice in MYOB and change the invoice number, then post the correct invoice from Simpro Premium to MYOB. Alternatively, if you have not yet sent the invoice to the customer, delete the invoice in Simpro Premium and re-create it to get another invoice number.

Customer not found. Receive payment not imported.

Cause: The customer associated with the payment being sent does not exist in MYOB.

Customer not found. Sale invoice not imported.

Cause: The customer associated with the invoice being sent does not exist in MYOB.

The card attached to the invoice is not the same as the card attached to the payment.

Cause: The customer on the invoice in MYOB is different from the customer that is on the payment in Simpro Premium.

Find the invoice in MYOB and change the invoice number, then post the correct invoice from Simpro Premium to MYOB.

Alternatively, if you have not yet sent the invoice to the customer, delete the invoice in Simpro Premium and re-create it to get another invoice number.

Transactions dated before the beginning of your financial year may not be imported.

Cause: The financial period in MYOB is locked.

It is not possible to send a transaction to a locked period. Consult your accountant.

Supplier not found. Purchase order not imported.

Cause: The supplier associated with the purchase order being sent does not exist in MYOB.

Send the supplier to MYOB, followed by the purchase order.

[HY000][MYOB ODBC] General error – Database keyword not present in the connect string.

Cause: The MYOB company file address in the Setup tab is not correct.

In the accounting link, go to the Setup tab and enter the correct address that links to the company file.

Incorrect Username/Password specified (MYOB and Simpro Premium)

Cause: Either the MYOB or Simpro Premium username or password is incorrect.

Enter your MYOB and Simpro Premium username and password again.

[HZ080] [MYOB ODBC] – Unable to connect for writing. No MYOB application has been specified.

Cause: The MYOB company file address in the Setup tab is not correct.

In the accounting link, go to the Setup tab and enter the correct address that links to the company file.

Account number not found in list of postable accounts.

Cause: The account number specified either does not exist or is not a postable account.

In Simpro Premium, go to System > Setup > Defaults Financial and System > Setup > Accounts > Cost Centres and check that the account numbers match postable accounts in MYOB.

Also, make sure the account number is not a header account. In MYOB, header account numbers are in bold, and cannot be posted to from the accounting link as they are groups of accounts.