IBM Cognos Disclosure Management Version COREP FINREP Technical Notes

Transcription

1 IBM Cognos Disclosure Management Version COREP FINREP Technical Notes

2 Note Before using this information and the product it supports, read the information in Notices on page 23. Product Information This document applies to Cognos Disclosure Management Version and may also apply to subsequent releases. Licensed Materials - Property of IBM Copyright IBM Corporation US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

3 Contents Introduction v Chapter 1. Overview of COREP, FINREP, AE, and FP in IBM Cognos Disclosure Management Terminology Minimum system requirements for COREP, FINREP, AE, and FP Chapter 2. Taxonomy support Taxonomy version supported by IBM Cognos Disclosure Management for COREP and FINREP Data Point Modelling methodology Chapter 3. Synopsis of rules in the Implementing Technical Standard Rules for individual disclosures in Implementing Technical Standard Reporting frequency EBA Taxonomies roadmap and reporting dates Remittance dates National and regional differences Chapter 4. Structure of the taxonomy Files required for complete definition of the taxonomy Main folder structure Report types and entry points for COREP, FINREP, AE, and FP Rendering Chapter 5. Filing packages Repeating templates Filing indicators Chapter 6. Additional information Reference dates QName tagging and lookup lists Further information Notices Index Copyright IBM Corp iii

4 iv IBM Cognos Disclosure Management Version : COREP FINREP Technical Notes

5 Introduction This document provides support for COREP (Common Reporting), FINREP (Financial Reporting), AE (Asset Encumbrance), and FP (Funding Plans) in IBM Cognos Disclosure Management. The document describes the structure of the taxonomies for COREP, FINREP, AE, and FP and the links to regulatory sites. It also describes the different types of templates, such as open and repeating templates, and other related topics. Copyright IBM Corp v

6 vi IBM Cognos Disclosure Management Version : COREP FINREP Technical Notes

