Search for Q&As

Enquirers can use various factors to search for a Q&A:

  • These include searching by the Q&A ID; legal reference, date submitted, technical standard / guideline, or by keyword if known.
  • Searches can be extended to more than one legal act, topic, technical standard or guidelines by making multiple selections (i.e. pressing 'Ctrl' on your keyboard, and selecting the relevant ones from the drop-down lists by left mouse-click).

Disclaimer:

Q&As refer to the provisions in force on the day of their publication. The EBA does not systematically review published Q&As following the amendment of legislative acts. Users of the Q&A tool should therefore check the date of publication of the Q&A and whether the provisions referred to in the answer remain the same.

Please note that the Q&As related to the supervisory benchmarking exercises have been moved to the dedicated handbook page. You can submit Q&As on this topic here.

Final Q&As Q&As under review Rejected Q&As Archived Q&As All Q&As

List of Q&A's

Definition of Special Purpose Vehicle (SPV) as Financial Institution

Are Special Purpose Vehicles (SPV) which are used for of Asset Backed Securities (ABS) transactions "Financial Institutions" according to Art. 4 (27) CRR?If so, shall the Special Purpose Vehicles Reported as the 10 largest exposures on a consolidated basis to unregulated financial entities according to Art. 394 (2) CRR?

  • Legal act: Regulation (EU) No 575/2013 (CRR)
  • COM Delegated or Implementing Acts/RTS/ITS/GLs: Regulation (EU) No 680/2014 - ITS on supervisory reporting of institutions (repealed)
  • ID: 2014_1530
  • Topic: Supervisory reporting - Large Exposures
  • Date of submission:
  • Published as final Q&A: 04/10/2019

Large Exposures Reporting of Volatility Haircut applied to Exposure Value

The instructions for template C 28.00, column 300 and C 29.00, column 310 i.e. “(-) Funded credit protection other than substitution effect”, are currently unclear how volatility haircuts that are applied to the exposure value under CRM are reported.Some vendors have suggested that the CRM volatility haircut applied to the exposure value should be included as a positive value (+), while the volatility haircut applied to the collateral should be included as a negative value (-) within template C 28.00, column 300 and template C 29.00, column 310.This is the only way to satisfy the following validation rules:v0653_m{c330} = {c210} + {c240} + {c250} + {c260} + {c270} + {c280} + {c290} + {c300} + {c310} + {c320}v1683_m{c340} = {c220} + {c250} + {c260} + {c270} + {c280} + {c290} + {c300} + {c310} + {c320} + {c330}The current text used for “(-) Funded credit protection other than substitution effect”, in templates C 28.00 and C 29.00 simply states that "the institution shall report the amounts of funded credit protection, as defined in Article 4(58) of Regulation (EU) No 575/2013, that are deducted from the exposure value due to the application of Article 401 of Regulation (EU) No 575/2013". There is no reference to the volatility haircut applied to the exposure value under CRM. Therefore, can we suggest that the instructions to template C 28.00, column 300 and template C 29.00, column 310 are amended to provide clarification on how the volatility haircut applied to the exposure value under CRM is incorporated into the large exposures templates C 28.00 and C 29.00

  • Legal act: Regulation (EU) No 575/2013 (CRR)
  • COM Delegated or Implementing Acts/RTS/ITS/GLs: Draft ITS on Supervisory Reporting of Institutions
  • ID: 2014_1327
  • Topic: Supervisory reporting - Other
  • Date of submission:
  • Published as final Q&A: 04/10/2019

Clarification on whether a particular business model type constitutes the provision of an account information service as defined by Article 4 (16) of PSD2

Does a business model where the provider offers a service sending the account information to third parties (different from the payment service user)  (detail provided in the background) constitute the provision of an account information service, particularly as it is not proposed that the account information obtained will be given directly to the Payment Service User?

  • Legal act: Directive 2015/2366/EU (PSD2)
  • COM Delegated or Implementing Acts/RTS/ITS/GLs: Not applicable
  • ID: 2018_4098
  • Topic: Authorisation and registration
  • Date of submission:
  • Published as final Q&A: 13/09/2019

