Template:M summ 2002 ISDA Defaulting Party

Revision as of 11:15, 7 July 2022 by Amwelladmin (talk | contribs) (Created page with "The key thing to notice here is that — in an uncharacteristically rather neat, understated bit of drafting — Defaulting Party encapsulates a party who has itself defaulted...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

The key thing to notice here is that — in an uncharacteristically rather neat, understated bit of drafting — Defaulting Party encapsulates a party who has itself defaulted, or whose Credit Support Provider or Specified Entity has committed an act which amounts to an Event of Default for that counterparty to this ISDA Master Agreement. I know, I know, this doesn’t seem that big of a deal: this sort of thing that should be plain, obvious and go without saying — but it saves you a job when, in your peregrinations round the party’s Confirmation, you come to talk of pending Events of Default and Termination Events agaisnt that party.

Instead of saying, laboriously, i“f there is an Event of Default or Termination Event with respect to a party or its Credit Support Providers or Specified Entities, as the case may be” you can speak of a Defaulting Party or an Affected Party.

Of course, it would be nice if there was a catch all for a party who has committed an Event of Default or suffered a Termination Event, so you didn’t need to go “Defaulting Party or Affected Party, as the case may be” — cheekily we suggest “Innocent Party” and “Implicated Party” (“Guilty Party”, though fun, isn’t quite right, seeing as Termination Events aren’t meant to impute any kind of culpability).