Response to consultation on supervisory reporting changes related to CRR2 and Backstop Regulation (Framework 3.0)

Go back

NPL backstop

NPL backstop
No benefits are expected on that matter taking into consideration high challenges to report both this information in the two sets of reporting COREP and FINREP in a different way. As NPL backstop is prudential focused, this requirement should be left in the COREP framework and it should be removed from FINREP as the breakdown by exposure classes and instruments does not bring any highlights for the supervisors to have an accurate monitoring.
They are
No discrepancies are identified.
Agree but the inclusion into FINREP framework is not relevant as above mentioned.

Credit risk

Credit risk
C08.05 and C08.05b: columns 20, 30 and 40 are not appropriate according to a regulatory approach (neither PD nor exposure class). This will not help to benchmark with pairs and not for risk identification. TRIM already fulfills this function. It will be more appropriate.
Internal modeling is based on an approach to risk management. Showing this information according to a regulatory approach can lead to confusion over the reading of the model.
For example, in the context of modeling, insurance is part of banks unlike to the regulatory approach. Sometimes the perimeters is different between regulatory approach and risk management approach (i.e.: large corporation).
the costs of development will be burdensome and not representative of risk management.
The regulatory exposure classes are not representative of how the risks are monitored by the banks.
Finally, the EBA’s review of the IRB approach (IRB repair) coincides with the global reforms reflected in the final Basel III framework. It will be appropriate to wait the new framework (CRR3) to design new reporting.

C08.07: Credit and counterparty credit risks and free deliveries: IRB approach to capital requirements: scope of use of IRB and SA approaches (CR IRB 7) : We question the relevance of this new template as the information is already computed through C07 and C08.
C09.01: Methodologies to computed Additional Valuation Adjustment as described in the regulation EU 2016/101 prescribe the rule of computation to be performed on the basis of Valuation Exposure (§6) which are based on financial instruments or portfolio of financial instruments.
For those purposes, financial instruments may be combined to portfolio when, for market price uncertainty and close out cost AVA, the instruments are valued on the basis of the same risk factor or when for model risk AVAs they are valued on the basis of the same pricing model.
Reporting in the C09.01 is only related to financial instruments, and the AVA hold in funds reduction cannot be split using this granularity since the computation is performed accordingly to the article 6 of the regulation.
Furthermore, the scope of the template C09.01 is Credit Risk and Counterparty Risk made of both receivable in Amortized Cost or in Fair Value. This scope is not compatible and comparable to the scope of the regulation EU 2016/101 which define the scope of the core approach in article 8.1: For fair-valued assets and liabilities for which a change in accounting valuation has a partial or zero impact on CET1 capital, AVAs shall only be calculated based on the proportion of the accounting valuation change that impacts CET1 capital.
The COREP Templates 32.01/32.02/32.03/32.04 have already defined precise information on Prudent Valuation reporting, which respect the way the prudent value is computed, by type of AVA (Close-out Cost, Market Price Uncertainty etc…) and even requiring the largest Valuation Exposure in the context of Model Risk AVA and Concentrated Position AVA.
We encourage EBA to remove C09.01.
They are.
Please refer to question 9.
They do but some overlapping is raised (please refer to question 9).

Counterparty credit risk

Counterparty credit risk
The relevance of IM/VM reporting is questioned as it is not required so far for Pillar3 purposes nor required by CRR2. Implementation of such requirement is very burdensome.
No comments.
No comments.
It would be.
C34.01 seems to be very complex to implement especially for GSIIB where part of SACCR would not be so much significant. We would encourage EBA to remove this template from the ITS.
They are so far apart from the following clarifications needed: .
• There are discrepancies related to reporting frequencies between C.08.06 and C.0807 COREP Templates and CR6A and CR10 Pillar 3 templates. The formers are on a half-yearly basis whereas the latter are on an annual basis. We would suggest alignment of frequencies between COREP templates and Pillar 3 templates.
Subsidiaries sub consolidated of the Group seem to stick to the whole requirement on COREP templates (especially C08.06 and C34.08) even those related to Pillar3 alignment whereas these entities are not required to provide the whole information through their Pillar 3 as mentioned in article 13 of CRR (respectively CR6 and CCR5 in Pillar 3 framework). We would encourage EBA to align the COREP Templates submission for these sub-consolidated entities with Pillar 3 requirements.
Refer to answer to question 17.

