Case Study: BCBS 239 Compliance

Solution

• Full risk data aggregation and risk reporting (BCBS239) compliance

Banking area

• Treasury IT

• Regulatory Reporting Areas Including:

  • Counterparty Credit Risk

  • Market Risk

Skill set

• MS Visio

•  Microsoft BI

• Informatica

• Murex

• SQL

Themes

• Banking Regulation

• Market Risk And Counterparty Credit Risk

• Process Automation

Insights

• Key to the role was ensuring that all existing documentation was up to date and accurate

• Buy in from important stakeholders at the start of the project was key

• Understanding the data lineage of all regulatory reports before data service level agreement phase

• Ensuring all approximations were relevant to the regulatory reporting area

Overview

A large retail bank was tasked with complying with several principles enacted by the Basel Committee on Banking Supervision under BCBS 239. The bank had to develop and account for BCBS 239 controls around data, IT, systems and processes to ensure that risk data used in producing risk measures reported to external and internal stakeholders was accurate, complete and produced in a timely manner.

Monocle was tasked with unpacking the data lineage of
each of the risk measures that were contained in the risk reports communicated to various stakeholders. Monocle developed the controls for the provision and consumption of risk data, the relevant data service agreements and the processes for reporting on data quality. This enabled the bank to better understand various intricacies within their
risk process.

Results 

• Development of Data Service Agreements

• Process optimisation for each risk area within the bank

• Full compliance with relevant regulation

Key skills required 

• Management of multiple stakeholders within the risk function of the bank

• Mapping out of key risk data across complex system and processes

• Intricate knowledge of relevant international and local regulations pertinent to the risk function