Right to Terminate - ISDA Provision: Difference between revisions

From The Jolly Contrarian
Jump to navigation Jump to search
No edit summary
No edit summary
 
(11 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{isdaanat|6(b)(iv)}}
{{nman|isda|2002|6(b)(iv)}}
What a beast. If you track it through in {{tag|nutshell}} terms, it isn’t as bad as it first seems, but you have the derivative lawyer’s gift for over-complication, and the ISDA drafter’s yen for dismal drafting, to thank for this being the trial it is.
 
To make it easier, we’ve invented some concepts: Unaffected Party and Unaffected Transaction - saves you all that mucking around saying the party who is not the Affected Party and so on)
 
Here is how it works.
 
Keep in mind that, unlike {{isdaprov|Events of Default}}, {{isdaprov|Termination Event}}s can arise through no fault of the {{isdaprov|Affected Party}} and are not always apocalyptic in consequence. Depending what they are, they may be cured, worked around, or dented Transactions may be surgically trimmed out, allowing the remainder of the Agreement, and the Unaffected Transactions, to carry on as normal. So here goes:
 
====Divide up the types of {{isdaprov|Termination Event}}====
# Tax ones: If a {{isdaprov|Tax Event}} or a {{isdaprov|TEUM}} ''where the party merging is the one that suffers the tax'', the parties have a month to try to rearrange matters between them, their offices and affiliates to avoid the tax issue. Only once that has failed are you in {{isdaprov|Termination Event}} territory. ''See Section {{isdaprov|6(b)}}(ii) and {{isdaprov|6(b)(iii)}}'''.
# {{isdaprov|Unaffected Party}} ones: If it's a CEUM, an ATE or a TEUM ''where the {{isdaprov|Unaffected Party}} suffers the tax''
# {{isdaprov|Illegality}} and {{isdaprov|Force Majeure}}: Here there may be a {{isdaprov|Waiting Period}} to sit through, to see whether the difficulty clears (For {{isdaprov|Force Majeure Event}} it is eight {{isdaprov|Local Business Day}}s; for {{isdaprov|Illegality}} ''other than one preventing performance of a {{isdaprov|Credit Support Document}}'': three {{isdaprov|Local Business Day}}s; Sit through it.
::Why is there exception for {{isdaprov|Illegality}} on a {{isdaprov|Credit Support Document}}? Because, even though it wasn’t your fault, illegality of a {{isdaprov|Credit Support Document}} profoundly changes your credit assessment (in a way that arguably, even a payment or delivery obligation doesn’t), and that is the most fundamental risk you are managing under the {{isdama}}.

Latest revision as of 16:01, 1 February 2024

2002 ISDA Master Agreement

A Jolly Contrarian owner’s manual™

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

Original text

6(b)(iv) Right to Terminate.
(1) If:―
(A) a transfer under Section 6(b)(ii) or an agreement under Section 6(b)(iii), as the case may be, has not been effected with respect to all Affected Transactions within 30 days after an Affected Party gives notice under Section 6(b)(i); or
(B) a Credit Event Upon Merger or an Additional Termination Event occurs, or a Tax Event Upon Merger occurs and the Burdened Party is not the Affected Party,
the Burdened Party in the case of a Tax Event Upon Merger, any Affected Party in the case of a Tax Event or an Additional Termination Event if there are two Affected Parties, or the Non-affected Party in the case of a Credit Event Upon Merger or an Additional Termination Event if there is only one Affected Party may, if the relevant Termination Event is then continuing, by not more than 20 days notice to the other party, designate a day not earlier than the day such notice is effective as an Early Termination Date in respect of all Affected Transactions.
(2) If at any time an Illegality or a Force Majeure Event has occurred and is then continuing and any applicable Waiting Period has expired:―
(A) Subject to clause (B) below, either party may, by not more than 20 days notice to the other party, designate (I) a day not earlier than the day on which such notice becomes effective as an Early Termination Date in respect of all Affected Transactions or (II) by specifying in that notice the Affected Transactions in respect of which it is designating the relevant day as an Early Termination Date, a day not earlier than two Local Business Days following the day on which such notice becomes effective as an Early Termination Date in respect of less than all Affected Transactions. Upon receipt of a notice designating an Early Termination Date in respect of less than all Affected Transactions, the other party may, by notice to the designating party, if such notice is effective on or before the day so designated, designate that same day as an Early Termination Date in respect of any or all other Affected Transactions.
(B) An Affected Party (if the Illegality or Force Majeure Event relates to performance by such party or any Credit Support Provider of such party of an obligation to make any payment or delivery under, or to compliance with any other material provision of, the relevant Credit Support Document) will only have the right to designate an Early Termination Date under Section 6(b)(iv)(2)(A) as a result of an Illegality under Section 5(b)(i)(2) or a Force Majeure Event under Section 5(b)(ii)(2) following the prior designation by the other party of an Early Termination Date, pursuant to Section 6(b)(iv)(2)(A), in respect of less than all Affected Transactions.
See ISDA Comparison for a comparison between the 1992 ISDA and the 2002 ISDA.
The Varieties of ISDA Experience
Subject 2002 (wikitext) 1992 (wikitext) 1987 (wikitext)
Preamble Pre Pre Pre
Interpretation 1 1 1
Obligns/Payment 2 2 2
Representations 3 3 3
Agreements 4 4 4
EODs & Term Events 5 Events of Default: FTPDBreachCSDMisrepDUSTCross DefaultBankruptcyMWA Termination Events: IllegalityFMTax EventTEUMCEUMATE 5 Events of Default: FTPDBreachCSDMisrepDUSTCross DefaultBankruptcyMWA Termination Events: IllegalityTax EventTEUMCEUMATE 5 Events of Default: FTPDBreachCSDMisrepDUSSCross DefaultBankruptcyMWA Termination Events: IllegalityTax EventTEUMCEUM
Early Termination 6 Early Termination: ET right on EODET right on TEEffect of DesignationCalculations; Payment DatePayments on ETSet-off 6 Early Termination: ET right on EODET right on TEEffect of DesignationCalculationsPayments on ETSet-off 6 Early Termination: ET right on EODET right on TEEffect of DesignationCalculationsPayments on ET
Transfer 7 7 7
Contractual Currency 8 8 8
Miscellaneous 9 9 9
Offices; Multibranch Parties 10 10 10
Expenses 11 11 11
Notices 12 12 12
Governing Law 13 13 13
Definitions 14 14 14
Schedule Schedule Schedule Schedule
Termination Provisions Part 1 Part 1 Part 1
Tax Representations Part 2 Part 2 Part 2
Documents for Delivery Part 3 Part 3 Part 3
Miscellaneous Part 4 Part 4 Part 4
Other Provisions Part 5 Part 5 Part 5

