Bank Profiles

Note

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

Buttons Explained

Button	Description
Add/Edit	Creates or edits a bank profile.
Save	Saves any changes.
Actions	Download Bank Profiles From Master: Lists the available bank profiles that can be downloaded. If the master database has no bank profiles, the message “No Bank Profiles from Master.” appears.
Output	Exports the list (currently unavailable).
Menu	Layout

Info

Fields marked in blue (✎) can be edited.

Field	Description
ID	The system-generated number allocated to the entry.
Code	A short description of the entry.
Description	The entry’s full description.
File Extension	Select one of these extensions: .ofx .csv .txt
Parser Function	Select a parser function from the dropdown list.
File Sample	Checkbox. Checked automatically when a file sample is uploaded.
Created	The date on which the entry was created.
Updated	The date on which the entry was last updated.
Updated By	The user who last updated the entry.
	A context menu with the following options: Upload Sample File: Uploads a sample bank file. If a sample is already uploaded, the message “The File Sample has been uploaded. Would you like to replace the existing one?” appears; click Yes (button) to replace it. Download Sample File: Saves the uploaded sample file. If no sample is uploaded, the message “File Sample has not been uploaded.” appears. Delete Bank Profile: Deletes the bank profile.

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

Guidelines for bank_parser_… function:

A Country Code (e.g. [ZA] for South Africa, [TH] for Thailand) must come before the bank code (e.g. [ZA] FNB).
The function must check that the bank account number is in the Lookup field of the linked bank account. If it is not, the function must return an error message.
If the export file contains a unique ID (e.g. FITID in an 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 must 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.