The Credit Risk Management Platform supports the import of existing client master data and transactional data from third party applications, e.g. core banking systems. All data can also be entered manually using an intuitive web-based front-end. This includes both master data from a single obligor and relationship data for managing groups of related companies. In addition, facility and collateral data can be fed into the system to establish related risk rating and credit origination processes, e.g. LGD ratings, credit pricing. The Client Management Module is seamlessly integrated with the platform’s other credit risk management modules. This includes the risk assessment of a company’s financials and calculation of a risk rating on both an individual company level and an aggregated group level.
The ACTICO Client & Facility Data Management Module is available on premise or in the cloud. Discover ACTICO Cloud Services!
Master data (e.g. obligor data, grouping
information) and transactional data (e.g. facilities, collaterals) are stored
centrally in the database. Data can either be imported from existing data
sources, e.g. core banking, or created manually in the application.
The Client Management module provides standard
interfaces for data exchange and synchronization with existing systems of
record, e.g. client relationship management, core banking. The integration is possible on a database level or via standardized APIs.
Master and transactional data can also be captured manually by end users via web-based front-ends. This approach is required for the rating of prospective companies that do not yet exist in the system of record, such as a bank’s core banking system.
The Client and Facility Management module enables grouping of counterparties, e.g. to satisfy regulatory requirements related to the management of groups of connected counterparties or borrower units as part of the risk assessment process.
Calculation of LGDs, risk-sensitive credit pricings and processing new credit applications require data on existing facilities and collaterals. The software supports the import and management of such credit-related data and mapping between obligors, groups of obligors, facilities and collaterals.
The Client Management module is seamlessly integrated with the platform’s operation credit risk management modules. This includes the assessment of a company’s financials or calculation of a risk rating on both an individual company level and an aggregated group level.
“With the ability to integrate the rating system with the bank’s core banking system, data could be transferred both upstream and downstream automatically, eliminating the manual transmission previously required.”
The system enables configuration and editing of all main entities. This includes adding new or amending existing data attributes on obligors, facilities, or collaterals. The specific attributes can be maintained manually in the application or imported via the interfaces from third party applications.
The client management module is seamlessly
integrated with the operative credit risk management modules. This enables
the consolidation of financial statements or the calculation and assignment of
ratings, e.g. within groups of connected companies.
The module managing client master data supports all relevant regulatory requirements, e.g. to define and assess groups of connected clients in accordance with the Capital Risk Regulations (CRR article 4, paragraph 1, point 39) or the “principles for effective risk data aggregation and risk reporting” (BSBC 239).
All master and transactional data is accessible by
a comprehensive reporting environment. The client and facility structures can therefore
be aggregated with the data sets of the other modules, such as financial statements,
risk ratings and credit applications.
Client master data is primarily
maintained in a bank’s existing system of record (e.g. core banking systems).
The application dramatically reduces integration costs with these back-end
systems by using standard interfaces for data import and synchronization.
All data are stored in a
central database. All modification of master data is tracked and stored as
historic revisions in the system. Subject to specific permissions, users can
view and compare historic revisions of master data records.