Principle 5: Timeliness – A bank should be able to generate aggregate and up-to-date risk data in a timely manner while also meeting the principles relating to accuracy and integrity, completeness and adaptability. A timely and accurate view of risk exposure, aggregated across credit counterparties and financial products could have
Principle 4: Completeness – A bank should be able to capture and aggregate all material risk data across the banking group. Data should be available by business line, legal entity, asset type, industry, region and other groupings, as relevant for the risk in question, that permit identifying and reporting risk
Principle 3: Accuracy and Integrity – A bank should be able to generate accurate and reliable risk data to meet normal and stress/crisis reporting accuracy requirements. Data should be aggregated on a largely automated basis so as to minimize the probability of errors. It seems logical that banks would want
Principle 2: Data architecture and IT infrastructure – A bank should design, build and maintain data architecture and IT infrastructure which fully supports its risk data aggregation capabilities and risk reporting practices not only in normal times but also during times of stress or crisis, while still meeting the other
Principle 1: Governance – A bank’s risk data aggregation capabilities and risk reporting practices should be subject to strong governance arrangements consistent with other principles and guidance established by the Basel Committee. My colleagues and I have written a series of posts on the principles of BCBS 239. In this
Interestingly, the Basel Committee’s Principles for Effective Risk Data Aggregation and Risk Reporting (otherwise known as BCBS 239) begins with a quote from T.S. Elliot’s The Rock: Where is the wisdom we have lost in knowledge? Where is the knowledge we have lost in information? In this age of big
