As the 1st January 2019 deadline for BCBS 239 is closing in on DSIBs it becomes clear that none will be fully compliant, especially since implementation plans are expected to run till 2020. When it comes to the GSIBs, the January 2016 deadline has already come and gone – but where has this left things? Most GSIBs are now materially compliant, working towards being fully compliant, but it is difficult for all banks to understand what exactly being fully compliant means when the risk data aggregation and reporting regulation is principles based, with not only one way to deal with it. Progressing towards full compliance is tricky with a big regulation impacting more than just reporting, but also data management in the both risk and finance departments (the fundamental areas of a bank). At this point in time banks will be looking to confront self assessment of what they have implemented in order to improve processes but it is difficult to know exactly what the regulators want when Basel and ECB are not agreed on their views of BCBS 239 implementation. With this in mind, in this marcus evans conference we will look at the continued efforts placed to achieve sustainable and full compliance of BCBS 239 with focus on data lineage, taxonomy and consistency.’
Attending This Premier marcus evans Conference Will Enable You to:
- De-silo risk data governance through a connected central database to support data lineage
- Achieve consistent risk reporting by upholding shared taxonomy and data management practices
- Embed BCBS 239 in the wider risk framework to transition into a state of business as usual
- Explore an outlook beyond BCBS 239 examining how it supports and overlaps with other regulations
Learn from Key Practical Case Studies
- SEB demonstrate how to create and utilise a shared data repository as a shared risk and finance data hub for the entire business
- EDM Council show the benefits to data consistency of moving beyond a data dictionary to data ontology
- Nedbank reveal how introducing a CDO can help to make risk data aggregation and risk reporting a priority throughout the business
- Natixis explain how to support FRTB projects through good risk data practices as upheld by BCBS 239
