Bank Import

Overview#

• The Bank module lets you import Bank Statements in various formats and from different banks.
• Imports are supported for both .ofx and .csv files.
• After a file is imported, it is renamed, by adding the Batch ID and the date to the filename. The renamed file is moved to the Imported folder.
• A warning is provided when a duplicate transaction appears – when the date, Amount and Description are the same as another transaction.
• The List View hides the ID and Acc No. and shows the Status column by default.
• You can only import Bank Accounts if they have access to the Bank's Entity. (Users who are not linked to an Entity have access to all the Entities.)
• When importing a Bank Statement, the created transaction is automatically linked to the Entity that is linked to the Bank Account.

Settings#

User Settings#

Transaction Settings#

• Users need View, New and Edit access to all the transactions that can be processed from a bank import.
• If you do not have access to a particular transaction, you can cancel the transaction when doing a Bank Import or leave it Pending for a user with access to process later.
• If a transaction is cancelled, it must be manually entered afterwards.

General Settings#

Accounting Settings#

When a unique ID is not provided, all the transactions in the import file are imported. You must manually check that entries are not duplicated, and that no entries were missed (e.g. by doing a bank reconciliation).

• Select an Import option from the dropdown list in the Import column for each Bank Account.
• Options on the dropdown list:
  • SA ABSA (.ofx): 
    • Has unique FITID
    • Has closing tags
    • Date format: yyyymmdd
  • SA ABSA (.csv):

• Does not have unique FITID.
• Date Format: yyyymmdd
• Line 1 – Empty,
• Line 2 – Opening balance,
• Line 3 – Transactions start
• Columns Imported/Used:
  • B – Bank Account no.
  • C – Transaction Date
  • G – Amount
  • I+J – Description
  • M – Balance

• SA FNB (.ofx): 
  • Has unique FITID.
  • Does not have closing tags.
  • Date format: yyyymmdd.
• SA FNB – No FITID Check (.ofx): 
  • No FITID check
• SA Investec (.ofx): 
  • Does not have unique FITID
  • Does not have closing tags (file has leading spaces in front of tags)
  • Date format: yyyymmdd
• SA Nedbank (.ofx): 
  • Does not have unique FITID
  • Has closing tags
  • Date format: yyyymmdd
• SA Nedbank – Credit Card (.csv)
• SA Standard (.ofx):
  • Has unique FITID (Date+ID).
  • Does not have closing tags.
  • Date format: yyyymmdd.
• SA Standard – Option 1 (.csv):
  • Custom CSV
  • Date format: yyyymmdd
• SA Standard – Option 2 (.csv): 
  • Custom CSV
  • Date format: yyyymmdd
• Capitec (.ofx) files:
  • Does not have unique FITID.
  • Date format: YYYYMMDD000000.
  • A Fees transaction is added for every transaction that attracts fees.

Default View#

Buttons Explained#

Data Filters Explained#

Fields Explained#

Edit Bank Transaction#

Buttons Explained#

Matching Text and Items Explained#

1. Matching records lets you quickly record recurring transactions (e.g. bank charges).
2. A record matches if the selected matching text matches the text on a previous entry.
3. If a matching record is found, you can click Update (button) to create a ledger transaction:
   1. Account names are prefilled based on the previous matching record.
   2. The description and amounts are updated from the current transaction.
4. If no matching records are found, you can manually create a transaction by clicking Create (button).

Fields Explained#

Bank Balance (List View)#

• When Ledger transactions are created for all the Bank Transactions, the Bank Balance at the bottom of the form should match.
• The bank-import grid view shows which Bank Transactions have matching Ledger transactions.
• Linked Ledger transactions must be valid accounting transactions before they appear on the grid view.