The European Banking Authority: Introduction and status of FINREP and COREP V2.0

Transcription

1 The European Banking Authority: Introduction and status of FINREP and COREP V June 2013 Stockholm Andreas Weller Head of IT, EBA Chairmen of XBRL Group EBA EBA European Banking Authority

2 Context The CRDIV Implementing Technical Standards will significantly change the XBRL landscape in the banking sector, across the EEA, on the 1 st Jan

3 2014 XBRL MAP >1 st level >2 nd level 3

4 Supervisory Reporting 4

5 Role of Datapoint Model DPM supervised entity Data requirements + concepts definitions Data Model?? XBRL taxonomy analysis and audit supervisor data 5

6 Data Exchange FINREP COREP TAXONOMY Catalogue of concepts, definition of exchanged information INSTANCE DOCUMENT Report containing facts (business data) DPM Catalogue of concepts, definition of meta and business related information 6

7 Interim ITS Templates Validation Rules DPM Database and explanatory document Data point definitions Dimension properties of tables Dimension usage by table group Hierarchies Dictionary of elements 7

8 Explanatory Document 8

9 Dimensional Properties of Tables 9

10 Data Point Definitions 10

11 Dimension Usage by Table Group 11

12 Final ITS Final package of DPM will result in ITS in June/July This will go to the European Parliament Taxonomy will be build according to ITS 12

13 XBRL Taxonomy FINREP V2.0 COREP V2.0 Multi dimensional Validation Rendering / Table link-base According to the latest XBRL standards 13

14 EBA XBRL Subgroup recommendations XBRL is the 2nd level data exchange format Two Taxonomies - FINREP and COREP All EBA defined validations will be implemented in the taxonomies NSAs will be able to provide labels in multiple languages 14

15 Links to CEN Project CEN Workshop XBRL proposals will be adopted where they are suitable. We will pursue harmonisation with other ESAs via CEN and a common namespace where applicable We suggest NSAs using XBRL for 1st level reporting also follow CEN proposals. 15

16 Different Purposes The DPM and the taxonomy are intended to fulfill different needs!!!!! 16

17 Different Purposes The DPM and the taxonomy are intended to fulfill different needs: Business use DPM to clarify and understand the reporting requirements NSA IT use taxonomy to transmit data to EBA. NSAs may use taxonomy to receive data from Credit Institutions. 17

18 EBA Data Point Model Motivation Regulations 2 4 U? Templates 4 U 2? Instructions * % Validations Regulators Financial Institutions 18

19 Communication + Clarity Regulations U42 Templates Instructions Validations DPM U42 U42 Regulators Financial Institutions 19

20 ITS map European Banking Authority ITS map April 2013 XBRL Draft FINREP P Architecture review Taxonomies generation DPM Excel files DPM Database Anotated Templates Basic Metamodel Sample metadata extraction Proof of concept FINREP templates Decomposed Templates Analysis Matrix COREP templates Integration Taxonomy Architecture P Public Consultation Advanced Metamodel DB Quality checks Analytical Platform DPM Architect tool Interim ITS P Integrity checks & loading Metadata exchange Tool testing DB Interface Taxonomies testing Final ITS 5 P DPM+XBRL evolution 6 Analytical model Instance integration Taxonomy generation

21 ITS Development: Iterative Process Templates Analysis Modeling...hitherto Structure checks DPM Excel Metadata loading Quality checks DPM Database Metadata extraction DPM-XBRL Generator Generation finalisation & evolution... Test results XBRL Taxonomies 21

22 Quality Review 22

23 The Frameworks COREP FINREP Leverage Liquidity Coverage Net Stable Funding Capital Adequacy Group Solvency Credit Risk IP Losses Operational Risk Market Risk Large Exposures Asset Encumbrance Primary Statements Assets & Liabilities Financial Asset Disclosures & Off Balance Sheet Income & Equity Financial & Non-Financial Disclosures, OBS Forbearance Non-performance

24 Expected Results Harmonized EEA Data Transparency Consistency 24

25 Software Vendors The market will increase Please adapt your tools Report the capability & compliance of your tools during the public consultation 25

26 European Banking Authority Vision Timeline All standard regulatory software for financial institutions will be compliant to FINREP and COREP as the main data exchange format XBRL becomes the primary regulatory reporting format EC adopts parts of FINREP and COREP in its standard taxonomy XBRL regulatory reporting becomes real time Majority of NSAs adopt XBRL for regulatory reporting FINREP and COREP get used in mobile computing for other purposes Regulatory taxonomies share an EC name space ITS published XBRL mandatory for data transfer from NSA to EBA

27 Contact information Andreas Weller European Banking Authority Floor 18 Tower Old Broad Street London EC2N 1HQ United Kingdom t +44 (0) f +44 (0) info@eba.europa.eu 27