Transactional Core Layer

 

Components that make up the core layer:

 

(a) People: management and maintenance of natural persons and Law relating to the financial institution through contracts, or that might be associated with them in the future as a result of new linkages.

 

(b) Product Catalog: It allows the definition and maintenance of products and services sold by the Bank, enabling proper operation by setting any of its attributes.

 

(c) Accounting: Allows the creation of the chart of accounts and accounting records of the various transactions of the entity. This module is based on parameterization and flexibility to adjust to changes that may occur in the future, minimizing the impact on other applications that is based on the strategy of a financial institution, and which apply to high value added business.

 

(d) Contract Management - Agreements: Allows to establish the negotiation and contracting policies of the financial institution, as well as the established contracts with third parties. This system component supports activities from the application of a Contract to the reporting of the denial and file, or full operation of the approved contracts.

 

(e) A.M. Account Movements Management: All moves or passes accounts automatically produced from the operation supported by transactional and transaction execution philosophy modeled and executed under Workshops & Engines.

 

(f) N.B. Notes and Balance Management: All operational movements that cause registration of notes and update any of the balances involved, automatically produced from the operation supported by transactional and transaction execution philosophy modeled and executed under Workshops & Engines.

 

(g) E.J. Electronic Journal: Manage traceability and audit of all transactions and movements of any kind. Provides an interface capable of handling cancellations, reversals or any particular intervention was required.

 

(h) I.M. Incident Management: Manages automated manual intervention or compromise of any incident produced any instance of the circuit.

 

(i) I.C.U. Institutions, Centres, Users and Profiles: Cross-type module which supports the definition and maintenance of Financial Institutions, its organizational structure and its staff, allowing to adapt the functioning of the organizational model of the financial institution. It also allows to the Finantial Institutions to define all levels of permissions and responsibilities of all actors involved in the Model.

 

(j) Gatherings: cross type module which supports all communication processes with external entities, allowing the definition of interfaces, ETL or web services, as required, to ensure the information interoperability from different satellite organizations linked to the financial institution.