21 July 2018
Paul McPhater

Getting down to the data

Paul McPhater - Markit

12Posts 33,123Views 0Comments

BCBS 239: Data First, Reporting After

25 July 2014  |  2829 views  |  0

Without data that is accurate, reconciled and validated, risk reporting may be useless.

This is Part 2 in a four-part series on the key areas of the BCBS 239 risk data aggregation and reporting guidelines. View Part 1 here.

In its stocktaking report on BCBS 239 progress at the end of last year, the BIS highlighted how banks had assigned themselves higher ratings on the risk reporting principles than they did on the corresponding data aggregation principles. This raised the question as to how reliable and useful risk reports can be when the data within these reports and the processes to produce them are not in place.

The reports being produced need to be accurate, clear, complete, useful and frequent. The end game is simple: to enable informed decisions based on accurate information.

When you consider what a risk report usually looks like – a bunch of spreadsheets – and how long it has taken to produce – typically not a quick process, but rather a complex and time-consuming one that happens across silos – the ongoing challenge becomes clearer.

Exact reporting requires data that is accurate, reconciled and validated. Outside of the data architecture issues, an historic reliance on manual processes and inconsistencies in reconciliation procedures also hamper progress. BCBS 239 also requires firms to fully incorporate risk appetite into their risk reporting, which adds an additional layer to the challenge.

Risk management executives must be empowered to make informed decisions, and all roads lead back to the data. As a result, it's vital that banks have a system in place that can cope with the vast volumes of data across the institution. BCBS 239 is big on interdependencies across all three areas of the principles: governance and infrastructure, risk data aggregation, and risk reporting – without adherence to principles governing data, reporting adherence simply cannot happen. 

TagsRisk & regulationPost-trade & ops

Comments: (0)

Comment on this story (membership required)

Latest posts from Paul

When one yes equals BCBS 239 compliance

23 March 2015  |  2140 views  |  0 comments | recomends Recommends 0 TagsRisk & regulation

RDA: do the responses stack up?

24 February 2015  |  2085 views  |  0 comments | recomends Recommends 0 TagsRisk & regulationPost-trade & ops

Risk data aggregation: what progress this past year?

10 February 2015  |  2083 views  |  0 comments | recomends Recommends 0 TagsRisk & regulation

Another Lehman’s legacy: connecting the data dots

19 November 2014  |  2817 views  |  0 comments | recomends Recommends 0 TagsRisk & regulationPost-trade & ops

Data audits: invaluable insights into costs

22 October 2014  |  2179 views  |  0 comments | recomends Recommends 0 TagsRisk & regulationPost-trade & ops

Paul's profile

job title COO Enterprise Software
location London
member since 2014
Summary profile See full profile »
COO Enterprise Software at Markit - based in London.

Paul's expertise

Member since 2014
12 posts0 comments
What Paul reads
Paul's blog archive
2015 (3)2014 (9)

Who's commenting on Paul's posts