LogoLogo
  • Ellipse Overview
  • Phases of Ellipse
  • Background
    • Challenges of Regulatory Reporting
    • Possible Solutions
    • Digital Reporting and Granular Data
    • Understanding Data Needs of Stakeholders
  • Ellipse Phase 1: Proof of Concept
    • Two Jurisdictions, One Common Data Model
    • Cross-Border Data Model using Retail Mortgage Loans
    • Data Components for Retail Mortgages
    • Data Attributes
    • Data Definitions
    • Using the Common Domain Model (CDM)
    • Normalising Common Components
    • CDM Mortgage JSON
    • Programmable Reporting Logic and Machine Executable Reports
    • VIDEO: Demonstration of the Mortgage CDM
    • Our Findings
    • Next Steps
  • Annex
    • Terminology & Acronyms
    • References
  • About
    • Contact the Ellipse Team
  • LEGAL
    • Terms and Conditions of Use
    • Privacy Notice
    • Cookies Notice
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. Background

Challenges of Regulatory Reporting

PreviousPhases of EllipseNextPossible Solutions

Last updated 3 years ago

Was this helpful?

Supervisors today rely heavily on regulatory reporting to inform them of potential risks that may be forming in regulated entities, which can have broader implications for the financial system. However, there are challenges with the information that supervisors receive from regulatory reports, such as the ones listed below.

Challenge

Description

Template-Based, Aggregated

Regulatory requirements are often template-based and ask for aggregate data, meaning that data sets are fixed to a use case and hence the data received cannot be easily reused for other purposes. New reporting requirements are needed each time additional or ad hoc information is needed.

Data is inconsistently described

Reporting data is often sourced from legacy data systems within reporting firms that are not always integrated. This often results in heterogeneity of data for any given product or transaction – both within a bank and across different banks – as systems will describe these data differently.

Infrequent backward looking

Regulatory reports are submitted to supervisors from reporting entities on an infrequent basis (e.g every month or quarter). At times of heightened risk, the need for up-to-date data increases but given the static nature of regulatory reports, supervisors may not have the timeliest data to make informed judgments.

Different sources of data are not integrated

Information contained in regulatory reports are often linked with other types of information that may point to emerging risks, but these sources of information are not connected. For instance, information sourced from market data and news are often the first indications of emerging risks but it is difficult for supervisors to scan through the vast volumes of market and news data to assess which point to a need to take early action.

The challenge is how supervisors can form an accurate picture of exposures and have predictive insights into emerging risks using these data sets. Project Ellipse therefore explores how supervisors can better identify and assess emerging risks in real time to inform them of early supervisory actions that may need to be taken.

Document with solid fill
Clipboard Mixed with solid fill
History with solid fill
Server with solid fill