Force Majeure Event - ISDA Provision

From The Jolly Contrarian
Revision as of 16:09, 7 March 2018 by Amwelladmin (talk | contribs)
Jump to navigation Jump to search
ISDA Anatomy™

2002 ISDA

5(b)(ii) Force Majeure Event. After giving effect to any applicable provision, disruption fallback or remedy specified in, or pursuant to, the relevant Confirmation or elsewhere in this Agreement, by reason of force majeure or act of state occurring after a Transaction is entered into, on any day:―
5(b)(ii)(1) the Office through which such party (which will be the Affected Party) makes and receives payments or deliveries with respect to such Transaction is prevented from performing any absolute or contingent obligation to make a payment or delivery in respect of such Transaction, from receiving a payment or delivery in respect of such Transaction or from complying with any other material provision of this Agreement relating to such Transaction (or would be so prevented if such payment, delivery or compliance were required on that day), or it becomes impossible or impracticable for such Office so to perform, receive or comply (or it would be impossible or impracticable for such Office so to perform, receive or comply if such payment, delivery or compliance were required on that day); or
5(b)(ii)(2) such party or any Credit Support Provider of such party (which will be the Affected Party) is prevented from performing any absolute or contingent obligation to make a payment or delivery which such party or Credit Support Provider has under any Credit Support Document relating to such Transaction, from receiving a payment or delivery under such Credit Support Document or from complying with any other material provision of such Credit Support Document (or would be so prevented if such payment, delivery or compliance were required on that day), or it becomes impossible or impracticable for such party or Credit Support Provider so to perform, receive or comply (or it would be impossible or impracticable for such party or Credit Support Provider so to perform, receive or comply if such payment, delivery or compliance were required on that day),
so long as the force majeure or act of state is beyond the control of such Office, such party or such Credit Support Provider, as appropriate, and such Office, party or Credit Support Provider could not, after using all reasonable efforts (which will not require such party or Credit Support Provider to incur a loss, other than immaterial, incidental expenses), overcome such prevention, impossibility or impracticability;

(view template)

Index: Click to expand:Navigation
See ISDA Comparison for a comparison between the 1992 ISDA and the 2002 ISDA.
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: IllegalityFMTax EventTEUMCEUMATE 5 Events of Default: FTPDBreachCSDMisrepDUSTCross DefaultBankruptcyMWA Termination Events: IllegalityTax EventTEUMCEUMATE 5 Events of Default: FTPDBreachCSDMisrepDUSSCross DefaultBankruptcyMWA Termination Events: IllegalityTax EventTEUMCEUM
Early Termination 6 Early Termination: ET right on EODET right on TEEffect of DesignationCalculations; Payment DatePayments on ETSet-off 6 Early Termination: ET right on EODET right on TEEffect of DesignationCalculationsPayments on ETSet-off 6 Early Termination: ET right on EODET right on TEEffect of DesignationCalculationsPayments on ET
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
Tell me more
Sign up for our newsletter — or just get in touch: for ½ a weekly 🍺 you get to consult JC. Ask about it here.
Numbering Discrepancy: Note the numbering discrepancy in Section 5(b) between the 1992 ISDA and 2002 ISDA. This is caused by a new 5(b)(ii) (Force Majeure Event) in the 2002 ISDA before Tax Event, which is thus shunted from Section 5(b)(ii) (in the 1992 ISDA) to Section 5(b)(iii) (in the 2002 ISDA).

Note that, while the 1992 ISDA does not contain the concept of force majeure, there is an ISDA Illegality/Force Majeure Protocol (see here) which can be signed to adopt/incorporate the relevant parts:

Section 5(b)(ii) in the 1992 ISDA

There is no equivalent to the Force Majeure Event in the 1992 ISDA. An Impossibility clause was frequently written into the schedule, which endeavoured to do the same thing. Note a few caveats with regard to Force Majeure Events:

Waiting Period

The Waiting Period for Illegality (Section 5(b)(i)) is three Local Business Days; for a Force Majeure Event (5(b)(ii)) it is 8 Local Business Days.

Incorporating Force Majeure into the 1992 ISDA

One can incorporate Force Majeure into the 1992 ISDA as long as you carry the concept through to its logical conclusion i.e.:

The concept also impacts the basis of Close Out because the 2002 ISDA requires use of true mids for valuation i.e, not the mean of each party's view of the bid/offer where a Force Majeure Event (or Illegality) occurs, which is effectively what you get under the 1992 ISDA with a "Two Affected Parties" option.