Validation rule e4898_n

Is the validation rule e4898_n of ITS consistent with the Article 134(7) of the CRR?

  • Legal act: Regulation (EU) No 575/2013 (CRR)
  • COM Delegated or Implementing Acts/RTS/ITS/GLs: Regulation (EU) No 680/2014 - ITS on supervisory reporting of institutions (repealed)
  • ID: 2017_3548
  • Topic: Supervisory reporting - COREP (incl. IP Losses)
  • Date of submission:
  • Published as final Q&A: 13/09/2019

Originator obligations

What are the obligations of an originator who purchases third party's exposures and subsequently securitises them, in order to meet the requirements set out in Article 9 of the Securitisation Regulation?

  • Legal act: Regulation (EU) No 2017/2402 (SecReg)
  • COM Delegated or Implementing Acts/RTS/ITS/GLs: Not applicable
  • ID: 2018_4368
  • Topic: Provisions applicable to all securitisations
  • Date of submission:
  • Published as final Q&A: 13/09/2019

Reporting of template C71.00 by significant currency

How is template C71.00 (concentration of counterbalancing capacity by counterparty) to be completed in the context of the reporting by significant currency (as referred to in Article 415(2) of Regulation (EU) No 575/2013 (CRR))? Specifically, are exposures in a significant currency going to rise in the ranking when being reported by significant currency (given that items denominated in a different currency will be disregarded in the separate currency reporting)?

  • Legal act: Regulation (EU) No 575/2013 (CRR)
  • COM Delegated or Implementing Acts/RTS/ITS/GLs: Regulation (EU) No 680/2014 - ITS on supervisory reporting of institutions (repealed)
  • ID: 2019_4550
  • Topic: Supervisory reporting - COREP (incl. IP Losses)
  • Date of submission:
  • Published as final Q&A: 06/09/2019

Classification of multilateral development banks (MDBs) for the purpose of the reporting of the Additional Liquidity Monitoring Metrics (ALMM)

For the purpose of the reporting of the ALMM, are MDBs to be considered as financial counterparties, non-financial corporate counterparties or other counterparties?

  • Legal act: Regulation (EU) No 575/2013 (CRR)
  • COM Delegated or Implementing Acts/RTS/ITS/GLs: Regulation (EU) No 680/2014 - ITS on supervisory reporting of institutions (repealed)
  • ID: 2019_4549
  • Topic: Supervisory reporting - Liquidity (LCR, NSFR, AMM)
  • Date of submission:
  • Published as final Q&A: 06/09/2019

Counterparty classification of the ESM and the ESFS

How are ESM and ESFS to be classified for FINREP – as government or as non-financial corporations?

  • Legal act: Regulation (EU) No 575/2013 (CRR)
  • COM Delegated or Implementing Acts/RTS/ITS/GLs: Regulation (EU) No 680/2014 - ITS on supervisory reporting of institutions (repealed)
  • ID: 2018_4282
  • Topic: Supervisory reporting - FINREP (incl. FB&NPE)
  • Date of submission:
  • Published as final Q&A: 06/09/2019

C 66.00, validation rule v5903_s

In an environment of negative (money market indexing) interest rates this rule may not be applicable.

  • Legal act: Regulation (EU) No 575/2013 (CRR)
  • COM Delegated or Implementing Acts/RTS/ITS/GLs: Regulation (EU) No 680/2014 - ITS on supervisory reporting of institutions (repealed)
  • ID: 2018_4193
  • Topic: Supervisory reporting - COREP (incl. IP Losses)
  • Date of submission:
  • Published as final Q&A: 06/09/2019

Conditions for the filling of template C 33.00

