Articles — BCBS 239 and RDARR — page 2
Analysis that revisits specific points of BCBS 239 and the ECB's RDARR Guide.
20 business days: what the ECB requires for risk reporting speed
Both texts remain mostly qualitative — except on one point: the ECB sets a precise numerical benchmark for judging whether an institution produces its risk reports fast enough. Here's why.
What should a good risk report contain? The 5 qualities of BCBS 239's Pillar III
Accurate data alone doesn't guarantee good decisions: the reports built on it also need to be accurate, comprehensive, clear, produced at the right pace and delivered to the right people. BCBS 239 makes this five separate principles.
Who and what does BCBS 239 apply to? The exact scope according to the Basel Committee and the ECB
BCBS 239 isn't limited to "risk data" in the abstract. The Basel Committee's text and the ECB's Guide define a precise scope — banks, models, reports and indicators — that goes further than is often assumed.
Who must do what? RDARR's lines of defence according to BCBS 239 and the ECB
BCBS 239 mentions it in a single footnote; the ECB's RDARR Guide details it over several pages. How responsibilities are actually split between data owners, governance, validation and audit.
BCBS 239, ten years on: why the ECB still considers implementation insufficient
From the 2007-2008 crisis to the 2024 RDARR Guide: how the ECB found, review after review, that no significant institution — not even the most systemic ones — fully applied the Basel Committee's 14 principles.