Affected Transactions - ISDA Provision: Difference between revisions

From The Jolly Contrarian
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
{{manual|MI|2002|Affected Transactions|Section|Affected Transactions|short}}
{{isdamanual|Affected Transactions}}

Revision as of 08:32, 30 May 2023

2002 ISDA Master Agreement

A Jolly Contrarian owner’s manual™

Affected Transactions in a Nutshell

The JC’s Nutshell summary of this term has moved uptown to the subscription-only ninja tier. For the cost of ½ a weekly 🍺 you can get it here. Sign up at Substack. You can even ask questions! Ask about it here.

Affected Transactions in all its glory

Affected Transactions” means (a) with respect to any Termination Event consisting of an Illegality, Force Majeure Event, Tax Event or Tax Event Upon Merger, all Transactions affected by the occurrence of such Termination Event (which, in the case of an Illegality under Section 5(b)(i)(2) or a Force Majeure Event under Section 5(b)(ii)(2), means all Transactions unless the relevant Credit Support Document references only certain Transactions, in which case those Transactions and, if the relevant Credit Support Document constitutes a Confirmation for a Transaction, that Transaction) and (b) with respect to any other Termination Event, all Transactions.

Related agreements and comparisons

Click here for the text of Section Affected Transactions in the 1992 ISDA
Click to compare this section in the 1992 ISDA and 2002 ISDA.

Resources and Navigation

This provision in the 1992

Resources Wikitext | Nutshell wikitext | 1992 ISDA wikitext | 2002 vs 1992 Showdown | 2006 ISDA Definitions | 2008 ISDA | JC’s ISDA code project
Navigation Preamble | 1(a) (b) (c) | 2(a) (b) (c) (d) | 3(a) (b) (c) (d) (e) (f) (g) | 4(a) (b) (c) (d) (e) | 55(a) Events of Default: 5(a)(i) Failure to Pay or Deliver 5(a)(ii) Breach of Agreement 5(a)(iii) Credit Support Default 5(a)(iv) Misrepresentation 5(a)(v) Default Under Specified Transaction 5(a)(vi) Cross Default 5(a)(vii) Bankruptcy 5(a)(viii) Merger Without Assumption 5(b) Termination Events: 5(b)(i) Illegality 5(b)(ii) Force Majeure Event 5(b)(iii) Tax Event 5(b)(iv) Tax Event Upon Merger 5(b)(v) Credit Event Upon Merger 5(b)(vi) Additional Termination Event (c) (d) (e) | 6(a) (b) (c) (d) (e) (f) | 7 | 8(a) (b) (c) (d) | 9(a) (b) (c) (d) (e) (f) (g) (h) | 10 | 11 | 12(a) (b) | 13(a) (b) (c) (d) | 14 |

Index: Click to expand:

Overview

edit

The provisions are identical but for reference to the newly added Force Majeure Termination Event and also a cheeky caveat relating to an Illegality or Force Majeure which affects only the Credit Support Document, and here the “leave no detail, however tiresome, unconsidered” department of ISDA’s crack drafting squad™ caters for the eventuality that your Credit Support Document provides credit support for some, but not, all Transactions.

Summary

edit

Seeing how third party credit support generally works under an ISDA Master Agreement — it only comes into play once Transactions have been closed out, and there are no Transactions left, Affected or otherwise[1] this does seem a rather fussy detail; all the more so now in the age of regulatory variation margin. I mean, who provides credit support for individual Transactions under a master agreement specifically designed to achieve cross-transactional closeout netting?

Premium content

Here the free bit runs out. Subscribers click 👉 here. New readers sign up 👉 here and, for ½ a weekly 🍺 go full ninja about all these juicy topics 👇
  • The JC’s famous Nutshell summary of this clause
  • The limited optionality of an ATE
  • When you might need to terminate only some Transactions under an ATE
edit

See also

edit

References

  1. The notable exception being a New York law Credit Support Annex of course.