If a bank will move to IFRS9 accounting standards starting from 1 July 2018, the first date for the Corep reporting under IFRS9 will be 30 September 2018. Therefore, at 30 June 2018 the new logic of the IFRS9 accounting portfolios is not available in data systems and it would be difficult to complete the new model C 33.00. We would like to know if the bank still need to fill in the template C 33.00 at 30 June 2018 and, if so, what logic it has to use.

  • Legal act: Regulation (EU) No 575/2013 (CRR)
  • COM Delegated or Implementing Acts/RTS/ITS/GLs: Regulation (EU) No 680/2014 - ITS on supervisory reporting of institutions (repealed)
  • ID: 2018_4072
  • Topic: Supervisory reporting - COREP (incl. IP Losses)
  • Date of submission:
  • Published as final Q&A: 06/09/2019

Double counting of intra-group funding in C68.00

"In C68.00 Unsecured wholesale funding (row 110) should be split per product type: - of which loans and deposits from financial customers (row 120) - of which loans and deposits from non-financial customers (row 130) - of which loans and deposits from intra-group entities (row 140) Should intragroup funding be reported exclusively in row 140? Or should it be reported in row 140 AND in row 120/130 depending if the intragroup entity is a financial or a non-financial customer? The same question applies to the split of wholesale funding."

  • Legal act: Regulation (EU) No 575/2013 (CRR)
  • COM Delegated or Implementing Acts/RTS/ITS/GLs: Regulation (EU) No 680/2014 - ITS on supervisory reporting of institutions (repealed)
  • ID: 2018_3962
  • Topic: Supervisory reporting - Liquidity (LCR, NSFR, AMM)
  • Date of submission:
  • Published as final Q&A: 06/09/2019

Incorrect validation rule v4456_m

The validation rule v4456_m is not correctly defined in the taxonomy 2.7. Prerequisites are following: C 47.00 and C 43.00.a and C 43.00.b and C 43.00.c It means that all tables have to be reported. However a bank with a standardised approach to credit risk do not report table C 43.00.c. Consequently the rule can not be applied. In theory a bank can have no data for the table C 43.00.a as well.

  • Legal act: Regulation (EU) No 575/2013 (CRR)
  • COM Delegated or Implementing Acts/RTS/ITS/GLs: Regulation (EU) No 680/2014 - ITS on supervisory reporting of institutions (repealed)
  • ID: 2018_3950
  • Topic: Supervisory reporting - COREP (incl. IP Losses)
  • Date of submission:
  • Published as final Q&A: 06/09/2019

Is the scope of the RTS on strong customer authentication (SCA) and secure communication one-leg or two-leg?

Does the PSD2 requirement on SCA, and subsequently the detailed requirements in the RTS on SCA including the practical usage of the allowed exemptions, apply also to one-leg transactions, with regards to:Transactions with the payer’s payment service providers (PSP) outside the EEA (credit transfers as well as card-based payments)?Credit transfers with the payer’s PSP inside the EEA and the payee’s PSP outside the EEA?Card-based payments with the payer’s PSP (the issuer) inside the EEA and the payee’s PSP (the acquirer) outside the EEA, when the non-EEA acquirer do support SCA?Card-based payments with the payer’s PSP (the issuer) inside the EEA and the payee’s PSP (the acquirer) outside the EEA, when the non-EEA acquirer does not support SCA?

  • Legal act: Directive 2015/2366/EU (PSD2)
  • COM Delegated or Implementing Acts/RTS/ITS/GLs: Regulation (EU) 2018/389 - RTS on strong customer authentication and secure communication
  • ID: 2018_4233
  • Topic: Strong customer authentication and common and secure communication (incl. access)
  • Date of submission:
  • Published as final Q&A: 06/09/2019

The Implementation of the electronic communications exclusion in the voiced-based premium rate services market

Considering the organisation of the voiced-based premium rate services market, and considering the interpretations proposed for the electronic communications exclusion (ECE) in the different countries, as far as a payment transaction complies with the conditions imposed by the ECE, does the ECE apply to the whole value chain, and therefore, all the providers of electronic communications networks or services involved in payment transactions covered by the ECE should not have to register as payment institutions or agents for these operations?

  • Legal act: Directive 2015/2366/EU (PSD2)
  • COM Delegated or Implementing Acts/RTS/ITS/GLs: Not applicable
  • ID: 2018_4181
  • Topic: Other topics
  • Date of submission:
  • Published as final Q&A: 06/09/2019

