These FAQs address the Regulatory Technical Standards (RTS) published in the EU Official Journal in May 2018, which set out the procedures for excluding third-country non-financial counterparties (NFCs) from the Credit Value Adjustment (CVA) capital risk charge under the Capital Requirements Regulation (CRR).
We have divided the FAQs into three sections related to the scope of the RTS, the requirements applicable under the RTS and the potential effects resulting from the current review of the European Market Infrastructure Regulation (EMIR Refit) and Brexit.
The responses to these FAQs involve an assessment of the existing requirements and their implications for firms; but do not constitute exhaustive nor definitive answers.
Disclaimer: This page does not contain legal advice and merely is intended as an information resource to assist market participants in planning and assessing for the identification of non-EU NFCs for the purpose of CVA requirements under CRR. For a legal interpretation of the rules, market participants should take independent counsel advice on the points addressed in these FAQs.
Share This Article:
Share ISDA FAQs on the Procedures for Excluding Non-EU Non-financial Counterparties Under the Capital Requirements Regulationon Facebook. May trigger a new window or tab to open. Share ISDA FAQs on the Procedures for Excluding Non-EU Non-financial Counterparties Under the Capital Requirements Regulationon Twitter. May trigger a new window or tab to open. Share ISDA FAQs on the Procedures for Excluding Non-EU Non-financial Counterparties Under the Capital Requirements Regulationon LinkedIn. May trigger a new window or tab to open. Share ISDA FAQs on the Procedures for Excluding Non-EU Non-financial Counterparties Under the Capital Requirements Regulationvia email. May trigger a new window or your email client to open.Documents (1) for ISDA FAQs on the Procedures for Excluding Non-EU Non-financial Counterparties Under the Capital Requirements Regulation
Related Articles
ISDA Response on DTO and PTRRS
Statement on EMIR 3.0 Implementation Dates
Tags: