Who does BCBS 239 apply to?

To global systemically important banks (G-SIBs) since 2016, and by extension from national supervisors to domestic systemically important banks (D-SIBs). Many non-systemic institutions adopt it as good practice because it underpins the rest of their regulatory reporting.

What is the real technical challenge?

Data lineage and quality, not the final report. You have to be able to trace every figure back to its source, ensure consistency across sources, and re-aggregate quickly in response to supervisory requests or stress scenarios. It is a data architecture and compute capacity problem.

How does it relate to FRTB, IFRS 9 or stress testing?

BCBS 239 is the data layer that feeds all of those calculations. If risk data aggregation is weak, market risk (FRTB), accounting impairment (IFRS 9) and stress tests inherit that weakness. That is why it is usually addressed as a cross-cutting foundation.

Glossary · Regulation · Risk data

BCBS 239 (RDARR) — risk data aggregation and reporting

BCBS 239 is the Basel Committee's 14 principles (2013) for a bank to aggregate its risk data and generate reports in an accurate, complete, timely and adaptable way. It applies to global systemically important banks (G-SIBs) and, by national extension, to domestic systemically important banks. In practice it is not a reporting problem: it is a data architecture and quality problem.

The 14 principles, in four blocks

Governance and infrastructure — board accountability and a data architecture that supports aggregation even under stress.
Aggregation capability — accuracy and integrity, completeness, timeliness and adaptability of risk data.
Reporting practices — accuracy, coverage, clarity, frequency and distribution of reports.
Supervision — review, tools and cooperation among authorities.

Why it is a data (and HPC) project

The real obstacle is not laying out the report, but having lineage, quality and granularity of risk data and being able to recalculate under stress within short timeframes. That requires a unified data architecture (not silos by area), end-to-end traceability and the compute capacity to re-aggregate complete portfolios. Fragmented cores and rigid batch processes are where these programmes get stuck.

How Vermont Solutions helps

Risk data architecture ready to re-aggregate

We modernise the core and the data layer to support aggregation with lineage and quality: extraction from legacy sources, end-to-end traceability and compute capable of re-aggregating portfolios under stress.

See legacy and core modernisation →

Fuentes

BCBS 239 — Basel Committee (BIS)

Last updated: 2026-06-19. Editorial content by Vermont Solutions, citable with attribution. This does not constitute regulatory advice; verify the current version at bis.org.