Template:Isda Affected Transactions comp

Revision as of 17:37, 12 April 2020 by Amwelladmin (talk | contribs) (Created page with "The provisions are identical but for reference to the newly added {{isdaprov|Force Majeure}} {{isdaprov|Termination Event}} and also a cheeky caveat relating to an {{{{{1}}}|I...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

The provisions are identical but for reference to the newly added Force Majeure Termination Event and also a cheeky caveat relating to an {{{{{1}}}|Illegality}} or Force Majeure which affects only the {{{{{1}}}|Credit Support Document}}, and here the “leave no detail, however tiresome, unconsidered” department of ISDA’s crack drafting squad™ caters for the eventuality that your {{{{{1}}}|Credit Support Document}} provides credit support for some, but not, all Transactions.

Seeing how third party credit support generally works under an ISDA Master Agreement — it only comes into play once {{{{{1}}}|Transaction}}s have been closed out, and there are no Transactions left, Affected or otherwise[1] this does seem a rather fussy detail; all the more so now in the age of regulatory variation margin. I mean, who provides credit support for individual Transactions under a master agreement specifically designed to achieve cross-transactional closeout netting?

Hold your letters: I am sure you can think of some reason.

  1. The notable exception being a New York law Credit Support Annex of course.