SECTION 1 GENERAL INFORMATION
1.1 SYSTEM INTRODUCTION
The BANCADO System provides community banks with a modern and simple method of accounting for deposits, loans, and the bank's general ledger. The method of accounting provided by the BANCADO SYSTEM combines the flexibility of magnetic disk storage with the power of the today's microprocessors.
The BANCADO System also provides for user-designed report generation and system maintenance. These features are standard system applications, and user documentation is available. Therefore, these features will not be described in this manual.
The BANCADO System is designed to provide the features most desired by the community banker. These features include:
1. Deposit Accounting
2. Loan Accounting
3. General Ledger Accounting
4. Forecasting
5. Bond Accounting
The BANCADO System maintains a complete set of files used for account processing. A file is defined as a group of like records, with a record being a group of related data elements or pieces of information pertaining to an individual customer or account. The BANCADO System maintains a complete customer files, called the Customer Information File, which contains one record for each customer of the bank. The system also maintains a file for each type of deposit and each type of loan, as well as a transaction file. A complete description of these files is presented in Section 1.3, Disk Files.
The BANCADO System consists of the following equipment:
The BANCADO System is menu driven. Each menu displays the operations that can be initiated. Selection of an operation often causes display of another menu for further definition of the task to be performed.
The flow of data through each application accounting system is dependent on the requirements of each installation. Few restrictions are built into the BANCADO System. In general, the following requirements must be met and determine system flow:
The first step in installing a BANCADO accounting system is to build the system files. The system files that must be set up depend on the application systems that will be used.
Most application systems use the Customer Information File (CIF). After building the Customer Information File, each system requires the building of other pertinent files. For example, the Deposit system requires the Deposit Account file and the Installment Loan system requires the Loan file.
On a daily basis, transactions and new accounts, loans, or certificates of deposit are entered for each application system. The transactions are stored in Transaction files for printing transaction journals. Each transaction journal must be generated every day because the daily accrual update is performed during the printing of the transaction journals. The frequency of printing other reports is left to the discretion of each bank.
The processing schedule presented below is intended as a guide and should be adjusted according to the needs of your bank.
DAILY PROCESSING SCHEDULE
MORNING:
AFTERNOON:
STATEMENT DAYS:
The BANCADO accounting systems are used to generate numerous reports. The reports can be generated on any cyclic basis or whenever requested by the bank. Each installation will have different requirements for report generation. In general, the accounting reports will be generated as follows:
File No. |
File Name |
Description |
0 |
System Control |
This file contains control information used in system operation. |
1 |
Customer Information |
This file contains one record for each customer. The information contained in the file pertains to the customer rather than to an individual loan or account. In this way, the system is able to group a customer's loans and accounts together for reporting purposes, while conserving disk space by not repeating information such as name and address for each record. |
1 |
General Ledger Account |
This file contains two records for each general ledger account; one for the current year and one for the prior year. |
1 |
Construction Loan Project |
This file contains the basic descriptive information concerning construction loan projects. |
2 |
Commercial Loan |
This file contains information pertaining to individual notes, such as amount, balance, and interest due. |
2 |
Proof Transaction |
This file contains daily transaction data for the proof entry system. |
2 |
Bond Description |
This file contains descriptive data concerning bank owned bonds. |
2 |
G/L Report Control |
This file contains records that control the printing of general ledger daily statement and income reports. |
2 |
|
This file contains the various balances for each cost center involved in the current construction loan projects. |
3 |
Installment Loan |
This file contains information pertaining to individual loans such as amount, balance, and payoff. |
3 |
Bond Accounting |
This file contains the accounting data pertaining to bond accounts. |
3 |
G/L Automatic Entries |
This file contains records for general ledger transactions that are generated automatically on a regular basis. |
3 |
Construction Loan Transaction |
This file contains detail transaction history for construction loan projects. |
3 |
ForeCash Assumptions |
This file contains the assumptions for forecast accounts with one record per forecast account number. |
4 |
Floor Plan Detail |
This file contains detailed descriptions of the collateral for floor plan loans. |
4 |
Performance |
This file contains records for each type of installment loan by office and dealer for storage of earnings information. |
4 |
G/L Transaction |
This file contains detail general ledger transactions. Normally, 13 areas are reserved for the transactions so that annual general journals may be produced. |
4 |
Inquiry Control File |
This file contains control records for the BANCADO Inquiry system. There are records for valid commands, stations, and passwords. |
4 |
ForeCash Assumptions |
This file is used to temporarily save the assumptions for forecast accounts with one record per forecast account number. |
4 |
ForeCalc History Text |
This file contains one record per text row on forecasts. |
4 |
Certificates of Deposit |
This file contains information pertaining to the terms of each individual certificate of deposit. |
5 |
ForeCash Forecast File |
This file contains actual forecast records. |
5 |
IRA |
This file contains information pertaining to Individual Retirement Accounts such as balance, year-to-date interest, and account type. |
6 |
Deposit Account |
This file contains information pertaining to individual accounts such as balance, year-to-date interest and account type. |
6 |
ForeCash Tables |
This file contains various tables used by ForeCash. |
6 |
ForeCalc Master Reference |
This file contains one reference record for each fifty rows of forecasts on file. |
7 |
Transaction (for each application) |
All transaction history is contained in the Transaction file. The current day's transaction journal and prior transactions are retained for printing on the customer ledger. In addition, file 7 contains special records pertaining to Bank Control information such as last posting date, total balance, etc. |
8 |
Deposit Control |
This file contains control records for interest calculations and proof entry. |
8 |
Name Lookup |
This file contains cross-reference data for accessing accounts by last name. Since it also contains cross-reference data for deposit accounts, it is defined as file number 9 for the Deposit Account System. |
8 |
ForeCash Master Accounts |
This file contains the master account records for ForeCash. |
9 |
Lookup (for each application) |
The lookup file is a cross-reference file and is used to access a particular customer record by account number when the customer number is unknow. |
9 |
G/L Average Balance |
This file contains two records for each general ledger account. The records store average balance information for the current year and for last year. |
9 |
Inquiry Log |
This file is used to log all accesses through the BANCADO Inquiry System for management review. The file size will depend on the maximum number accesses and the frequency of the running of the clearing function. |
9 |
ForeCash General Purpose |
This file is used to temporarily store information during ForeCash operation. |
9 |
ForeCalc User Work Area |
One single track user work area must be available for each station permitted to access ForeCalc. |
9 |
Sort Work |
This area is used for temporary storage of sort information during sort,
merge, and fetch cycles. In most |
END OF SECTION 1