Skip to main content
Skip table of contents

Error: "Extract File NOT imported successfully. The file either contains errors or previously imported transactions"

This support note applies to:

  • AO Classic General Ledger (AU)
  • AO Classic (NZ)
Article ID: 37002

In MYOB Accountants Office Classic (AO Classic) you may experience the error "Extract File NOT imported successfully. The file either contains errors or previously imported transactions" when importing a file which was extracted from MYOB Essentials. This occurs as the MYOB Essentials file contains a blank line within the extracted data.

MYOB is investigating this issue.

To be able to import the MYOB Essentials file, extract the .txt file and use the AccountantLink option to import the file. During the import process assign the suspense account to the blank line.

As there are no transactions against the blank line, this has no impact on the balances or transactions in the suspense account. 
To extract the .txt file

When transactions are exported from MYOB Essentials they are in the format 'Filename.mye'.

  1. Right-click on the .mye file and rename it to .zip.
  2. Double-click on the .zip file to view the contents.
  3. Right-click on the MYOBAO.txt file and select Copy.
  4. Right-click on your Desktop and select Paste.
To import a txt file into AO Classic
  1. Open AO Classic and open the Clients General Ledger.
  2. Follow the menu path: File > Import > MYOB AccountRight/MYOB Essentials Accounting.
  3. Select the MYOB AccountRight / Essentials extract file option.
  4. Click the ellipsis (...) button to browse to and select the MYOBAO.txt file located on the Desktop.
  5. Click OK. The file path is updated to point to the txt file.
  6. Select any required posting options and account code conversion templates.
  7. Click Import. The Account Code conversion screen appears.
  8. Assign the suspense account code against the blank line and then click Import. The transactions are imported. Review all the imported transactions to ensure they are correct.
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.