Import the client's transactions

If you’re using an online accounting software or a third-party accounting software, you typically get the option to choose to import transactions data as you import the trial balance data.

If you’re importing the client’s data from a CSV file, you need to first import the trial balance data then import the transactions CSV to populate the transactions data in your engagement.

Import from a CSV file

Go to the Data page and select Import in the left pane, then Import Transactions CSV. To successfully import transactions from a CSV file, you need to:

  1. Prepare the CSV file.
  2. Import the CSV file.
  3. Map the fields.
  4. Optionally, import additional transactions CSV files.

Stap 1: Prepare the CSV file

Make sure the transactions CSV file is valid. The validity requirements display in the page once you select Import Transactions CSV.

Validity requirements for transactions CSV file

Stap 2: Import the CSV file

  1. Drag and drop the file or browse.

    Drag and drop here or browse the CSV file.

  2. Select the desired field delimiter.

    Beschikbare opties:

    • Comma (,)
    • Tab (\t)
    • Vertical Bar (|)
    • Semicolon (;)
    • Record Separator (\u001e)
    • Unit Separator (\u001f)
  3. Select Continue.

    Upon a successful file import, a confirmation message displays at the bottom of the page.

Stap 3: Map the fields

To complete the transactions import process, you need to map the source fields in the CSV file to target fields that match the data.

There are four main value categories for the target fields: Core, Additional Fields, Subledger Master and Account Master.

In some cases, when you map a field, the MAP COLUMN VALUES drop-down becomes available for the field because you need to map the values in this field as well. For example, the Document Type field (which is part of the Core category). Once you select this field as the target field, you need to select the MAP COLUMN VALUES drop-down to specify target values for each source value as well.


To map the source fields in the CSV file to desired target fields:

  1. Select MAP.

    Map transactions

    The page splits to two sections. The upper section shows the source fields from the CSV and the lower section shows the data in each field.

  2. Use the available drop-downs to select a target field to map each source field in the CSV.

    The main categories and their subsequent fields display in the drop-downs.

    TIP: Move your cursor to a specific field to view a description of it to help you map the values correctly. You can also find specific target fields using the search field at the top of the drop-down menu.

    Move your cursor to a specific field to view a description of the field so you can do correct mapping. If you know the target field, use the Search field at the top to find it.

  3. If value mapping is required for a specific field, the MAP COLUMN VALUES drop-down is available at the field.

    1. Select the MAP COLUMN VALUES drop-down.

    2. Specify your selections, then collapse the drop-down menu once you’re done.

      The following figure shows an example of field value mapping for Document Type. Note that Document Type has been mapped to originating_document_type field in the source CSV file. In the process of value mapping, the target value General Ledger Entries (GJ) values is mapped to GJ from the CSV file.

      Value mapping for originating_document_type.

  4. Once you finish the mapping process, select the Import button () to finalize the transactions import process.

    Tip: You can restart the mapping process if needed using the REMAP button.

    Remap transactions.

  5. Close the Import Transactions page and go back to your engagement file.

To view the account transactions you've just imported, go back to the Data page and select the Transactions tab. To learn more, see View the client’s transactions.