Leverage ratio

Leverage ratio
Please refer to questions 19.1 & 19.2.
Structures presented are complete.
They do
Most susceptible: Securities Finance Transactions;
We agree with the BCBS conclusions (d468 Revisions to leverage ratio disclosure requirements – June 2019) that only SFT exposures are susceptible to face temporary reductions in transaction volumes,
However, the reporting of daily exposure is excessive and would lead to disproportionate operational complexity and costs. From our understanding, a calculation for SFTs based on weighted month end average exposure values would provide the same information as an operationally excessive reporting of daily actuals.
In any case, the computation of an average of daily calculations for SFTs should only be done with management data on a best effort basis, as evidenced by UK and US banks Daily Values to be used for the calculation of leverage ratios should not be based on accounting values, but they should be based on management data and on a best effort basis.
Best estimates should be considered as acceptable provided that they are measured consistently (within the quarter and with the accounting-based end of quarter figures) and prudently. As there might be difficulties in valuing the assets, applying the leverage ratio netting rules and even eliminating intra group transactions (for the group consolidated ratio) at the end of each day, the best way is to adopt a pragmatic approach.
It should also be noted that the calculation of leverage exposure for SFTs based on daily values would impose significant one-off and ongoing costs on banks, as internal processes and IT systems would need to be adjusted to the new disclosure requirements.
Lastly, in order to reduce excessive burden LR6.2 (C48.01) should be deleted, as LR6.1 (C48.02) already shows the average result of LR6.2.
Please refer to questions 21.1 & 21.2
We would prefer to report both RWEA and LRE figures after potential substitution effects due to credit risk mitigation.
Reporting RWAE without taking into account risk reduction techniques would imply that current outcomes of the IRB and STD tools could no longer be used and that new computation processes would have to be developed leading do increased complexity and costs.
C 47.00 - LEVERAGE RATIO CALCULATION (LRCalc): row 251 IPS exposures exempted in accordance with Article 429a(1)(c) of the CRR: Instructions shall be more explained on IPS exposures.
C 40.00 - ALTERNATIVE TREATMENT OF THE EXPOSURE MEASURE (LR1):
Row 350. Large institutions that are not G-SIIs shall report total of financial assets on an annual frequency whereas they are required to report the same amount on a semi-annual frequency in the template LR1/LSUM. We would suggest alignment of frequencies between COREP templates and Pillar 3 templates.
Paragraph 20 of the instructions on reporting on leverage (Annex XI) refers to “derivatives, SFTs off-balance sheet”, whereas detailed instructions to fulfill the template cells exclude SFTs from off-balance sheet items (Row 095). Accordingly, it should be noted in paragraph 20 “derivatives, SFTs and off-balance sheet”:

C48.01: Daily values for SFTs for the reporting period should be aligned with Pillar 3 on an annual basis.
Agree.

Large Exposures

Large Exposures
They are.
No discrepancies identified
Agree

NSFR

