Specified Entity - ISDA Provision: Difference between revisions
Amwelladmin (talk | contribs) |
Amwelladmin (talk | contribs) No edit summary |
||
Line 1: | Line 1: | ||
{{ | {{fullanat|isda|Specified Entity|2002}} | ||
Note the reference in relation to (a) Section {{isdaprov|5(a)}} {{isdaprov|Termination Event}}s (like {{isdaprov|DUST}} for example), and (b) the "{{isdaprov|Absence of Litigation}}" representation in Section ''3(c)'' of the {{2002ma}}. | Note the reference in relation to (a) Section {{isdaprov|5(a)}} {{isdaprov|Termination Event}}s (like {{isdaprov|DUST}} for example), and (b) the "{{isdaprov|Absence of Litigation}}" representation in Section ''3(c)'' of the {{2002ma}}. | ||
Line 10: | Line 8: | ||
===Tricks for young players: nominating {{isdaprov|Specified Entities}} for yourself has its upsides=== | ===Tricks for young players: nominating {{isdaprov|Specified Entities}} for yourself has its upsides=== | ||
{{isdaprov|Specified Entity}} widens the scope of those provisions also to include defaults by {{isdaprov|Specified Entities}} under contracts with ''your'' {{isdaprov|Specified Entities}} - so there *is* some benefit to naming ''your'' affiliates, friends and relations as {{isdaprov|Specified Entities}}. But given how unlikely you are to be actually monitoring how a counterparty performs with an affiliate, it's more of a false comfort than a real one. | {{isdaprov|Specified Entity}} widens the scope of those provisions also to include defaults by {{isdaprov|Specified Entities}} under contracts with ''your'' {{isdaprov|Specified Entities}} - so there *is* some benefit to naming ''your'' affiliates, friends and relations as {{isdaprov|Specified Entities}}. But given how unlikely you are to be actually monitoring how a counterparty performs with an affiliate, it's more of a false comfort than a real one. | ||
{{ | {{seealso}} | ||
*{{isdaprov|Specified Transaction}} | *{{isdaprov|Specified Transaction}} | ||
*{{isdaprov|Cross Default}} | *{{isdaprov|Cross Default}} | ||
*{{isdaprov|Default under Specified Transaction}} | *{{isdaprov|Default under Specified Transaction}} |
Revision as of 17:48, 4 October 2017
Note the reference in relation to (a) Section 5(a) Termination Events (like DUST for example), and (b) the "Absence of Litigation" representation in Section 3(c) of the 2002 ISDA.
A Specified Enity is any affiliate (or, in theory at any rate, even a non-affiliate) of a counterparty to an ISDA Master Agreement which is designated in the relevant Schedule.
It is relevant to the definition of Cross Default and Default under Specified Transaction in that it widens the effect of those provisions to include defaults by the parties specified.
Tricks for young players: nominating Specified Entities for yourself has its upsides
Specified Entity widens the scope of those provisions also to include defaults by Specified Entities under contracts with your Specified Entities - so there *is* some benefit to naming your affiliates, friends and relations as Specified Entities. But given how unlikely you are to be actually monitoring how a counterparty performs with an affiliate, it's more of a false comfort than a real one.