Affected Transactions - ISDA Provision: Difference between revisions
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) No edit summary |
||
(2 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
{{ | {{nman|isda|2002|Affected Transactions}} |
Latest revision as of 16:55, 14 August 2024
2002 ISDA Master Agreement
A Jolly Contrarian owner’s manual™ Go premium
Crosscheck: Affected Transactions in a Nutshell™
Original text
See ISDA Comparison for a comparison between the 1992 ISDA and the 2002 ISDA.
Resources and Navigation
|
Comparisons
The provisions are identical but for reference to the newly added Force Majeure Termination Event and also a cheeky caveat relating to an Illegality or Force Majeure which affects only the 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 Credit Support Document provides credit support for some, but not, all Transactions.
Basics
Seeing how third party credit support generally works under an ISDA Master Agreement — it only comes into play once Transactions 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?
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👇
|
See also
References
- ↑ The notable exception being a New York law Credit Support Annex of course.