NSFR
We agree on looking at each netting set and calculating the fair value for each of them in its settlement currency. This treatment participates to create consistency in all separate reporting by currency between, on the one hand, derivative liabilities and assets amounts and, on the other hand, margin calls amounts to be reported.
However, with regard to FX derivatives with exchange of notional amounts, this treatment is not sufficient, as it will lead to structural imbalance between ASF and RSF in separate currency reporting as the MtM of foreign exchange derivatives are observed on a net basis.
Indeed, principal amounts exchanged in each currency will be neutralized, which will result in an incomplete overview of the liquidity profile in significant currencies, leading to an ASF and RSF imbalance.
For instance, assets in a given currency (say USD) that are funded by liabilities in another currency (say EUR) hedged by a CCIRS in USD/EUR would generate RSF in the reporting in USD and ASF in the reporting in EUR, and those RSF/ASF would not be compensated by the hedging instrument impact as this impact is circumscribed to the MtM (without taking the notional amounts exchanged into account).
Such imbalance creates a bias in the NSFR reporting in significant currencies.
We thus request to have the possibility to take the notional amounts of FX derivatives with exchange of notional amounts into account in the NSFR in significant currencies otherwise, it will be useful to understand the requested treatment.
No comments
For reporting consistencies, willingness to have the vocabulary aligned with LCR delegated regulation (HQLA indeed is a Basel wording).
No discrepancies have been identified
We do not agree on the 100% RSF applied to the non performing OBS items (whatever the maturity):
• This is not in line with the regulation that refer to the non performing balance sheet exposures (even in Basel III, there is no reference to non performing OBS items)
• It does not make sense when we compare to the RSF applied to the performing OBS items (5%).
We would be grateful if this part would be removed for the updated ITS”.

FINREP

FINREP
Please refer to questions 33.1 & 33.2
Agree
Clear without specific challenges.
Please refer to question 34.1 & 34.2
We see no major challenges.
However, we would appreciate that the EBA clarifies the following point related to the item " Cash balances at central banks and other demand deposits" included in the scope of the template FIN 12 that is currently unclear:
• FIN 12.01. the item « Cash balances at central banks and other demand deposits" is shown in specific rows (Rows 035; 185; 365) and related explanation is given in the ITS instructions.
• FIN 12.02. no specific rows related to the item and no explanation in the ITS instructions.
Consistency check within F18 templates should be amended accordingly as impairments on cash balances at central banks and other demand deposits are currently mapped with exposures instead of impairments.
We see no major challenges, but the relevance of the information required is questioned on that matter.
While the information on direct transfers between Stage 1 and Stage 3 exists in the Datawarehouse, it can be expected that exposures concerned are not material and transfers occur infrequently. Accordingly, collecting direct stage 1-3 transfers would require important changes in technical systems and establishment of new reporting processes creating implementation burden that would outweigh the benefits of the information reported. Indeed, this information would require identifying intermediate changes of impairment stage, what is in contradiction with ITS 2.169 that requests to report information by comparing impairment stage “at the opening of the financial year or initial recognition” and at “the reporting reference date.”
No major challenges but according to IFRS9 the 30 dpd as a backstop to stage2 is refutable, hence the relevance of these amendments is questioned.

Other amendments

Other amendments
Asset encumbrance:
• ABS replaced by securitisations not in all ITS templates (remains in the F36.02) and not in the disclosure templates
• A clear definition of “immovable property” is essential (is it confirmed that it corresponds to RW<= 35%)?
FIN 2 - Row 320 and FIN 20.3 – Row 120 « Gains or (-) losses on derecognition of investments in subsidiaries, joint ventures and associates, net »
• The rows are presented as existing rows but with "amendments in their content / definition" (yellow color code). In our opinion, as these rows do not exist in the current FINREP models (including FINREP 2.9) at least for IFRS models since 2014, they should be considered as new.
• We would appreciate that the EBA clarifies the point and confirms the status of these rows, i.e. new or not applicable for IFRS models.
While we agree, clarification is need on the various codes in template 40.
• The "LEI code" columns have been replaced by a "code" column (column 010) where the LEI code shall be reported or, if not available, the national code of the entity. A "type of code" column (column 015) is added as well as a "National Code" column (column 025) to be completed when the code indicated in column 010 is a LEI code.
• We would appreciate the EBA to confirm that the column "National Code" (column 025) will be 0 if a National Code is filled in the "Code" column (column 10).
We agree.

Upload files

Name of organisation

FEDERATION BANCAIRE FRANCAISE