Transfer to Avoid Termination Event - 1992 ISDA Provision

From The Jolly Contrarian
Jump to navigation Jump to search
1992 ISDA Master Agreement

A Jolly Contrarian owner’s manual™

6(b)(ii) 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.

6(b)(ii) in all its glory

6(b)(ii) Transfer to Avoid Termination Event. If either an Illegality under Section 5(b)(i)(1) or a Tax Event occurs and there is only one Affected Party, or if a Tax Event Upon Merger occurs and the Burdened Party is the Affected Party, the Affected Party will, as a condition to its right to designate an Early Termination Date under Section 6(b)(iv), use all reasonable efforts (which will not require such party to incur a loss, excluding immaterial, incidental expenses) to transfer within 20 days after it gives notice under Section 6(b)(i) all its rights and obligations under this Agreement in respect of the Affected Transactions to another of its Offices or Affiliates so that such Termination Event ceases to exist.
If the Affected Party is not able to make such a transfer it will give notice to the other party to that effect within such 20 day period, whereupon the other party may effect such a transfer within 30 days after the notice is given under Section 6(b)(i).
Any such transfer by a party under this Section 6(b)(ii) will be subject to and conditional upon the prior written consent of the other party, which consent will not be withheld if such other party’s policies in effect at such time would permit it to enter into transactions with the transferee on the terms proposed.

Related agreements and comparisons

Related Agreements
Click here for the text of Section 6(b)(ii) in the 2002 ISDA
Comparisons
Click to compare this section in the 1992 ISDA and 2002 ISDA.

Resources and Navigation

Resources Wikitext | Nutshell wikitext | 2002 ISDA wikitext | 2002 vs 1992 Showdown | 2006 ISDA Definitions | 2008 ISDA

Navigation Preamble | 1(a) (b) (c) | 2(a) (b) (c) (d) (e) | 3(a) (b) (c) (d) (e) (f) | 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) Tax Event 5(b)(iii) Tax Event Upon Merger 5(b)(iv) Credit Event Upon Merger 5(b)(v) Additional Termination Event (c) | 6(a) (b) (c) (d) (e) | 7 | 8(a) (b) (c) (d) | 9(a) (b) (c) (d) (e) (f) (g) | 10 | 11 | 12(a) (b) | 13(a) (b) (c) (d) | 14 |

Index: Click to expand:

Overview

edit

Note in the 2002 ISDA there is no reference to Illegality (or for that matter Force Majeure, which did not exist under the 1992 ISDA but tends to treated rather like a special case of Illegality and therefore, we think, would have been included in this provision of the 1992 ISDA if it had existed ... if you see what I mean).

When the 2002 ISDA gets on to the topic of Illegality and Force Majeure it allows the Unaffected Party to cherry-pick which Affected Transactions it will terminate, but then seems almost immediately to regret it (see especially in Section 6(b)(iv)). Under the 1992 ISDA if you wanted to pull the trigger on any Termination Event, you had to pull all Affected Transactions. Under the 2002 ISDA it is only binary for the credit- and tax-related Termination Events.

Otherwise, but for one consequential change — 1992’s “excluding” became 2002’s “other than” — I mean, you can just imagine the barney they must have had in the drafting committee for that one, can’t you — the provisions are identical.

Summary

edit

Once the Waiting Period expires, it will be a Termination Event entitling either party to terminate some or all Affected Transactions. Partial termination is permitted because the impact on an event on each Transaction may differ from case to case (eg transactions forming part of a structured finance deal like a repack or a CDO) might not be easily replaced, so the disadvantages of terminating may outweigh the advantages.

As far as branches are concerned this is relatively uncontroversial, especially if yours is a multi-branch ISDA Master Agreement. But there is an interesting philosophical question here, for, without an express pre-existing contractual right to do so, a party may not unilaterally transfer its obligations under a contract to someone else. That, being a novation, requires the other party’s consent. This is deep contractual lore, predating the First Men and even the Children of the Woods. So if the Affected Party identifies an affiliate to whom it can transfer its rights and obligations, the Non-affected Party still may withhold consent. True, it is obliged to provide consent if its policies permit but — well — y’know. Polices? Given the credit department’s proclivities for the fantastical, it’s a fairly safe bet they’ll be able to find something if they don’t feel up to it.

That is to say, this commitment falls some wat short of the JC’s favourite confection: “in good faith and a commercially reasonable manner”.

Note also that if an Non-Affected Party does elect partial termination, the Affected Party has the right to terminate some or all of the remaining Transactions: this prevents Non-Affected Parties being opportunistic. Heaven forfend.

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

Template:M premium 1992 ISDA 6(b)(ii)

edit

See also

edit

Template:M sa 1992 ISDA 6(b)(ii)

References