Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »


 

 

This feature is not enabled for all users. If this option isn’t available in the Tasks bar, please contact your client manager to enable this feature for your practice.

In order to import a client file, make sure that the configured ledger is Practice Ledger.

If you need to use ledger data that was prepared using a ledger that cannot be directly connected to, you can load the ledger data by importing an MYE, TXT or CSV file.

An MYE or TXT file contains details about the client’s ledger being imported, and chart of accounts and journal transactions. A CSV file contains either chart of accounts, or chart of accounts and transactions.

How to import an MYE client file

- When you import an MYE file, the system identifies any accounts that need to be added to the chart of accounts, and adds all the journal transactions as journals to the ledger.
- If your MYE file exceeds the system limit for journal entries (16,000), an error message will display. To address this issue, decrease the number of transactions and consolidate prior period data.

  1. Open the client’s Client Accounting > Trial Balance tab (called the Workpapers tab if you are licensed for Workpapers).
  2. Click Ledger > Import client file on the Tasks bar.
  3. In the Import Wizard window, Select the .MYE option under Choose file type.
  4. In the Select file to import field, browse for the .MYE file to import.
  5. Click Next. A message displays with details of the client’s name, start date and end date.
  6. If the details are correct, click Yes. The system validates the file format.
  7. Continue to Selecting account mapping options.
How to import a TXT client file

When you import a TXT file, the system identifies any accounts that need to be added to the chart of accounts, and adds all the journal transactions as journals to the ledger.

  1. Open the client’s Client Accounting > Trial Balance tab (called the Workpapers tab if you are licensed for Workpapers).
  2. Click Ledger > Import client file on the Tasks bar.
  3. In the Import Wizard window, Select the .TXT option under Choose file type.
  4. In the Select file to import field, browse for the .TXT file to import.
  5. Click Next. A message displays with details of the client’s name, start date and end date.
  6. If the details are correct, click Yes. The system validates the file format.

  7. Continue to Selecting account mapping options.

How to import a CSV client file

- Importing of CSV files is controlled by an XML configuration file, located in the Deploy folder. This file controls the mapping between columns in your CSV file and ledger fields. Additional information can be found in the XML file.
- CSV files containing up to 38,000 journal lines are supported. To import a CSV file with more than 38,000 journal lines, separate the CSV file into multiple files, ensuring that each file does not exceed the journal line limit, and perform a separate import for each file. You can also try decreasing the number of transactions and consolidating prior period data.

  1. Open the client’s Client Accounting > Trial Balance tab (called the Workpapers tab if you are licensed for Workpapers).

  2. Click Ledger > Import client file on the Tasks bar.

  3. In the Import Wizard window, Select the .CSV option under Choose file type.

  4. In the Select file to import field, browse for the .CSV file to import.

  5. Select the type of mapping to use from the Select template dropdown.

    - Choose the template that matches the client’s source file. If you’re not sure which one to select, contact your IT or MYOB Support
    - The default options are Default Template and Quickbooks 2014 Template. If there are any other options listed, that means they have been customised for your site.

  6. Click Next. The system validates the file format.

  7. Continue to Selecting account mapping options.

Using the default MYOB template

To successfully import 3rd party transactions, the file containing the exported transactions need to follow the default import format. Below are the default template specifications for the contents of the import file. The file needs to match these specifications to be able to import the transactions. These are normally in CSV file format, which you can create using Microsoft Excel.

The column names in your CSV file must be in the first line of your CSV file.

Some ledger fields are mandatory and some are optional, as shown in the following table.

 

Column name    

Maps toMandatory/optional
account codeAccountCodeMandatory
account nameAccountNameOptional
account typeAccountType

Optional

Note: The following values are valid:
Income, Other Income, Liability, Equity, Expense, Other Expense, Assets, Cost of Sales, Uncategorised

account type groupAccountTypeGroupOptional
tax codeTaxCode

Optional
The valid code values (and their definitions) are:
  • NA (No tax implied)
  • (Australia) CAP (Capital acquisitions)
  • (Australia) EXP (Export sales)
  • (Australia) FRE (GST free)
  • GST (Goods & Services Tax)
  • (New Zealand) E (Exempt)
  • (Australia) GNR (Not registered)
  • (Australia) INP (Input taxed purchases)
  • (Australia) ITS (Input taxed sales)
  • NTR (Not reportable).
  • (New Zealand) Z (Zero rate)
  • (New Zealand) I (GST on imported supplies).
If no value is entered, the default value of NA is used.
transaction referenceTransactionReferenceId

Optional
transaction descriptionTransactionDescription

Optional
transaction dateTransactionDate

Optional (mandatory if TransactionAmount is mapped)

The following formats are both valid:
  • dd/mm/yyyy
  • dd-mm-yyyy
transaction amountTransactionAmountOptional

Note: The file should be balanced:
Sum of Amount = $0
Sum of Amount for each unique Date = $0

No special characters are allowed ($ or ',')
Signage is allowed (+, -)
 

 

Column name    Maps to    Mandatory/optional
account code    AccountCode    Mandatory
account name    AccountName    Optional
account type    AccountType    Optional
The following values are valid:
Income, Other Income, Liability, Equity, Expense, Other Expense, Assets, Cost of Sales, Uncategorised
account type group    AccountTypeGroup    Optional
tax code    TaxCode    Optional
The valid code values (and their definitions) are:
NA (No tax implied)
(Australia) CAP (Capital acquisitions)
(Australia) EXP (Export sales)
(Australia) FRE (GST free)
GST (Goods & Services Tax)
(New Zealand) E (Exempt)
(Australia) GNR (Not registered)
(Australia) INP (Input taxed purchases)
(Australia) ITS (Input taxed sales)
NTR (Not reportable).
(New Zealand) Z (Zero rate)
(New Zealand) I (GST on imported supplies).
If no value is entered, the default value of NA is used.
transaction reference    TransactionReferenceId    Optional
transaction description    TransactionDescription    Optional
transaction date    TransactionDate    Optional (mandatory if TransactionAmount is mapped)

The following formats are both valid:
dd/mm/yyyy
dd-mm-yyyy
transaction amount    TransactionAmount    Optional

The file should be balanced:
Sum of Amount = $0
Sum of Amount for each unique Date = $0

No special characters are allowed ($ or ',')
Signage is allowed (+, -)