Definition of BCBS 239
In January 2013, the Basel Committee on Banking Supervision (BCBS) published the “Principles for effective risk data aggregation and risk reporting”. Usage has settled on the name BCBS 239. The number, absent from the text, seems to come from the address of the document on the Bank for International Settlements website (bis.org/publ/bcbs239), where we read it on 12 November 2026. We did not find a French version there: the headings given here are our own wording, based on the English original.
The text starts from a lesson of the financial crisis that began in 2007 (paragraph 1): some banks were unable to aggregate their exposures or identify their concentrations, quickly and accurately, at group level. It calls risk data aggregation the defining, gathering and processing of this data according to the bank’s risk reporting requirements (paragraph 8).
Fourteen principles, four groups
- Governance and infrastructure (principles 1 and 2): governance; data architecture and IT infrastructure.
- Risk data aggregation capabilities (3 to 6): accuracy and integrity, completeness, timeliness, adaptability.
- Risk reporting practices (7 to 11): accuracy, coverage of all material risks (comprehensiveness), clarity and usefulness, frequency, distribution.
- Supervisory review (12 to 14): review, remedial actions, cooperation between home and host authorities.
Principles 1 to 11 are addressed to banks, the last three to their supervisors.
Banks concerned and original timetable
Paragraph 13 addresses the principles first and foremost to systemically important banks, and leaves national supervisors free to extend them to other banks, proportionately. Paragraph 14 set January 2016 as the deadline for global systemically important banks designated by the Financial Stability Board in November 2011 or November 2012; those designated later would have three years after their designation. Paragraph 15 strongly suggests that national supervisors apply the principles to domestic systemically important banks, three years after their designation. According to paragraph 19, the principles also apply to processes entrusted to third parties.
What the text expects of the data itself
Several expectations read like a data governance programme: integrated taxonomies across the group, with single identifiers or unified naming conventions for legal entities, counterparties, customers and accounts (paragraph 33); defined roles for data ownership, on the business side and on the IT side (paragraph 34); a “dictionary” of the concepts used (paragraph 37).
Others concern data quality: controls as robust as those applied to accounting data and a reconciliation with sources (paragraph 36), documented manual processes (paragraph 39), and accuracy that is measured and monitored (paragraph 40).
BCBS 239, DORA regulation, data lineage: not to be confused
BCBS 239 is a Basel Committee document, not a European Union regulation. In May 2024, the European Central Bank published a guide on the same subject: it states that it uses these principles as a benchmark of good practice, and specifies that the guide creates no new requirement.
The DORA regulation, Regulation (EU) 2022/2554, deals with a different subject: the digital operational resilience of financial entities.
Data lineage is an instrument. The 2013 text does not use the term; the 2024 guide cites it.
A request from the risk committee, on a Friday
Suppose a banking group whose risk committee asks, on a Friday, for the group’s total exposure to a counterparty in difficulty. The leasing subsidiary and the retail bank do not identify this counterparty with the same identifier. The figure, rebuilt by hand in a spreadsheet, reaches the committee after the decision it was meant to inform.
Three principles are at stake: completeness (4), timeliness (5) and adaptability to ad hoc requests (6). The remedy points to paragraph 33: a single identifier per counterparty.
These principles add to the texts that frame a project in a financial institution, presented on our banking and insurance page.