Bank Profiles

A Bank Profile is needed to import bank entries from a bank statement. The supported formats are .ofx, .csv, and .txt.

Navigation: Setup > Accounting > Bank Profiles (tab)

Bank Profiles Interface

Buttons Explained

ButtonDescription
Add/EditAllows a new bank profile to be edited or created.
SaveSaves any changes.
ActionsDownload Bank Profiles from Master: Lists the available bank profiles that can be downloaded.
OutputAllows the list to be exported.
MenuLayout

Fields Explained

FieldDescription
IDThe system-generated number allocated to the entry.
CodeThe entry’s brief description.
DescriptionThe entry’s full description.
File ExtensionA dropdown list to select one of these extensions:
.ofx
.csv
.txt
Parser FunctionA dropdown list to select a parser function.
File SampleCheckbox. If a file sample is uploaded, the block is automatically checked.
CreatedThe date on which the entry was created.
UpdatedThe date on which the entry was last updated.
Updated ByThe user who last updated the entry.
WidgetA submenu with the following functions:
– Upload Sample File
– Download Sample File
– Delete Bank Profile

Tutorials

How to Create a Bank Profile

This procedure assumes the applicable Parser file has been created and uploaded to the Master database.

  1. Navigate to Bank Profiles.
  2. Click Actions (button) > Download Bank Profiles from Master.
  3. Click the profile on the list.
  4. Click Select (button).

Technical Information: Parser Files

  1. Create a Postgres function to parse the bank files and update the Bank Import table. The function is created according to this format: 
    • Name = bank_parser_[file_extension][bank_name]: The lookup searches for functions starting with bank_parser_
    • Input Parameter = (bank_header_id integer)
  2. Once created, upload the file, including notes on how it works to the Master DB

Guidelines for bank_parser_… function:

  • The function should verify the Bank Account Number that must be contained in the linked Bank Account’s Lookup field. If the verification fails, return an error message.
  • If the export file contains a unique ID (e.g. FITID in FNB .ofx file), this value is saved to the bank_id field and is used to check for duplicate transactions in the bank_items table. The function must set the Start and End Dates.
  • If the export file does not contain a unique ID, the bank_id field should be left blank, only transactions that are dated on or after the Start Date must be imported and the function must set the End Date.

Learn More

  1. Bank Imports: Importing entries from a bank account.
  2. Bank Reconciliations: Bank recon interface and tutorial.