To facilitate the exchange of information among components selected by the banks, ABIS is designed around a central information store. This information store is responsible for the creation and retention of information commonly used throughout the entire program.

Core information is broken down into two areas. The first is user-defined items that are used in the processing of transactions or the identification of information. This includes Bank and Customer Information, Exchange Rates, Fees, Transaction Types, Ledger Account codes and Depo Bank codes.
The second set of information is program-specific items,which are also user defined. These include

calculation methods for currency conversions, translation files for head office accounts, and computer security files.

The purpose for placing these within a common store of information is to provide a single point of creation for items that are used throughout the program and to provide users with the greatest degree of flexibility in easily tailoring their program. By providing users with an ability to easily create transaction types, information can be sorted and accessed with greater speed and flexibility. In addition, a central information store reduces the potential for information to be duplicated. Clients are entered in one place, bypassing the creation of duplicate accounts that make obtaining a view of your relationships impossible.




ABIS's bank and customer information elements allow financial institutions to define their relationships with counterparties and clients. Besides standard information relating to name, address and contact information, ABIS also captures group and risk identifiers within this file. Customer or Bank groups can be created so that an institution's relationship can be determined at various levels. In addition, institutions establish ultimate and current locations for the client, as well as industry categories, in order to be able to segment clients and more easily determine risk. As such, information can be produced on clients within a certain geographical region in a certain industry category in order to respond quickly to changing risk environments.




All information is eventually tracked to a series of ledger accounts, whether within ABIS or as part of an external ledger system. ABIS allows financial institutions to establish their own Chart of Accounts in order to provide continuity between old and new applications.




Because information is constantly changing, ABIS can be linked to various information providers to provide updated content. Interest and currency rates can be captured periodically and use to keep transactions valued correctly.



To profitably manage a financial institution, data cross sections must be available so that analysis can be performed both bank-wide and down to the individual product level. ABIS enables financial institutions to define the types of transactions that they are performing, as opposed to lumping everything into a general category. This enables an institution to retrieve information on transactions with a certain purpose such as project financing or working capital, increasing the control an institution has on its business.




ABIS's limit management program enables the bank to establish limits for nations, counterparties and transactions. Tied to standard rating agency information, users establish a model that is linked both to the Customer information file to determine country limits for clients as well as purpose limits for user defined purposes. ABIS also establishes foreign exchange trading limits for use by dealers. The transaction modules access these limits in order to determine if the transaction falls within the bank's accepted risk profile. Appropriate authorization can override this function.


 


| Design Philosophy | ABIS Structure | Core Elements | Transactions | Repositories | | Each of Modules | Product Features |