Template:M gen 2002 ISDA 6(b): Difference between revisions

From The Jolly Contrarian
Jump to navigation Jump to search
No edit summary
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 4: Line 4:
{{quote|“Why just in this direction, thither where all the suns of humanity have hitherto ''gone down''? Will it perhaps be said of us one day that we too, ''steering westward, hoped to reach an India'' – but that it was our fate to be wrecked against infinity?”<ref>[[Friedrich Nietzsche]], {{br|Morgenröte}}, 575.</ref>}}
{{quote|“Why just in this direction, thither where all the suns of humanity have hitherto ''gone down''? Will it perhaps be said of us one day that we too, ''steering westward, hoped to reach an India'' – but that it was our fate to be wrecked against infinity?”<ref>[[Friedrich Nietzsche]], {{br|Morgenröte}}, 575.</ref>}}
Let us not be daunted by ''[[hinterstoisser Traverse|der Morderwand]]''!
Let us not be daunted by ''[[hinterstoisser Traverse|der Morderwand]]''!
{{M gen 2002 ISDA 6(b)(i)}}
{{M gen 2002 ISDA 6(b)(ii)}}
{{M gen 2002 ISDA 6(b)(iii)}}
{{M gen 2002 ISDA 6(b)(iv)}}
===Section {{isdaprov|6(b)(iv)}} Right to Terminate ===
{{Isda 6(b)(iv) summ|isdaprov}}

Latest revision as of 16:23, 5 January 2023

You may find yourself staring at this forbidding north wall of text — on of the most fearsome north walls in all derivatives mountaineering — and for a while begin to wonder whether your eyes are burning, or your brains leaking out of your ears. And just wait till you see what a structured finance lawyer will do with it. there are crevices, cracks, ice-covered chimneys, great glazed traverses which have claimed many a valiant eaglet.

But, friends, we are aeronauts of the spirit!

“Why just in this direction, thither where all the suns of humanity have hitherto gone down? Will it perhaps be said of us one day that we too, steering westward, hoped to reach an India – but that it was our fate to be wrecked against infinity?”[1]

Let us not be daunted by der Morderwand!

Section 6(b)(i): Notice

It starts off gently. If you are subject to a Termination Event — remember these are generally extraneous things beyond your control like Tax Events, Illegality, Force Majeure, for which you can’t really be blamed, but which affect your capacity to efficiently perform the agreement, so this is nothing really to be ashamed about, even though it might colour your counterparty’s view of carrying on — you must notify your counterparty.

Section 6(b)(ii): Transfer to Avoid Termination Event

Things start to go a bit wobbly. You sense that ISDA’s crack drafting squad™ has been on the sauce, or marching powder or something, and became attached to the idea of trying to codify the unknowable future. It gets worse before it gets better but here the permutations are about the parties tax status: either the Tax law has changed for one or other party — a Tax Event — or a party has executed some fancy cross-border merger which has somehow changed its tax residence, status, or eligibility of favourable tax treatment: this is a Tax Event Upon Merger. Here, in essence, you have a little window to sort yourself out, if you hadn’t done that before the merger (isn’t that what Tax advisors are for, by the way?).

Tax Event Upon Merger is also apt to create magnificent rounds of three-dimensional ninja combat drafting, because there is an Affected Party, and a Burdened Party, and they are not ~ necessarily ~ the same, and that is even before you worry about what has happened if there is a Credit Event Upon Merger (could be, right? There is a merger... so why not?) and/or a Force Majeure going on at the same time.

In any case: the Affected Party of a simple Tax Event, or the Affected Party of a TEUM who is also the Burdened Party must try doggedly for twenty days to transfer its rights and obligations to an unaffected Office or Affiliate before it is allowed to trigger an Early Termination Date. In any case the innocent, Unaffected Party, has a varnished right to decline the transfer if it can’t trade with the designated transferee.

Section 6(b)(iii) Two Affected Parties

Well, if they are both Affected Parties they can do their best to agree a fix, but this is what all eagle-eyed members of legal squad will recognise as an agreement to agree. Template:M gen 2002 ISDA 6(b)(iv)

Section 6(b)(iv) Right to Terminate

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[2] 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[3], 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.

  1. Friedrich Nietzsche, Morgenröte, 575.
  2. That’s “Tax Event Upon Merger” to the cool kids.
  3. That’s “Credit Event Upon Merger” to the cool kids.