Geographical scope of application of the RTS on strong customer authentication (SCA) and secure communication requirements – ‘Two-leg’ transactions

Is it necessary that issuer, acquirer, cardholder and merchant be all located in the EEA for the RTS on SCA requirements to apply to two-leg transactions?May the issuer use the merchant’s location as a proxy (in lieu of the acquirer’s location)?

  • Legal act: Directive 2015/2366/EU (PSD2)
  • COM Delegated or Implementing Acts/RTS/ITS/GLs: Regulation (EU) 2018/389 - RTS on strong customer authentication and secure communication
  • ID: 2018_4030
  • Topic: Strong customer authentication and common and secure communication (incl. access)
  • Date of submission:
  • Published as final Q&A: 06/09/2019

IFRS 9 Transitional Arrangements - Business Combination

There is a business combination between banks which decided to apply the static and dynamic phase in the arrangements envisaged by Article 473a CRR.1) How should the static phase-in arrangements envisaged by Article 473a CRR apply on the consolidated basis?2) How should the dynamic phase-in arrangements envisaged by Article 473a CRR apply on the consolidated basis?

  • Legal act: Regulation (EU) No 575/2013 (CRR)
  • COM Delegated or Implementing Acts/RTS/ITS/GLs: Not applicable
  • ID: 2018_4391
  • Topic: Accounting and auditing
  • Date of submission:
  • Published as final Q&A: 09/08/2019

What is considered as a dedicated interface

Payment Service Users (PSUs) communicate with an account servicing payment service provider (ASPSP) via Web using HTTP while mobile PSUs and Third Party Providers (TPPs) via REST Application Programming Interfaces (APIs) but in all cases the processing is done by the same back-end server using the same credentials, authorisations and business logic. In the case of mobile and TPP channels, the APIs are similar and are exposed from the same ASPSP’s gateway. Any issue in the back-end server will result in downtime for all channels. Clarification is required whether this solution is considered as a dedicated interface or not.

  • Legal act: Directive 2015/2366/EU (PSD2)
  • COM Delegated or Implementing Acts/RTS/ITS/GLs: Regulation (EU) 2018/389 - RTS on strong customer authentication and secure communication
  • ID: 2019_4681
  • Topic: Strong customer authentication and common and secure communication (incl. access)
  • Date of submission:
  • Published as final Q&A: 09/08/2019

Inclusion of time taken for SCA in the performance KPI

Does the Key Performance Indicator (KPI) for the performance of the dedicated interface include the time taken for conducting Strong Customer Authentication (SCA)? 

  • Legal act: Directive 2015/2366/EU (PSD2)
  • COM Delegated or Implementing Acts/RTS/ITS/GLs: Regulation (EU) 2018/389 - RTS on strong customer authentication and secure communication
  • ID: 2019_4661
  • Topic: Strong customer authentication and common and secure communication (incl. access)
  • Date of submission:
  • Published as final Q&A: 09/08/2019

Contactless transactions - SCA

Does the cumulative count / authorised sum amount apply to any contactless authorisation request, regardless if the request was approved or not?

  • Legal act: Directive 2015/2366/EU (PSD2)
  • COM Delegated or Implementing Acts/RTS/ITS/GLs: Regulation (EU) 2018/389 - RTS on strong customer authentication and secure communication
  • ID: 2018_4230
  • Topic: Strong customer authentication and common and secure communication (incl. access)
  • Date of submission:
  • Published as final Q&A: 09/08/2019

SCA at vending machines without PIN pad

Do transactions at vending machines without PIN pad require Strong Customer Authentication (SCA)?

  • Legal act: Directive 2015/2366/EU (PSD2)
  • COM Delegated or Implementing Acts/RTS/ITS/GLs: Regulation (EU) 2018/389 - RTS on strong customer authentication and secure communication
  • ID: 2018_4057
  • Topic: Strong customer authentication and common and secure communication (incl. access)
  • Date of submission:
  • Published as final Q&A: 09/08/2019