Skip to main content

Import transactions

Updated over 2 months ago

It is possible to import transaction data into Access Financials.
​
The ability to do so depends on the Security Profile permissions of the user.
​
To check the security profile of a user:

  1. Identify the security profile assigned to the user via their record.

  2. Click System, Security, Profiles.

  3. Select the required security profile.

  4. Click Edit.

  5. On the Permissions tab, check if Utilities, then for each of the Ledgers (Debtors, Creditors, Financials) is Imports enabled.

  6. Change if required.

  7. Click Save.
    ​Note: Everyone with this profile will now be able to do imports.

There a two types of Imports available for most transaction imports:

  • Grid: This is the legacy way of importing transaction data into Access Financials and can be used like an online grid of rows of your transactional data. Where you can easily copy and paste from a local file/spreadsheet application.

    • The import process can be sensitive to external formatting and so it is advisable to clear this as much as possible before pasting to the grid:

      • Paste special (Values) to an interim sheet then copy from there to the grid.

      • Ensure any number fields are set to 2dp and have the comma delimiter unset.

  • File based: This is where you are able to import from a local .CSV file directly to Access Financials, by uploading into the Database through the Financials Application.

In each type of import you are able to configure the import to your preferences, including which columns are in which order, and whether (for File based) the imported data contains Header Rows, etc.

Please note that Transaction Reference is used to group rows per account. Any rows that have the same Transaction Reference and same customer or supplier code, will be grouped together and loaded as one transaction, even if the rows have different dates. For transactions of type PAY, if you wish to create separate transactions that have the same reference for the same account, but with different dates, these will need to be imported in two separate imports, one per date and ensure there are no more than one row per account.

Did this answer your question?