Affected Transactions - ISDA Provision

2002 ISDA Master Agreement A Jolly Contrarian owner’s manual™ Resources and navigation [[{{{1}}} - 1992 ISDA Provision|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) | 5 • 5(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: 2002 ISDA 1992 ISDA Section Affected Transactions in a Nutshell™ Use at your own risk, campers! “Affected Transactions” means: (a) for an Illegality, Force Majeure Event, Tax Event or TEUM, all Transactions affected by the Termination Event (and if it is an Illegality or Force Majeure Event that affects Credit Support Document covering only some Transactions, those Transactions) and (b) for any other Termination Event, all Transactions. view template Full text of Section Affected Transactions “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. view template 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. Tell me more Sign up for our newsletter — or just get in touch: for ½ a weekly 🍺 you get to consult JC. Ask about it here.

Content and comparisons

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.

Template

Summary

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 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?

Template

General discussion

Template

See also

• Right to Terminate

Template

References

Note that for Additional Termination Events and Credit Event Upon Merger, all Transactions are automatically caught, and if you want to capture just certain Transactions, you'll need to tweak this definition too.

There is a lot more about how pointlessly over-engineered this clause is at the commentary to Section 6(b)(iv), the Right to Terminate.

See also

• Right to Terminate