Template:M summ 2002 ISDA Affected Party: Difference between revisions

From The Jolly Contrarian
Jump to navigation Jump to search
No edit summary
Tags: Mobile edit Mobile web edit
Replaced content with "{{isda Affected Party summ|isdaprov}}"
Tag: Replaced
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
One who is subject to a Section {{isdaprov|5(b)}} {{isdaprov|Termination Event}}, but not a Section {{isdaprov|5(a)}} {{isdaprov|Event of Default}} — thus one of a marginally less opprobrious character, seeing as {{isdaprov|Termination Event}}s are generally not considered to be one’s ''fault'' as such, but just sad things that happen that no-one expected, or wanted, but bring what was once a beautiful relationship to an end. It’s not you, it’s — well, it’s not me either, it’s just that confounded [[Tax Event Upon Merger - ISDA Provision|tax event that occurred upon your recent merger]].
{{isda Affected Party summ|isdaprov}}
 
Note that, in its wisdom, {{icds}} chose not to have a generic term for the sort of person who is subject to ''either'' a {{isdaprov|Termination Event}} ''or'' an {{isdaprov|Event of Default}}, so there is much “{{isdaprov|Defaulting Party}} [[and/or]] {{isdaprov|Affected Party}}, [[as the case may be]]” sort of malarkey. This depresses we prose stylists, but {{icds}} has ''never'' cared about us, so we should hardly be surprised.
 
And given its relentless quest for infinitesimal particularity — and accepting for a moment it is ''warranted''<ref>~''Grimaces''~ Right. Moment over.</ref> — perhaps {{icds}} has a point, for “{{isdaprov|Affected Party}}” appears in subtly different guises in each of the {{isdaprov|Termination Events}}. Sometimes there is one {{isdaprov|Affected Party}}; sometimes there are two. Where there are two {{isdaprov|Affected Parties}} there is not a “victim” and a “perpetrator” as such, but you are in this odd new millennial world where everyone’s a victim, either party may trigger the {{isdaprov|Termination Event}}, both may estimate replacement prices on termination and they have to split the difference.
 
Where there is one {{isdaprov|Affected Party}}, only the {{isdaprov|Unaffected Party}} can terminate, and it is responsible for obtaining the valuation.

Latest revision as of 18:17, 12 April 2020

The Affected Party is the one who is subject to a Section 5(b) Termination Event, as opposed to the perpetrator of a Section 5(a) Event of Default — thus one of a marginally less opprobrious character, seeing as Termination Events are generally not considered to be one’s fault as such, but just regrettable things that happen that no-one expected, or wanted, but bring what was once a beautiful relationship to an end.

It’s not you, it’s — well, it’s not me either — it’s just that confounded tax event that occurred upon your recent merger.

Note that, in its wisdom, ISDA’s crack drafting squad™ chose not to have a generic term for the sort of person who is subject to either a Termination Event or an Event of Default, so there is much “Defaulting Party and/or Affected Party, as the case may be” sort of malarkey. This depresses we prose stylists, but ISDA’s crack drafting squad™ has never cared about us, so we should hardly be surprised.

Practical differences between “Affected Party” and “Defaulting Party”

What is the practical, economic difference between being closed out on the same Transaction for an Event of Default and a Termination Event?

This is something that all ISDA ninjas know, or sort of intuit, in a sort of semi-conscious, buried-somewhere-deep-in-the-brain-stem kind of way, but they may mutter darkly and try to change the subject if you ask them to articulate it in simple English.

To be fair the topic might be chiefly of academic interest were it not for the unfortunate habit of the same “real world” event potentially comprising more than one variety of termination right. This leads to some laboured prioritisation in the ISDA, and sometimes some in the Schedule too. What if my Tax Event upon Merger is also a Credit Event Upon Merger and, for that matter, also a Force Majeure Event? That kind of question.