Skip to main content
Skip table of contents

Error: "Tax File Number already exists"

This support note applies to:

  • AE Tax Series 6 & 8 (AU)
  • AE Tax (AU)
Article ID: 34052

In MYOB Accountants Enterprise (AE) when opening a tax return from AE Practice Manager you may experience the error "Tax file number already exists".

This message can occur if the Tax File Number (TFN) is attached to another tax return in the same tax year.

To eliminate this error search for and remove the TFN from the existing return.

To search for TFN in the Tax ledger
  1. Identify the TFN of the client and close all open returns.

  2. Open Windows Explorer or Computer and browse to the SOL64 location, for example X:\SOL64\ Where X:\ is the drive where System Release is installed.

    If you use Client Compliance/Contacts then to identify the relevant location, open Contacts/Client Compliance and from the Help menu, select About MYOB Contacts/Client Compliance, then click Application Details. Note the System Release Path, this refers to your Sol64 location.
  3. Double-click the sr.exe file.
  4. Type SUPERVIS in the User code field and S6 in the Password field and click OK.
  5. Open the folder with the reference AETAX1. (AETAX1 is the name of the tax database).

  6. Double-click on the relevant Tax ledger to open the ledger, for example AE tax 2012, if the issue is with a 2012 return.

    If the view shows return by clients and not all returns then follow the menu path: Utilities > Control Record > Defaults, and deselect the select returns by client option, click OK, then close Tax 2012 and then reopen Tax 2012.
  7. Right-click on any return and select Search.

  8. Click TFN, enter the required TFN without any spaces and click OK.

  9. Right-click on the incorrect tax return and select Properties.

  10. Delete the contents of the Tax File No field and click OK.

  11. Close the Tax Ledger and close System Release.

You are now able to successfully add the TFN to the required return without experiencing the error.

JavaScript errors detected

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

If this problem persists, please contact our support.