Hierarchy of Events - ISDA Provision: Difference between revisions

From The Jolly Contrarian
Jump to navigation Jump to search
No edit summary
No edit summary
Line 2: Line 2:
In which the [[JC]] thinks he might have found a ''bona fide'' use for the awful legalism “[[and/or]]”. Crikey.
In which the [[JC]] thinks he might have found a ''bona fide'' use for the awful legalism “[[and/or]]”. Crikey.


What to do if the same thing counts as an {{isdaprov|Illegality}} [[and/or]] a {{isdaprov|Force Majeure Event}} ''and'' an {{isdaprov|Event of Default}} [[and/or]] a {{isdaprov|Termination Event}}.
What to do if the same thing counts as an {{isdaprov|Illegality}} ''[[and/or]]'' a {{isdaprov|Force Majeure Event}} ''[[and]]'' an {{isdaprov|Event of Default}} ''[[and/or]]'' a {{isdaprov|Termination Event}}.


Why do we need this? Remember an {{isdaprov|Event of Default}} is an apocalyptic disaster scenario which blows your whole agreement up with extreme prejudice; a {{isdaprov|Termination Event}} is just “one of those things” which justifies termination, but may relate only to a single transaction: it isn’t something one needs necessarily to hang one’s head about.  
Why do we need this? Remember an {{isdaprov|Event of Default}} is an apocalyptic disaster scenario which blows your whole agreement up with extreme prejudice; a {{isdaprov|Termination Event}} is just “one of those things” which justifies termination, but may relate only to a single transaction: it isn’t something one needs necessarily to hang one’s head about.  

Revision as of 14:49, 3 August 2018

ISDA Anatomy™
incorporating our exclusive ISDA in a Nutshell™


In a Nutshell Section 5(c):

5(c) Hierarchy of Events

5(c)(i) As long as an event counts as an Illegality or a Force Majeure Event, it will not count as an Failure to Pay or Deliver, a non-repudiatory Breach of Agreement or the first limb of Credit Support Default.
5(c)(ii) In any other circumstances, an Illegality or a Force Majeure Event which also counts as an Event of Default or a Termination Event, will count as the relevant Event of Default or Termination Event, and not the Illegality or Force Majeure Event.
5(c)(iii) If a Force Majeure Event also counts as an Illegality, it will be treated as an Illegality and not a Force Majeure Event (unless covered by clause 5(c)(ii) above).

view template

2002 ISDA full text of Section 5(c):

5(c) Hierarchy of Events.

5(c)(i) An event or circumstance that constitutes or gives rise to an Illegality or a Force Majeure Event will not, for so long as that is the case, also constitute or give rise to an Event of Default under Section 5(a)(i), 5(a)(ii)(1) or 5(a)(iii)(1) insofar as such event or circumstance relates to the failure to make any payment or delivery or a failure to comply with any other material provision of this Agreement or a Credit Support Document, as the case may be.
5(c)(ii) Except in circumstances contemplated by clause 5(c)(i) above, if an event or circumstance which would otherwise constitute or give rise to an Illegality or a Force Majeure Event also constitutes an Event of Default or any other Termination Event, it will be treated as an Event of Default or such other Termination Event, as the case may be, and will not constitute or give rise to an Illegality or a Force Majeure Event.
5(c)(iii) If an event or circumstance which would otherwise constitute or give rise to a Force Majeure Event also constitutes an Illegality, it will be treated as an Illegality, except as described in clause 5(c)(ii) above, and not a Force Majeure Event.

view template

Click here for the text of Section 5(c) in the 1992 ISDA


Index: Click to expand:Navigation
The Varieties of ISDA Experience
Subject 2002 (wikitext) 1992 (wikitext) 1987 (wikitext)
Preamble Pre Pre Pre
Interpretation 1 1 1
Obligns/Payment 2 2 2
Representations 3 3 3
Agreements 4 4 4
EODs & Term Events 5

Events of Default
FTPDBreachCSDMisrepDUSTCross DefaultBankruptcyMWA
Termination Events
IllegalityTax EventTEUMCEUMATE

5

Events of Default
FTPDBreachCSDMisrepDUSTCross DefaultBankruptcyMWA
Termination Events
IllegalityTax EventTEUMCEUMATE

5

Events of Default
FTPDBreachCSDMisrepDUSTCross DefaultBankruptcyMWA
Termination Events
IllegalityFMTax EventTEUMCEUMATE

Early Termination 6

Early Termination
ET right on EODET right on TEEffect of DesignationCalculations

6

Early Termination
ET right on EODET right on TEEffect of DesignationCalculationsSet-off

6

Early Termination
ET right on EODET right on TEEffect of DesignationCalculationsSet-off

Transfer 7 7 7
Contractual Currency 8 8 8
Miscellaneous 9 9 9
Offices; Multibranch Parties 10 10 10
Expenses 11 11 11
Notices 12 12 12
Governing Law 13 13 13
Definitions 14 14 14
Schedule Schedule Schedule Schedule
Termination Provisions Part 1 Part 1 Part 1
Tax Representations Part 2 Part 2 Part 2
Documents for Delivery Part 3 Part 3 Part 3
Miscellaneous Part 4 Part 4 Part 4
Other Provisions Part 5 Part 5 Part 5

Comments? Questions? Suggestions? Requests? Insults? We’d love to 📧 hear from you.
Sign up for our newsletter.


In which the JC thinks he might have found a bona fide use for the awful legalism “and/or”. Crikey.

What to do if the same thing counts as an Illegality and/or a Force Majeure Event and an Event of Default and/or a Termination Event.

Why do we need this? Remember an Event of Default is an apocalyptic disaster scenario which blows your whole agreement up with extreme prejudice; a Termination Event is just “one of those things” which justifies termination, but may relate only to a single transaction: it isn’t something one needs necessarily to hang one’s head about.

A Force Majeure Event is something that is so beyong one’s control or expectation that it shouldn't count as an Event of Default or even a Termination Event at all.

An Event of Default has more severe consequences for the counterparty. Well, the whole point about force majeure is that it is meant to give you an excuse not to perform your agreement. and an Illegality is only a Termination Event (one can’t be criticised if they go and change the law on you, can one?), so

See also