7 Chapter 1. Overview of COREP, FINREP, AE, and FP in IBM Cognos Disclosure Management This section describes the system requirements for COREP (Common Reporting), FINREP (Financial Reporting), AE (Asset Encumbrance), and FP (Funding Plans) in the IBM Cognos Disclosure Management Filing Plug-in, the terminology that is used, and the taxonomy version that is supported. Terminology This section describes terms that are related to COREP (Common Reporting), FINREP (Financial Reporting), AE (Asset Encumbrance), and FP (Funding Plans). CRD IV/CRR Capital Requirements Directive 4th version and Capital Requirements Regulations 4th version are the European specific implementation of the Basel III Accord and are extended to address other financial institutions by the EU. BASEL III The Basel III Accord that relates to Capital and Liquidity requirements for banks. COREP/FINREP/AE/FP Common Reporting and Financial Reporting together are the standards that realize CRD IV and CRR. The terms COREP, FINREP, AE, and FP are often used interchangeably. You can find more information at the following locations: CRD IV and CRR IV CRD IV and CRRIV ( background/ bkg07195/ bkg07195_en.pdf) CRD IV CRD IV ( CRR IV CRR IV ( Official Journal Official Journal ( JOHtml.do?uri=OJ:L:2013:176:SOM:EN:HTML) Basel III Basel III ( Important: The preceding links are correct as of the publication date of this document. Minimum system requirements for COREP, FINREP, AE, and FP This section provides information about the system requirements that are needed for COREP, FINREP, AE, and FP in IBM Cognos Disclosure Management. Copyright IBM Corp

8 To process the COREP, FINREP, AE, and FP taxonomies from the European Banking Authority, the minimum requirement is Cognos Disclosure Management Version (10.2 Refresh Pack 3, Fix Pack 1). Updates to the taxonomy set from the regulator might also require later Interim Fixes. 2 IBM Cognos Disclosure Management Version : COREP FINREP Technical Notes

9 Chapter 2. Taxonomy support Taxonomy support in this document includes the taxonomy location on the European Banking Authority website, the methodology that is used, and samples of valid and invalid instances. You can download the taxonomy package for COREP, FINREP, AE, and FP from the European Banking Authority (EBA) website at the following location: EBA publishes XBRL taxonomy for remittance of supervisory reporting by competent regulatory authorities ( You can see the links on the right side of the screen. Important: The preceding link is correct as of the publication date of this document. Taxonomy version supported by IBM Cognos Disclosure Management for COREP and FINREP This section describes the versions of the COREP, FINREP, AE, and FP taxonomies that are supported by IBM Cognos Disclosure Management as of 31 October The taxonomy versions from the central regulator, the European Banking Authority (EBA), that are supported by Cognos Disclosure Management are Version published 4 December 2013 (applicable as of March 2014), Version published 15 July 2014 (applicable as of September 2014), and Version 2.2 published 18 August 2014 (applicable as of December 2014). Important: Do not use previous versions of the taxonomy, for example the version that was published in September IBM provides no support for these previous versions. Data Point Modelling methodology The taxonomy for COREP, FINREP, AE, and FP uses Data Point Modelling methodology for its creation. The reporting requirements were defined in terms of spreadsheet templates and the analysis of each cell that is to contain data determines the dimensionality of the cell. This analysis is used to create the various dimensional metadata in terms of an XBRL taxonomy. The model is delivered as a Microsoft Access database together with the supporting artifacts from which the XBRL taxonomy was generated. Both the taxonomy and the supporting artifacts are available from the website of the European Banking Authority (EBA). Copyright IBM Corp

10 4 IBM Cognos Disclosure Management Version : COREP FINREP Technical Notes

11 Chapter 3. Synopsis of rules in the Implementing Technical Standard The rules for what data should be reported, and the timing and method for reporting are described in a document that was published by the European Banking Authority (EBA). The document Implementing Technical Standard describes the rules for the data that should be reported and the timing and method for reporting. You can find helpful details on some of the contents of Implementing Technical Standard in this chapter. The document is published at the following location: Draft Implementing Technical Standards with regard to supervisory reporting of institutions ( Important: The preceding link is correct as of the publication date of this document. Rules for individual disclosures in Implementing Technical Standard Reporting frequency Many disclosures are required under the Implementing Technical Standard (ITS). You can find instructions for disclosures on the ITS web page. Related concepts: Chapter 5, Filing packages, on page 11 You can obtain a filing package that enables you to set up the filing report that suits your NSA and EBA requirements. The rules that govern the reporting frequency for particular types of disclosure are established in ITS on the website of the European Banking Authority (EBA). The COREP module contains multiple templates with various frequencies, described in the following chapters: v v v v v Chapter 3 describes the format and frequency of reporting on own funds and own fund requirements, and financial information. Section 1 describes the format and frequency of reporting on own funds and own fund requirements. Section 2 describes the format and frequency of reporting on financial information on a consolidated basis. Chapter 4 describes the format and frequency of reporting on losses that stem from lending collateralised by immovable property. Chapter 5 describes the format and frequency of reporting on large exposures. Chapter 6 describes the format and frequency of reporting on leverage ratio. Chapter 7 describes the format and frequency of reporting on liquidity. For FINREP, the frequency varies from quarterly to semiannually to annually. Copyright IBM Corp

12 Forbearance and Non-performing exposures reporting is described in a separate draft ITS at the moment of writing. These templates are additional to the FINREP framework. The reporting frequencies can be found in the associated annexes: a55b9933-be43-4cae-b c90135b9 For AE, the frequency varies from quarterly to semiannually to annually. Read Chapter 7a article 16a of the Draft ITS (correct at the moment of writing): EBA+ITS Final+draft+ITS+on+Asset+Encumbrance.pdf/0239d2fe-ff97-4cb4-af04-60eef4808e6f For Funding Plans, the frequency is described in the following document (correct at the moment of writing): EBA-GL %28Guidelines+on+Harmonised+Definitions+and+Templates+for+Funding+Plans %29.pdf/69a06e39-5f9c-4e7f-b240-2c66f09a83c5 EBA Taxonomies roadmap and reporting dates Remittance dates The road map and reporting dates is documented in detail under Supporting Documents\EBA_Taxonomies_Roadmap_ xlsx in this compressed file: XBRL Taxonony and Supporting Documents.2.2.zip Financial institutions submit their reports to their national competent authority (National Supervisory Authority or NSA) according to the following schedule. 1. Institutions must submit information to the competent authority (NSA) by close of business on the remittance dates described in the following table: Reporting type Monthly reporting Remittance dates 15 calendar days after the reporting reference day Quarterly reporting 12 May, 11 August, 11 November, 11 February Semi-annual reporting 11 August, 11 February Annual reporting 11 February 2. If the remittance day is a public holiday in the Member State of the competent authority to which the report is to be submitted, or a Saturday or Sunday, the data must be submitted the following working day. 3. If institutions submit their financial information using adjusted reporting reference dates that are based on their accounting year end, as described in Article 2 paragraph 3, then the remittance dates can also be adjusted accordingly. The same remittance period from the adjusted reporting reference date is maintained. 4. Institutions can submit unaudited figures. Where audited figures deviate from the submitted unaudited figures, the revised audited figures must be submitted without undue delay. Unaudited figures have not received an external auditor's opinion, whereas audited figures have been audited by an external auditor who has expressed an audit opinion. 6 IBM Cognos Disclosure Management Version : COREP FINREP Technical Notes

13 5. All other corrections to the submitted reports must be submitted to the competent authority without delay. National and regional differences Some national and regional differences exist regarding how National Supervisory Authorities (NSAs) require financial institutions to submit reports. The XBRL taxonomy that is published by the EBA is for the use of each NSA to submit data to the EBA. Some NSAs also choose to use the same taxonomy for financial institutions to report to them. Other NSAs require different submission mechanisms, for example SURFI for France and customized proprietary XML formats for Austria and Slovenia. Other NSAs indicate that they plan to extend the Data Point Model or taxonomy, for example, Spain and Germany. Important: Determine the correct format for your own situation from your own NSA. Do not assume that the taxonomy from the EBA can be used in all cases. Chapter 3. Synopsis of rules in the Implementing Technical Standard 7

14 8 IBM Cognos Disclosure Management Version : COREP FINREP Technical Notes

15 Chapter 4. Structure of the taxonomy The structure of the taxonomy is described in full in the various documents in the website of the European Banking Authority (EBA). The taxonomy structure is documented in detail in various documents organized by taxonomy version and framework release on the EBA website. The documents can be downloaded as a compressed file: General Documentation.zip ( /XBRL+Taxonomy+and+Supporting+Documents zip/069c3bc2-a9e6-4c8d-a2ba-a02a3aeaaecf) Important: The preceding link is correct as of the publication date of this document. The following sections of this chapter describe some of the important concepts that are related to the structure of the taxonomy. Files required for complete definition of the taxonomy Main folder structure Three sets of files are required for the complete definition of the taxonomy. The three sets are produced by different parties: the EBA, the Eurofiling Group, and XBRL International. In the taxonomy package they are contained in the following subfolders: v EBA taxonomy files/ v Other referenced XML files (for convenience)/ v Other referenced XML files (for convenience)/ These files are local copies of information that can be found in the following locations: v European Banking Authority ( v Eurofiling Initiative ( v XBRL ( This fact is documented in the catalog.xml files in the folders EBA taxonomy files and Other referenced XML files (for convenience). Some of these files might not have been placed on the web in their canonical location, and therefore they can be used only locally. Important: The preceding links are correct as of the publication date of this document. The main folder structure is in the root directory of the website of the European Banking Authority (EBA). The root directory of contains a series of empty folders: Copyright IBM Corp

16 The crr folder contains the following subfolders: dict and fws. The content of the crr file is subject to change due to EBA taxonomy modifications. It might contain only an fws file. The dict folder contains the following subfolders: dom, met, and dim. v The dom folder contains one subfolder for each domain that forms part of the taxonomy, each identified by the two-character domain code. Each of these folders contains files that define the members of the domain in question and the hierarchies of those members. v The met folder contains the files that define the metrics, also referred to as primary items or concepts, and their hierarchies. v The dim folder contains files that define the dimensions in the model and, for each dimension, the relevant links to its associated domain. Each of the COREP, FINREP, AE, FP folders have an fws folder. Under each of these folders is one more sub-folder indicating the date of the ITS that governs the reporting (for example, its ). This structure allows for future expansion when new versions of the ITS are published. Under that is a folder indicating the release date of the specific version of the Data Point Model that the taxonomy represents. For example, for the July 2014 version, it is That folder is further divided into three subfolders: mod, tab, and val. v The mod folder contains the primary entry points or modules. v v The tab folder contains one subfolder for each table in the model in which are the relevant files pertaining specifically to that table or template. This structure is designed so that the.xsd file can be used as an entry point into the taxonomy pertaining specifically to that table and that table only. This can be loaded into a general purpose XBRL taxonomy viewing tool if you want to understand the specifics about that particular table (such as the hypercubes defined for it). The val folder contains all the formula linkbase files for the framework COREP or FINREP under which it lies. Each file name is similar to that of the table or tables that it relates to. For example, assetc_01.00_c_02.00_c_03.00.xml is the set of assertions that relate to tables or templates C 01.00, C and C Important: The preceding file names and links are correct as of the publication date of this document. Report types and entry points for COREP, FINREP, AE, and FP Rendering The entry points are automatically identified and used by IBM Cognos Disclosure Management based on the selected Framework and Report Type property of the Filing Report. Included in the taxonomy are the files that form the table linkbases to enable general-purpose XBRL tools to reconstitute tables that have similar layout to the original template. However, these files are not used by IBM Cognos Disclosure Management and are superfluous. Cognos Disclosure Management uses the actual Microsoft Excel templates that are provided by the regulator. 10 IBM Cognos Disclosure Management Version : COREP FINREP Technical Notes

17 Chapter 5. Filing packages You can obtain a filing package that enables you to set up the filing report that suits your NSA and EBA requirements. The filing packages that are obtained from IBM cover all types of templates. Closed templates A closed template is one whose size and shape are fixed and contains a known number of data points to be populated. Some closed templates are repeating in that they can be reproduced a known number of times depending on certain dimensional information, for example, the C a series of templates. The certain dimensional information is carried in the Z axis of the template with specific combinations of dimensional members being specified. For example: v Approach for prudential purposes = Standardised Approach v Exposure class = Exposures to central governments or central banks v Counterparty sector = Central governments or central banks This information is available from the template C a(002) in the file DPM Table Layout and Data Point Categorisation v2.2.xlsx provided by the EBA. This file already has these repeating templates unrolled so that every possible version is included. In general, there is a limited number of versions (fewer than 25) for each of these repeating closed templates. Open templates Some templates allow for the reporting of as many sets of information as are pertinent to the institution's business. This type of template is called an open template. There are two types of open templates, those that are open on the Y axis, and those that are open on the Z axis. The Y axis open templates are used where there is an unknown number of rows of information to be reported. Each row typically has one or more key values that are dimensionalized using typed dimensions. Thus, typically, the data that these templates represent are to be obtained from a (relational) database query (the data source can also be an OLAP or Excel database). In the July 2014 version of the templates, the following list contains Y axis open templates: C 06.02, C 08.02, C 10.02, C 14.00, C 27.00, C 28.00, C 29.00, C 30.00, C 31.00, F 40.01, and F Templates provided by IBM The following tables contain the templates that are provided by IBM from the EBA Framework Release of 07/2014 (applicable as of December 2014). Table 1. COREP templates Template C C Description Nature of Report (COREP) Capital Adequacy - Own funds definition Copyright IBM Corp

18 Table 1. COREP templates (continued) C Capital Adequacy - Risk Exposure Amounts C Capital Adequacy - Ratios C Capital Adequacy - Memorandum Items C Capital Adequacy - Transitional provisions: Summary C Capital Adequacy - Transitional provisions: Grandfathered instruments constituting State aid C Group Solvency -Total C Group Solvency C a Credit and counterparty credit risks and free deliveries: Standardised Approach to capital requirements C b Credit and counterparty credit risks and free deliveries: Standardised Approach to capital requirements - Of which: Arising from Counterparty Credit Risk C c Credit and counterparty credit risks and free deliveries: Standardised Approach to capital requirements - Memorandum items - Secured on Property C d Credit and counterparty credit risks and free deliveries: Standardised Approach to capital requirements - Memorandum items - in default C a Credit and counterparty credit risks and free deliveries: IRB Approach to capital requirements - TOTAL C b Credit and counterparty credit risks and free deliveries: IRB Approach to capital requirements - TOTAL - Of which arising from counterparty credit risk and off balance sheet C c Credit and counterparty credit risks and free deliveries: IRB Approach to capital requirements - TOTAL (SMEs subject to supporting factor) C d Credit and counterparty credit risks and free deliveries: IRB Approach to capital requirements - TOTAL - Of which arising from counterparty credit risk and off balance sheet (SMEs subject to supporting factor) C Credit and counterparty credit risks and free deliveries: IRB Approach to capital requirements - Breakdown of exposures assigned to obligor grades or pools by obligor grades C a Geographical breakdown of exposures by residence of the obligor (SA exposures) C b Geographical breakdown of exposures by residence of the obligor (SA exposures) - Exposures in default C Geographical breakdown of exposures by residence of the obligor (IRB exposures) C Breakdown of total own funds requirements for credit risk of relevant credit exposures by country C Credit risk: Equity - IRB approaches to capital requirements - TOTAL C Credit risk: Equity - IRB approaches to capital requirements - Breakdown of total exposures under the PD/LGD Approach by obligor grades C Settlement/Delivery risk 12 IBM Cognos Disclosure Management Version : COREP FINREP Technical Notes

19 Table 1. COREP templates (continued) C Credit risk: Securitisations - Standardised Approach to own funds requirements C Credit risk: Securitisations - IRB Approach to own funds requirements C Detailed information on securitisations C Exposures and losses from lending collateralised immovable property C a Operational risk - Excluding AMA C b Operational risk - AMA C a Operational risks: Gross losses by business lines and event types in the last year C b Operational risks: Thresholds applied in data collections C Market risk: Standardised Approach for traded debt instruments C Market risk: Standardised Approach for specific risk in securitisations C Market risk: Standardised Approach for specific risk in the correlation trading portfolio C Market risk: Standardised Approach for position risk in equities C Market risk: Standardised Approaches for foreign exchange risk C Market risk: Standardised Approach for position risk in commodities C Market risk: Internal models - Total C CVA RISK C Large exposures limits C Identification of the counterparty C Exposures in the non-trading and trading book C Detail of the exposures to individual clients within groups of connected clients C Maturity buckets of the 10 largest exposures to institutions and the 10 largest exposures to unregulated financial entities C Maturity buckets of the 10 largest exposures to institutions and the 10 largest exposures to unregulated financial entities: detail of the exposures to individual clients within groups of connected clients C Alternative treatment of the Exposure Measure C On- and off-balance sheet items additional breakdown of exposures C Alternative definition of capital C a Breakdown of leverage ratio exposure measure components: Off-balance sheet items, derivatives, SFTs, and trading book C b Breakdown of leverage ratio exposure measure components: Other non-trading book exposures (SA) C c Breakdown of leverage ratio exposure measure components: Other non-trading book exposures (IRB) Chapter 5. Filing packages 13

20 Table 1. COREP templates (continued) C General information C a Leverage ratio calculation C b Leverage ratio calculation - average C a Entities that are consolidated for accounting purposes but are not within the prudential scope of consolidation (I) C b Entities that are consolidated for accounting purposes but are not within the prudential scope of consolidation (II) C c Entities that are consolidated for accounting purposes but are not within the prudential scope of consolidation (III) C a Liquidity Coverage. Liquid assets (I). Total C b Liquidity Coverage. Liquid assets (II). Total C w Liquidity Coverage. Liquid assets (I). Significant currencies C x Liquidity Coverage. Liquid assets (II). Significant currencies C a Liquidity Coverage. Outflows (I). Total C b Liquidity Coverage. Outflows (II). Total C c Liquidity Coverage. Outflows (III). Total C d Liquidity Coverage. Outflows (IV). Total C w Liquidity Coverage. Outflows (I). Significant currencies C x Liquidity Coverage. Outflows (II). Significant currencies C y Liquidity Coverage. Outflows (III). Significant currencies C z Liquidity Coverage. Outflows (IV). Significant currencies C a Liquidity Coverage. Inflows (I). Total C b Liquidity Coverage. Inflows (II). Total C c Liquidity Coverage. Inflows (III). Total C w Liquidity Coverage. Inflows (I). Significant currencies C x Liquidity Coverage. Inflows (II). Significant currencies C y Liquidity Coverage. Inflows (III). Significant currencies C a Liquidity Coverage. Collateral swaps. Total C w Liquidity Coverage. Collateral swaps. Significant currencies C a Stable funding. Items requiring stable funding (I). Total C b Stable funding. Items requiring stable funding (II). Total C w Stable funding. Items requiring stable funding (I). Significant currencies C x Stable funding. Items requiring stable funding (II). Significant currencies C a Stable funding. Items providing stable funding (I). Total C b Stable funding. Items providing stable funding (II). Total C w Stable funding. Items providing stable funding (I). Significant currencies C x Stable funding. Items providing stable funding (II). Significant currencies 14 IBM Cognos Disclosure Management Version : COREP FINREP Technical Notes

21 Table 2. FINREP templates Template Description F Nature of Report (FINREP) F Balance Sheet Statement [Statement of Financial Position]: Assets F Balance Sheet Statement [Statement of Financial Position]: Liabilities F Balance Sheet Statement [Statement of Financial Position]: Equity F Statement of profit or loss F Statement of comprehensive income F Breakdown of financial assets by instrument and by counterparty sector: financial assets held for trading F Breakdown of financial assets by instrument and by counterparty sector: financial assets designated at fair value through profit or loss F Breakdown of financial assets by instrument and by counterparty sector: available-for-sale financial assets F Breakdown of financial assets by instrument and by counterparty sector: loans and receivables and held-to-maturity investments F Subordinated financial assets F Breakdown of financial assets by instrument and by counterparty sector: trading financial assets F Breakdown of financial assets by instrument and by counterparty sector: non-trading non-derivative financial assets measured at fair value through profit or loss F Breakdown of financial assets by instrument and by counterparty sector: non-trading non-derivative financial assets measured at fair value to equity F Breakdown of financial assets by instrument and by counterparty sector: non-trading debt instruments measured at a cost-based method F Breakdown of financial assets by instrument and by counterparty sector: other non-trading non-derivative financial assets F Breakdown of loans and advances by product F Breakdown of loans and advances to non-financial corporations by NACE codes F Financial assets subject to impairment that are past due or impaired F a Breakdown of financial liabilities by product and by counterparty (a) F b Breakdown of financial liabilities by product and by counterparty (b) F Subordinated liabilities F Off-balance sheet items subject to credit risk: Loan commitments, financial guarantees, and other commitments given Chapter 5. Filing packages 15

22 Table 2. FINREP templates (continued) F Loan commitments, financial guarantees, and other commitments received F Derivatives: Trading F Derivatives - Hedge accounting: Breakdown by type of risk and type of hedge F Derivatives - Hedge accounting under National GAAP: Breakdown by type of risk F Movements in allowances for credit losses and impairment of equity instruments F Breakdown of loans and advances by collateral and guarantees F Collateral obtained by taking possession during the period (held at the reporting date) F Collateral obtained by taking possession [tangible assets] accumulated F Fair value hierarchy: financial instruments at fair value F a Financial assets pledged as collateral: derecognition and financial liabilities associated with transferred financial assets (a) F b Financial assets pledged as collateral: derecognition and financial liabilities associated with transferred financial assets (b) F a Interest income and expenses by instrument and counterparty (a) F b Interest income and expenses by instrument and counterparty (b) F Realised gains and losses on financial assets and liabilities not measured at fair value through profit or loss by instrument F Gains and losses on financial assets and liabilities held for trading by instrument F Gains and losses on financial assets and liabilities held for trading by risk F Gains and losses on financial assets and liabilities designated at fair value through profit or loss by instrument F Gains and losses from hedge accounting F a Impairment on financial and non-financial assets (a) F b Impairment on financial and non-financial assets (b) F Reconciliation between IFRS and CRR scope of consolidation: Assets F Reconciliation between IFRS and CRR scope of consolidation: Off-balance sheet exposures - loan commitments, financial guarantees, and other commitments given F Reconciliation between IFRS and CRR scope of consolidation: Liabilities F a Information on performing and non-performing exposures (I) 16 IBM Cognos Disclosure Management Version : COREP FINREP Technical Notes

23 Table 2. FINREP templates (continued) F b Information on performing and non-performing exposures (II) F c Information on performing and non-performing exposures (III) F a Information forborn exposures (I) F b Information forborn exposures (II) F c Information forborn exposures (III) F Geographical breakdown of assets by location of the activities F Geographical breakdown of liabilities by location of the activities F Geographical breakdown of main income statement items by location of the activities F Geographical breakdown of assets by residence of the counterparty F a Geographical breakdown of off-balance sheet items subject to credit risk by residence of the counterparty (a) F b Geographical breakdown of off-balance sheet items subject to credit risk by residence of the counterparty (b) F Geographical breakdown of liabilities by residence of the counterparty F Geographical breakdown by residence of the counterparty of loans and advances to non-financial corporations by NACE codes F Tangible and intangible assets: assets subject to operating lease F Fee and commission income and expenses by activity F Assets involved in the services provided F Interests in unconsolidated structured entities F Breakdown of interests in unconsolidated structured entities by nature of the activities F Related parties: amounts payable to and amounts receivable from F Related parties: expenses and income generated by transactions with F Scope of the group: entity-by-entity F Scope of the group: "instrument-by-instrument" F Fair value hierarchy: financial instruments at amortised cost F Use of the Fair Value Option F Hybrid financial instruments not designated at fair value through profit or loss F Tangible and intangible assets: carrying amount F Provisions F Components of net defined benefit plan assets and liabilities F Movements in defined benefit plans and employee benefits F Memo items [related to staff expenses] Chapter 5. Filing packages 17

24 Table 2. FINREP templates (continued) F Gains and losses on financial assets and liabilities designated at fair value through profit or loss by accounting portfolio F Gains and losses on derecognition of non-financial assets other than held for sale F Other operating income and expenses F Statement of changes in equity Table 3. AE templates Template Description A Nature of Report (AE) F Asset encumbrance: Encumbrance overview - Assets F a Asset encumbrance: Encumbrance overview - Collateral (a) F b Asset encumbrance: Encumbrance overview - Collateral (b) F a Asset encumbrance: Not pledged. Own covered bonds and ABS issued and not yet pledged (a) F b Asset encumbrance: Not pledged. Own covered bonds and ABS issued and not yet pledged (b) F a Asset encumbrance: Sources of encumbrance (a) F b Asset encumbrance: Sources of encumbrance (b) F a Asset encumbrance: Maturity data (a) F b Asset encumbrance: Maturity data (b) F a Asset encumbrance: Contingent encumbrance (a) F b Asset encumbrance: Contingent encumbrance (b) F c Asset encumbrance: Contingent encumbrance (c) F a Asset encumbrance: Covered bonds issuance (a) F b Asset encumbrance: Covered bonds issuance (b) F c Asset encumbrance: Covered bonds issuance (c) F d Asset encumbrance: Covered bonds issuance (d) F a Asset encumbrance: Advance template for assets of the reporting institution (a) F b Asset encumbrance: Advance template for assets of the reporting institution (b) F c Asset encumbrance: Advance template for assets of the reporting institution (c) F a Asset encumbrance: Advance template for collateral and own debt securities issued other than covered bonds or ABSs (a) F b Asset encumbrance: Advance template for collateral and own debt securities issued other than covered bonds or ABSs (b) F c Asset encumbrance: Advance template for collateral and own debt securities issued other than covered bonds or ABSs (c) 18 IBM Cognos Disclosure Management Version : COREP FINREP Technical Notes

25 Table 4. FP templates Template P P P P P P P P P P P P P Description Nature of Report (FP) Assets Liabilities Forecast of Liquidity Ratios Insured and uninsured deposits and uninsured deposit-like financial instruments Public sector sources of funding Innovative funding structures Pricing: Loan Assets Pricing: Deposit Liabilities Structural currency mismatches Loan Assets Acquisitions, Run-Offs, and Disposals Plans Deposit Liabilities Acquisition and Disposal Plans Consolidation perimeter Repeating templates Filing indicators Important: The filing packages that are available from IBM apply only for EBA Standard Reporting. If your local regulator made modifications to these templates or requires more disclosures from institutions that file to them, contact your IBM representative to obtain an updated Filing Package. Related concepts: QName tagging and lookup lists on page 21 You can use QNametemType to refer to values of facts, and you can use a lookup list to simplify data entry for those values. Rules for individual disclosures in Implementing Technical Standard on page 5 Many disclosures are required under the Implementing Technical Standard (ITS). You can find instructions for disclosures on the ITS web page. Some templates are repeating templates. In a repeating template, there can be more than one copy of the template, depending on a dimensional item that is on the Z-axis. For example, there might be one copy of a template for each country of residence of a counterparty that is required for COREP reporting. Removing or Adding repeating templates can be done through the Add form wizard from within the report context or from the initial Filing Report setup wizard. Filing Indicators are automatically identified and generated based on the Reference Date, Frequency and Report Content. Any form that is found within the current Report Context will be considered as intended to be reported. Chapter 5. Filing packages 19

26 20 IBM Cognos Disclosure Management Version : COREP FINREP Technical Notes

27 Chapter 6. Additional information Reference dates This chapter contains additional information about COREP and FINREP in IBM Cognos Disclosure Management. A reference date in COREP/FINREP filings means that any instance document has only one time period, which is an instant (not a duration). That date is the reference date. The reference date is the date for which the filing is being produced. QName tagging and lookup lists You can use QNametemType to refer to values of facts, and you can use a lookup list to simplify data entry for those values. For example, to report AFGHANISTAN as the value of a fact, you must provide the value as eba_ga:af, where the member AF has the label AFGHANISTAN in the domain GA. Tip: Create a list of members and corresponding labels and domain (using the Microsoft Excel VLOOKUP function) to simplify data entry for these values. This information was also extracted into an Excel workbook by IBM, which you might find to be a more convenient format. The workbook is available from the same source as the pretagged templates. The DPM as expressed in the Access database file that is provided by the EBA can be used to create such lists. When you run the following query in that database, a table with the necessary information is produced. SELECT Table.OriginalTableCode AS [Template Code], Table.OriginalTableLabel AS [Template Name], Axis.AxisOrientation, AxisOrdinate.OrdinateCode AS [Row or Col Number], AxisOrdinate.OrdinateLabel AS [Row or Col Label], Member.MemberLabel AS [XBRL Concept Name], Member.MemberXbrlCode AS [XBRL Concept QName], Member_1.MemberXbrlCode AS [XBRL Value QName], Member_1.MemberLabel AS [XBRL Value Label] FROM (([Table] INNER JOIN TableVersion ON Table.TableID = TableVersion.TableID) INNER JOIN ((Member INNER JOIN ([Domain] INNER JOIN (DataType INNER JOIN Metric ON DataType.DataTypeID = Metric.DataTypeID) ON Domain.DomainID = Metric.CodeDomainID) ON Member.MemberID = Metric.MetricID) INNER JOIN ((Axis INNER JOIN AxisOrdinate ON Axis.AxisID = AxisOrdinate.AxisID) INNER JOIN OrdinateCategorisation ON AxisOrdinate.OrdinateID = OrdinateCategorisation.OrdinateID) ON Member.MemberID = OrdinateCategorisation.MemberID) ON TableVersion.TableVID = Axis.TableVID) INNER JOIN Member AS Member_1 ON Domain.DomainID = Member_1.DomainID WHERE (((DataType.DataTypeCode)="e")) ORDER BY Table.OriginalTableCode, AxisOrdinate.OrdinateCode, Member_1.MemberXbrlCode; Related concepts: Copyright IBM Corp

28 Further information Chapter 5, Filing packages, on page 11 You can obtain a filing package that enables you to set up the filing report that suits your NSA and EBA requirements. Customers and partners are invited to join a user group that is devoted to sharing experiences in IBM Cognos Disclosure Management. You can find a forum that contains a section that is specifically devoted to these mandates at this location: ( IBMCDMUserGroup) To subscribe, send an to one of the following forum administrators: v Hugh Wallis at hugh.wallis@ca.ibm.com v Ted Potma at tpotma@ca.ibm.com v Debra Pesek at dpesek@us.ibm.com Important: The preceding links and addresses are correct as of the publication date of this document. 22 IBM Cognos Disclosure Management Version : COREP FINREP Technical Notes

29 Notices This information was developed for products and services offered worldwide. This material may be available from IBM in other languages. However, you may be required to own a copy of the product or product version in that language in order to access it. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-ibm product, program, or service. This document may describe products, services, or features that are not included in the Program or license entitlement that you have purchased. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan Ltd , Nihonbashi-Hakozakicho, Chuo-ku Tokyo , Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Copyright IBM Corp

30 Any references in this information to non-ibm Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Software Group Attention: Licensing 3755 Riverside Dr. Ottawa, ON K1V 1B7 Canada Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information is for planning purposes only. The information herein is subject to change before the products described become available. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. 24 IBM Cognos Disclosure Management Version : COREP FINREP Technical Notes

31 If you are viewing this information softcopy, the photographs and color illustrations may not appear. This Software Offering does not use cookies. However, depending upon the configurations deployed, this Software Offering may use other technologies to collect personally identifiable information. These technologies collect each user's v name v user name v password v profile name v personally identifiable information other than name, user name, password, profile name and position for purposes of v session management v authentication v enhanced user usability v single sign-on configuration v usage tracking or functional purposes other than session management, authentication, enhanced user usability and single sign-on configuration These technologies cannot be disabled. If the configurations deployed for this Software Offering provide you as customer the ability to collect personally identifiable information from end users via cookies and other technologies, you should seek your own legal advice about any laws applicable to such data collection, including any requirements for notice and consent. For more information about the use of various technologies, including cookies, for these purposes, see IBM's Privacy Policy at and IBM's Online Privacy Statement at in the section entitled "Cookies, Web Beacons and Other Technologies" and the "IBM Software Products and Software-as-a-Service Privacy Statement" at Trademarks IBM, the IBM logo and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at Copyright and trademark information at Notices 25

32 26 IBM Cognos Disclosure Management Version : COREP FINREP Technical Notes

33 Index E EBA taxonomies 6 R reporting dates 6 roadmap 6 Copyright IBM Corp