Home / Wiki / R / Risk Data Aggregation (BCBS 239)

Risk Data Aggregation (BCBS 239)

Compliance Risk and ControlsUpdated 17 Nov 2026
Share

Risk data aggregation is the process by which a bank collects, processes and combines data on its exposures so that risks can be measured against its risk appetite and reported to management and supervisors. BCBS 239 is the common name for the Basel Committee on Banking Supervision (BCBS) document "Principles for effective risk data aggregation and risk reporting", published in January 2013 as the committee's 239th publication.

The principles respond to a lesson of the 2008 financial crisis: many large banks could not quickly and accurately tell how much they were exposed to a counterparty, sector or product across the whole group. BCBS 239 applies first to global systemically important banks (G-SIBs) and is recommended for domestic systemically important banks (D-SIBs). It is less a capital rule than a standard for governance, data and IT.

01

Background

During the crisis, banks with fragmented systems, manual workarounds and inconsistent data definitions struggled to answer basic questions, such as total exposure to a failing investment bank, within the hours or days that decisions required. The Financial Stability Board asked for improvements in risk data, and the Basel Committee responded with a set of principles rather than detailed rules. Banks identified as G-SIBs in 2011 and 2012 were expected to comply by January 2016, and banks later designated as G-SIBs within three years of designation.

02

The 14 principles

The 14 principles fall into four groups:

  • Overarching governance and infrastructure (principles 1 and 2). The board and senior management must own risk data quality, and the bank's data architecture and IT must support aggregation in normal times and in stress.
  • Risk data aggregation capabilities (principles 3 to 6). Data must be accurate and reconciled, complete across business lines, legal entities and risk types, timely, and adaptable to ad hoc requests during a crisis.
  • Risk reporting practices (principles 7 to 11). Reports must be accurate, comprehensive, clear and useful, produced at a suitable frequency, and distributed to the right people while keeping confidentiality.
  • Supervisory review, tools and cooperation (principles 12 to 14). Supervisors should review compliance, use remedial tools and capital or other measures where needed, and cooperate across borders.

The principles are deliberately linked. Accurate reports depend on accurate data, which depends on clear ownership, golden source data, consistent definitions and controls such as reconciliation of risk data with accounting data.

03

Implementation in practice

Banks typically respond with group-wide data governance programmes: data owners and stewards, data dictionaries and lineage tracing from source systems to reports, data quality metrics and thresholds, and automation that reduces reliance on spreadsheets. The work overlaps heavily with regulatory reporting, stress testing, resolution planning and financial risk aggregation for economic capital, because the same exposure data feed all of them.

Supervisors assess compliance through self-assessments, thematic reviews and on-site inspections, and some have imposed capital add-ons or required remediation plans. The European Central Bank (ECB) has made risk data aggregation a long-running supervisory priority and published a guide on effective risk data aggregation and risk reporting in 2024. In the United Kingdom the Prudential Regulation Authority (PRA) applies the principles to the largest firms.

04

Why compliance remains difficult

The Basel Committee's periodic progress reports have repeatedly found that few G-SIBs fully comply years after the 2016 deadline. Common reasons include:

  • Legacy systems inherited through mergers, with different customer and product identifiers that are costly to unify.
  • Heavy use of manual processes and end-user tools that are hard to control and audit.
  • Programmes treated as IT projects without lasting business ownership of data.
  • Principles that are broad and partly qualitative, which makes "full compliance" a matter of judgement.

Critics argue that the principles lack measurable requirements and that enforcement has been uneven between jurisdictions. Some also note that the principles were written before cloud computing, real-time data platforms and machine learning became common, so banks and supervisors have had to interpret how they apply to new technology and to data held by outside vendors. Supporters reply that the standard has driven substantial investment in data infrastructure and that its value showed in episodes such as the 2020 market turmoil and the 2023 bank failures, when supervisors asked banks for rapid, granular exposure reports. Good risk data also underpin risk exposure monitoring and limit frameworks across the bank.

Last updated 17 Nov 2026
Share this entry

Ref 1050000598