Successful assessment of data and business logic requirements for the migration of the liquidity risk management solution to QRM
Treasury and IT Systems
BCBS 239 Expertise
Liquidity Risk Management and Reporting
Risk Calculator Migration
Banks must dedicate significant time and effort to accurately and comprehensively unpack years of code and business rules in legacy systems
Migrations should be flexible and avoid delays so that initial analyses do not become irrelevant
Understand the granularity of source system data and business rule attribute requirements before embarking on a system migration to QRM
To improve the agility and long-term value of its liquidity risk management capabilities, a large retail, corporate and investment bank initiated a project to migrate its in-house risk management solution to a vendor-product solution – QRM.
As part of the migration programme, Monocle was tasked with assessing and documenting the various existing data sources and business rules that existed in the client-built solution that was used for liquidity risk reporting and risk management. We were also tasked with building the initial daily and monthly automated process to source, transform and centralise the datasets that were stored across the organisation.
Monocle ensured that data quality controls were implemented to achieve compliance with BCBS 239 principles and built the reconciliations to ensure the dataset was aligned to the bank’s balance sheet.
Comprehensive assessment and documentation of existing datasets
Automated process to source, transform and centralise the required liquidity risk data
Compliance with BCBS 239 principles
Technical expertise to unpack large and convoluted ETL and data preparation code sets
Automation of data sourcing, conformance and reconciliation with consideration to BCBS 239
Ability to effectively assist the collaboration between Treasury and IT
Explore the trending topics across the banking and insurance industries