Resources and Navigation

Index: Click to expand:

Comparisons

Template:Isda 6(b)(iv) comp

Basics

What a beast. If you track it through in Nutshell terms, it isn’t as bad as it looks, but you have the ISDA ninja’s gift for over-complication, and ISDA’s crack drafting squad™’s yen for dismal drafting, to thank for this being the trial it is.

To make it easier, we’ve invented some concepts and taken a few liberties:

Unaffected Transaction”, which saves you all that mucking around saying “Transactions other than those that are, or are deemed, to be Affected Transactions” and so on;

Termination Event Notice: An elegant and self-explanatory alternative to “after an Affected Party gives notice under Section 6(b)(i)”.

We take it as logically true that you can’t give 20 days’ notice of something which you then say will happen in fewer than 20 days. Therefore, there is no need for all this “designate a day not earlier than the day such notice is effective” nonsense.

So with that all out the way, here is how it works. Keep in mind that, unlike Events of Default, Termination Events can arise through no fault of the Affected Party and, therefore, are not always as apocalyptic in consequence. Depending what they are, they may be cured or worked-around, and dented Transactions that can’t be panel-beaten back into shape may be surgically excised, allowing the remainder of the ISDA Master Agreement, and all Unaffected Transactions under it, to carry on as normal. So here goes:

Divide up the types of Termination Event

Tax ones: If a Tax Event or a TEUM[1] where the party merging is the one that suffers the tax, the parties have a month to try to rearrange matters between them, their offices and affiliates to avoid the tax issue. Only once that has failed are you in Termination Event territory. See Section 6(b)(ii) and 6(b)(iii).

Non-Affected Party ones: If it’s a CEUM[2], an ATE or a TEUM where the Non-Affected Party suffers the tax, then if the other guy is a Non-Affected Party, then (whether or not you are) you may designate an Early Termination date for the Affected Transactions.

Illegality and Force Majeure: Here, if you are on a 2002 ISDA, there may be a Waiting Period to sit through, to see whether the difficulty clears. For Force Majeure Event it is eight Local Business Days; for Illegality other than one preventing performance of a Credit Support Document: three Local Business Days. So, sit through it. Why is there exception for Illegality on a Credit Support Document? Because, even though it wasn’t your fault, illegality of a Credit Support Document profoundly changes your credit assessment (in a way that arguably, even a payment or delivery obligation doesn’t), and that is the most fundamental risk you are managing under the ISDA Master Agreement.

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👇
  • JC’s “nutshell” summary of the clause
  • Background reading and long-form essays
    • “By not more than 20 business days’ notice”
    • Limited optionality of Termination Events
    • Illegality and Force Majeure
    • How this all works for repackaging SPVs

See also

Template:Isda 6(b)(iv) sa

References

  1. That’s “Tax Event Upon Merger” to the cool kids.
  2. That’s “Credit Event Upon Merger” to the cool kids.