bcbs 239 interview questions

Collibra: Roundtable – BCBS 239 & CCAR Programs

Dylan Jones: Finally, what is one parting piece of advice you can share with our audience?

And that’s how & when the epiphany occurred: it’s all about data, everything else is peripheral.

Additionally, the organization should start with a couple of LOB’s or Subject Areas to roll out the operationalization that sustains success.

Such events have been made available to all LOBs so that folks across all team and management layers are able to understand and appreciate the efforts, thereby applying their learnings in BAU mode.

Data Governance programs most definitely need the vision, mission and strategy part chalked out clearly and that too, upfront.

Principles for effective aggregation and reporting of risk data

To sum it up, these principles aim at enhancing the banking procedures related to financial risk management and corresponding decision-making processes. The fundamental principles are:

  • Completeness, integrity, and granularity: both internal and external reporting system must cover all the main risks the bank is exposed to. Moreover, they must do it efficiently and have an appropriate system of controls.
  • Governance: Top management and risk committees should be informed at least once a year about the status of alignment to the BCBS 239 principles (completeness, Data Quality, reporting timeliness); significant gaps should be the subject of an action plan for remediation.
  • Adaptability and responsiveness in case of financial crises: the reporting system must guarantee flexibility to respond also to immediate specific requests. These could be made in crisis situations, or as a consequence of internal developments, or by supervisory bodies.
  • [/vc_column_text][vc_column_text css=”.vc_custom_1627389933721{margin-top: 40px !important;}” el_class=”entry-content”]

    On what focus points should we base a methodology to achieve regulatory compliance?

    We identify three key points:

    GOVERNANCE AND IT INFRASTRUCTURE

    Strengthening the current Data Quality Framework and its system of controls by:

  • extending Data Governance to the activity of risk data processing and the preparation of the related reporting
  • developing the IT architecture towards supply chain integration and efficiency in preparing the reporting
  • RISK DATA AGGREGATION CAPABILITIES

    Banks should be able to monitor financial risks in a reliable way via:

  • overseeing data accuracy and integrity while minimizing manual intervention
  • constant andcomplete updating of the data
  • adaptible and flexible data to meet the specific requirements
  • RISK REPORTING PRACTICES ENHANCEMENT

    Ensure the data is available for the right people at the right time via:

  • data accountability, guaranteed by Data Governance
  • reporting accuracy
  • completenes, clarity, and timeliness of the reports
  • creating cooperation tools for the various automated business actors
  • [/vc_column_text][vc_column_text css=”.vc_custom_1628083102902{margin-top: 40px !important;}” el_class=”entry-content”]

    Despite investment, compliance levels are decreasing

    In recent years, banks have invested significantly in their data and technology programs. These largely support remediation for regulatory initiatives such as BCBS 239. Survey respondents revealed that the programs are mostly led by the risk and finance functions and run centrally. Two-thirds said that they are aligning their programs with an overarching data vision and strategy. The immediate focus is on getting the basics right: improving operations and IT, enhancing risk management, and better supporting the business. Many banks are also deepening senior-management accountability to improve program governance and data-quality awareness, as these are key topics for regulators. In developing a culture of data-quality awareness in their business and support functions, banks have also begun to tackle the question of data ownership, seeking to harmonize overlapping functions and increase collaboration among risk, finance, and treasury.

    Investments in fundamental data capabilities have varied. Value-added efforts such as automation are mostly in the beginning stages or are scheduled for a later date.

  • G-SIBs. Most G-SIBs have focused on documentation and selective remediation. About one-third are documenting data lineage up to the level of provisioning data elements and including data transformation—though several are questioning the value of data lineage in the context of broader data controls. Most banks are working on enabling specific IT systems rather than particular use cases or business capabilities. All US and most European and Asian G-­SIBs have conducted an independent validation. To ensure an independent perspective on the state of remediation, the validation is usually conducted by an internal team reporting to the chief risk officer. Several banks are complementing their internal validation with external support to build capabilities in their second-line function.
  • D-SIBs. European and Asian D­-SIBs are accelerating their remediation programs, as evidenced by rising investment levels. Three levels of maturity have been identified. At the highest level are D-­SIBs adhering to the G-SIB timeline—such as Canadian banks, due to a stronger push by local regulators. A second group of D-­SIBs began working on risk data and technology early on but have not yet finalized their programs. The last group are the late starters, which have only recently begun to work on risk data and technology.
  • Despite the data and technology investments, however, overall BCBS 239 compliance levels have declined since 2015 (Exhibit 1). Our respondents’ self-assessment is supported by the latest Basel Committee progress report on risk data aggregation and risk reporting, which finds that banks’ overall level of BCBS 239 compliance remains unsatisfactory. In fact, local supervisors have concluded that only one bank can be considered in alignment with the principles. Highlighted in the Basel Committee report is the regulators’ assessment that, based on the current state of BCBS 239 remediation, banks that began the process in 2013 will need an average of five to six years to complete it. Exhibit 1

    We strive to provide individuals with disabilities equal access to our website. If you would like information about this content we will be happy to work with you. Please email us at:

    A few factors have conspired to produce the more conservative compliance assessments. Through discussions with regulators and the sharing of industry best practices, banks now have a deeper understanding of the technical requirements for compliance. Through independent validation, many banks developed a better understanding of their own capabilities and discovered previously unknown gaps in coverage. A further contributing factor has been that banks have expanded the scope of their regulatory programs beyond risk and finance to include data for management and regulatory reporting, operational processes, and material business decisions.

    Around the globe, most bank executives believe regulators will continue to increase requirements for data capabilities. The present regulatory environment is thus viewed as only the starting point (Exhibit 2). The scope of regulation is expected to widen, with thickening coverage for risk metrics, reports, data, and legal entities. One result is that some banks, especially in Europe, have chosen to be “constantly materially compliant,” a status just shy of full compliance, because of ongoing long-term remediation programs. Exhibit 2

    We strive to provide individuals with disabilities equal access to our website. If you would like information about this content we will be happy to work with you. Please email us at:

    More frequent regulatory exams also are expected. Many regulators have already begun targeted reviews, such as the European Central Bank’s thematic review of BCBS 239 compliance for G-SIBs. They are also doing more live testing, through CCAR (in the United States) and other regulatory stress tests. Almost all G-SIBs and about 40 percent of D-SIBs across geographies have conducted an independent validation of their BCBS 239 capabilities, to meet a regulatory requirement and prepare for further discussions with regulators. Respondents indicate that US regulators have been the most assertive; in Europe regulators are issuing further standards to improve consistency, while in Asia the regulatory climate is less intense. The regulatory environment will thus continue to tighten, with a cluster of regulations relating to risk data and technology, including BCBS 239, CCAR, FRTB, GDPR, and RRP, posing capability challenges for the largest banks.

    While no one expects to see global standards for risk data and technology, general approaches are emerging within regions and have been codified in some countries (such as Germany’s “MaRisk,” or minimum requirements for risk management). Regulators have helped recently with more transparent definitions of data quality. The European Central Bank, for example, has developed BIRD (Banks’ Integrated Reporting Dictionary), a database with technical guidelines for reporting data, and has issued reviews of the quality of submitted reports, findings, and resolutions covering common reporting, financial reporting, the liquidity coverage ratio, the net stable funding ratio, and others.

    While self-assessed compliance levels have dipped and greater regulatory pressure is expected, banks’ spending on risk data and technology will likely vary by region (Exhibit 3). On the one hand, American G-SIBs are expected to maintain current budgets, because of either regulatory scrutiny or an appreciation of the competitive advantage these capabilities afford. European and Asian G-SIBs and American D-SIBs, however, are expected to reduce their level of investments by around 25 percent. Declining budgets pose significant challenges for many banks and may become a factor affecting compliance levels well into the future, as the impact of changes in investments may take several years to materialize. Exhibit 3

    We strive to provide individuals with disabilities equal access to our website. If you would like information about this content we will be happy to work with you. Please email us at:

    Most surveyed banks are already facing challenges in improving their overall data quality. Most commonly, a lack of front-office controls is leading to poor data quality at the systems of origin (Exhibit 4). Many banks also struggle with inefficient data architecture, often in legacy systems, which create operational inefficiencies and make it harder to improve data quality. Addressing these twin challenges usually requires more, not less, spending. Exhibit 4

    We strive to provide individuals with disabilities equal access to our website. If you would like information about this content we will be happy to work with you. Please email us at:

    At banks where budgets are shrinking, however, two factors may be at work. The value of the data transformation may be inadequately appreciated by the business, while board and senior-management support, which has been generally growing, is still relatively modest. With the regulatory bar still rising, many banks find themselves running in place, still fixing the basics after having made significant investments over the past several years. They may be losing the focus needed to get to the finish line.

    FAQ

    What are the principles of BCBS 239 and why it was critical for banks?

    The fundamental principles are: Completeness, integrity, and granularity: both internal and external reporting system must cover all the main risks the bank is exposed to. Moreover, they must do it efficiently and have an appropriate system of controls.

    What are the aims of the BCBS 239 regulation?

    BCBS 239 presents a set of principles aimed at strengthening banks’ governance frameworks, enterprise-wide risk data aggregation capabilities and internal risk reporting practices. In turn, effective implementation of BCBS 239 is expected to enhance risk management and decision-making processes at banks.

    What is data governance?

    Data governance means setting internal standards—data policies—that apply to how data is gathered, stored, processed, and disposed of. It governs who can access what kinds of data and what kinds of data are under governance.

    Related Posts

    Leave a Reply

    Your email address will not be published. Required fields are marked *