Events of Default - ISDA Provision: Difference between revisions

From The Jolly Contrarian
Jump to navigation Jump to search
No edit summary
 
(25 intermediate revisions by the same user not shown)
Line 1: Line 1:
==Section 5(a) of the [[2002 ISDA Master]]==
{{nman|isda|2002|5(a)}}
 
{{isdaquote|(a) '''Events of Default'''. The occurrence at any time with respect to a party or, if applicable, any {{isdaprov|Credit Support Provider}}<br>
of such party or any {{isdaprov|Specified Entity}} of such party of any of the following events constitutes (subject to Sections 5(c)<br>
and 6(e)(iv)) an event of default (an “Event of Default”) with respect to such party:―|5(a)|isda}}
 
==Section 5, {{isdama}}==
:(a) {{isdaprov|Events of Default}}
::(i) {{isdaprov|Failure to Pay or Deliver}}
::(ii) {{isdaprov|Breach of Agreement}}
::(iii) {{isdaprov|Credit Support Default}}
::(iv) {{isdaprov|Misrepresentation}}
::(v) {{isdaprov|Default under Specified Transaction}}
::(vi) {{isdaprov|Cross Default}}
::(vii) {{isdaprov|Bankruptcy}}
::(viii) {{isdaprov|Merger without Assumption}}
:(b) {{isdaprov|Termination Events}}
::(i) {{isdaprov|Illegality}}
::(ii) {{isdaprov|Tax Event}}
::(iii) {{isdaprov|Tax Event Upon Merger}}
::(iv) {{isdaprov|Credit Event Upon Merger}}
::(v) {{isdaprov|Additional Termination Event}}
:(c) {{isdaprov|Event of Default and Illegality}}
 
==Additional Events of Default==
Note that additional events of default may be set out in Part 5 of the [[ISDA Schedule]].
 
==Termination Events and Events of Default==
 
{{isdaprov|Termination Events}} and {{isdaprov|Events of Default}} under an {{isdama}} are similar in that when they occur to one party (the {{isdaprov|Affected Party}} or {{isdaprov|Defaulting Party}}) the other may terminate outstanding trades under the agreement. Differences:
*'''Events of Default''': As the word "default" implies EODs are treated as the ''fault'' the defaulting party and may give rise to third-party default rights (where the relevant {{isdaprov|Cross Default}} extends to derivatives and trading documents);
*'''Termination Events''': There is less "moral turpitude" associated with a Termination Event under an {{isdama}}, and they will generally not trigger Cross Defaults (not amounting to "defaults".
 
==Types of Events of Default==
Events of Default can be categorised:
*'''Independently Verifiable''': Some by their nature can independently verified without affirmation from the Counterparty particularly:
**'''Direct Breaches''': direct breaches of the Agreement (eg {{isdaprov|Failure To Pay}}; {{isdaprov|Breach of Agreement}});
**'''Public Actions''': Events which are necessarily public (most of the {{isdaprov|Bankruptcy}} limbs; {{isdaprov|Merger Without Assumption}}
*'''Not independently verifiable''': Others require acknowledgement or notice from the counterparty as they may depend on states of affairs which are not public knowledge, are not breaches of a direct obligation to BBPLC and would not otherwise come to the firm's attention: Particularly:
**{{isdaprov|Cross Default}}
**other limbs of {{isdaprov|Bankruptcy}} (eg "has a secured party take possession of all or substantially all its assets".
*'''"Hard" Events of default''': Hard events where some positive action has actually been taken representing a default - such as a {{isdaprov|Failure to Pay}}
*'''"Soft" or "Passive" Events of Default''': where a state of affairs has arisen permitting a Hard Event of Default to come about, but one has not necessarily happened, such as {{isdaprov|Cross Default}}, where the third party owning the actual "Hard" Default right may not have triggered it (and may have no intention of triggering it).
 
That said, and for the same reason, such "not independently verifiable" termination/default events are effectively soft anyway, even where we have such an obligation from counterparty to notify us of their occurrence, because we have no means of policing whether or not the Counterparty has in fact notified us, and therefore no practical remedy anyway if it does not. It is a self certification, after all, and all we can rely on is its moral force and the party's competence to monitor its own position and be sufficiently organised to tell us.
 
Additionally, the obligation on a Counterparty to monitor "passive" Events of Default like Cross Default (as opposed to [[cross acceleration]] where QED a defaulting party will be notified about the occurrence) is a pretty onerous one particularly for a large entity, and even more so where (as they often are for funds) derivatives are included in definition of {{isdaprov|Specified indebtedness}}.
 
Given that cross defaults may have artificially low {{isdaprov|Threshold Amount}}s (as do some of ours) and are set at levels where actual counterparties owning those rights directly are most unlikely to exercise them, it should not be a surprise to find parties resistant to notifying us about these.
 
This becomes a [[GFRM]] call but a practical recommendation would be:
 
#Impose notification requirement only on "active" termination/default events which are non-public and CP has no excuse for not having monitored them and counterparty has actually exercised; and
#If that doesn't work, agree to drop the provision altogether, as in my view its practical utility is limited to "moral" at best (as there is no effective sanction for counterparty breach anyway)
 
{{isdaanatomy}}
*[[Soft Events of Default]]

Latest revision as of 16:25, 14 August 2024

2002 ISDA Master Agreement

A Jolly Contrarian owner’s manual™

5(a) in a Nutshell

The JC’s Nutshell summary of this term has moved uptown to the subscription-only ninja tier. For the cost of ½ a weekly 🍺 you can get it here. Sign up at Substack. You can even ask questions! Ask about it here.

Original text

5(a) Events of Default. The occurrence at any time with respect to a party or, if applicable, any Credit Support Provider of such party or any Specified Entity of such party of any of the following events constitutes (subject to Sections 5(c) and 6(e)(iv)) an event of default (an “Event of Default”) with respect to such party:

5(a)(i) Failure to Pay or Deliver. Failure by the party to make, when due, any payment under this Agreement or delivery under Section 2(a)(i) or 9(h)(i)(2) or 9(h)(i)(4) required to be made by it if such failure is not remedied on or before the first Local Business Day in the case of any such payment or the first Local Delivery Day in the case of any such delivery after, in each case, notice of such failure is given to the party;
5(a)(ii) Breach of Agreement; Repudiation of Agreement.
(1) Failure by the party to comply with or perform any agreement or obligation (other than an obligation to make any payment under this Agreement or delivery under Section 2(a)(i) or 9(h)(i)(2) or (4) or to give notice of a Termination Event or any agreement or obligation under Section 4(a)(i), 4(a)(iii) or 4(d)) to be complied with or performed by the party in accordance with this Agreement if such failure is not remedied within 30 days after notice of such failure is given to the party; or
(2) the party disaffirms, disclaims, repudiates or rejects, in whole or in part, or challenges the validity of, this Master Agreement, any Confirmation executed and delivered by that party or any Transaction evidenced by such a Confirmation (or such action is taken by any person or entity appointed or empowered to operate it or act on its behalf);
5(a)(iii) Credit Support Default.
(1) Failure by the party or any Credit Support Provider of such party to comply with or perform any agreement or obligation to be complied with or performed by it in accordance with any Credit Support Document if such failure is continuing after any applicable grace period has elapsed;
(2) the expiration or termination of such Credit Support Document or the failing or ceasing of such Credit Support Document, or any security interest granted by such party or such Credit Support Provider to the other party pursuant to any such Credit Support Document, to be in full force and effect for the purpose of this Agreement (in each case other than in accordance with its terms) prior to the satisfaction of all obligations of such party under each Transaction to which such Credit Support Document relates without the written consent of the other party; or
(3) the party or such Credit Support Provider disaffirms, disclaims, repudiates or rejects, in whole or in part, or challenges the validity of, such Credit Support Document (or such action is taken by any person or entity appointed or empowered to operate it or act on its behalf);
5(a)(iv) Misrepresentation. A representation (other than a representation under Section 3(e) or 3(f)) made or repeated or deemed to have been made or repeated by the party or any Credit Support Provider of such party in this Agreement or any Credit Support Document proves to have been incorrect or misleading in any material respect when made or repeated or deemed to have been made or repeated;
5(a)(v) Default Under Specified Transaction. The party, any Credit Support Provider of such party or any applicable Specified Entity of such party:―
(1) defaults (other than by failing to make a delivery) under a Specified Transaction or any credit support arrangement relating to a Specified Transaction and, after giving effect to any applicable notice requirement or grace period, such default results in a liquidation of, an acceleration of obligations under, or an early termination of, that Specified Transaction;
(2) defaults, after giving effect to any applicable notice requirement or grace period, in making any payment due on the last payment or exchange date of, or any payment on early termination of, a Specified Transaction (or, if there is no applicable notice requirement or grace period, such default continues for at least one Local Business Day);
(3) defaults in making any delivery due under (including any delivery due on the last delivery or exchange date of) a Specified Transaction or any credit support arrangement relating to a Specified Transaction and, after giving effect to any applicable notice requirement or grace period, such default results in a liquidation of, an acceleration of obligations under, or an early termination of, all transactions outstanding under the documentation applicable to that Specified Transaction; or
(4) disaffirms, disclaims, repudiates or rejects, in whole or in part, or challenges the validity of, a Specified Transaction or any credit support arrangement relating to a Specified Transaction that is, in either case, confirmed or evidenced by a document or other confirming evidence executed and delivered by that party, Credit Support Provider or Specified Entity (or such action is taken by any person or entity appointed or empowered to operate it or act on its behalf);
5(a)(vi) Cross-Default. If “Cross-Default” is specified in the Schedule as applying to the party, the occurrence or existence of:―
(1) a default, event of default or other similar condition or event (however described) in respect of such party, any Credit Support Provider of such party or any applicable Specified Entity of such party under one or more agreements or instruments relating to Specified Indebtedness of any of them (individually or collectively) where the aggregate principal amount of such agreements or instruments, either alone or together with the amount, if any, referred to in clause (2) below, is not less than the applicable Threshold Amount (as specified in the Schedule) which has resulted in such Specified Indebtedness becoming, or becoming capable at such time of being declared, due and payable under such agreements or instruments before it would otherwise have been due and payable; or
(2) a default by such party, such Credit Support Provider or such Specified Entity (individually or collectively) in making one or more payments under such agreements or instruments on the due date for payment (after giving effect to any applicable notice requirement or grace period) in an aggregate amount, either alone or together with the amount, if any, referred to in clause (1) above, of not less than the applicable Threshold Amount;
5(a)(vii) Bankruptcy. The party, any Credit Support Provider of such party or any applicable Specified Entity of such party:―
(1) is dissolved (other than pursuant to a consolidation, amalgamation or merger);
(2) becomes insolvent or is unable to pay its debts or fails or admits in writing its inability generally to pay its debts as they become due;
(3) makes a general assignment, arrangement or composition with or for the benefit of its creditors;
(4)
(A) institutes or has instituted against it, by a regulator, supervisor or any similar official with primary insolvency, rehabilitative or regulatory jurisdiction over it in the jurisdiction of its incorporation or organisation or the jurisdiction of its head or home office, a proceeding seeking a judgment of insolvency or bankruptcy or any other relief under any bankruptcy or insolvency law or other similar law affecting creditors’ rights, or a petition is presented for its winding-up or liquidation by it or such regulator, supervisor or similar official, or
(B) has instituted against it a proceeding seeking a judgment of insolvency or bankruptcy or any other relief under any bankruptcy or insolvency law or other similar law affecting creditors’ rights, or a petition is presented for its winding-up or liquidation, and such proceeding or petition is instituted or presented by a person or entity not described in clause (A) above and either
(I) results in a judgment of insolvency or bankruptcy or the entry of an order for relief or the making of an order for its winding-up or liquidation or
(II) is not dismissed, discharged, stayed or restrained in each case within 15 days of the institution or presentation thereof;
(5) has a resolution passed for its winding-up, official management or liquidation (other than pursuant to a consolidation, amalgamation or merger);
(6) seeks or becomes subject to the appointment of an administrator, provisional liquidator, conservator, receiver, trustee, custodian or other similar official for it or for all or substantially all its assets;
(7) has a secured party take possession of all or substantially all its assets or has a distress, execution, attachment, sequestration or other legal process levied, enforced or sued on or against all or substantially all its assets and such secured party maintains possession, or any such process is not dismissed, discharged, stayed or restrained, in each case within 15 days thereafter;
(8) causes or is subject to any event with respect to it which, under the applicable laws of any jurisdiction, has an analogous effect to any of the events specified in clauses (1) to (7) above (inclusive); or
(9) takes any action in furtherance of, or indicating its consent to, approval of, or acquiescence in, any of the foregoing acts; or
5(a)(viii) Merger Without Assumption. The party or any Credit Support Provider of such party consolidates or amalgamates with, or merges with or into, or transfers all or substantially all its assets to, or reorganises, reincorporates or reconstitutes into or as, another entity and, at the time of such consolidation, amalgamation, merger, transfer, reorganisation, reincorporation or reconstitution:―
5(a)(viii)(1) the resulting, surviving or transferee entity fails to assume all the obligations of such party or such Credit Support Provider under this Agreement or any Credit Support Document to which it or its predecessor was a party; or
5(a)(viii)(2) the benefits of any Credit Support Document fail to extend (without the consent of the other party) to the performance by such resulting, surviving or transferee entity of its obligations under this Agreement.
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

Resources and Navigation

Index: Click to expand:

Comparisons

Redlines


Discussion

This is a landing page for all the ISDA’s many and varied Events of Default. Since there are eight of them, and all of them have their own little idiosyncrasies, we have not tried to discuss individual items in great detail on this page, but have given them their own pages. These are here:

5(a) Events of Default
5(a)(i) Failure to Pay or Deliver
5(a)(ii) Breach of Agreement
5(a)(iii) Credit Support Default
5(a)(iv) Misrepresentation
5(a)(v) Default Under Specified Transaction
5(a)(vi) Cross Default
5(a)(vii) Bankruptcy
5(a)(viii) Merger without Assumption

Here we will discuss them in the round as it were. As a collective.

Basics

Events of Default can generally be contrasted with Termination Events. They tend to be more focused on the outright creditworthiness of the Defaulting Party: whether it could, even if it wanted to, perform its obligations. Termination Events on the other hand tend to be extraneous factors preventing a party from continuing the contract (Or making the contract uneconomic) even though it has the financial resources to do so.

The broad thrust of the Events of Default is:

  1. Direct failures under the Master Agreement itself: Direct contraventions of the ISDA Master Agreement itself and its Transactions by one of the principals to the contract. Within here we have:
    1. Failure to Pay, which became Failure to Pay or Deliver when the cash-only 1987 ISDA gave way to the broader range of non-cash underlying assets under the 1992 ISDA;
    2. Breach of Agreement: Breach of any obligation other than a payment or delivery obligation
    3. Misrepresentation: Breach of any cross-my-heart-and-hope-to-die sort of precontractual representation made undere the contract
    4. Credit Support Default: Failure to provide collateral under a Credit Support Document. While in ordinary banking world a credit support obligation would generally be provided by someone other than a party to the contract. This is not so on Planet ISDA: (some) CSAs and CSDs are “Credit Support Documents”. So this counts as these are mainly principal obligations of the parties themselves (though of course end users will often be guaranteed).
  2. Direct failures under other Agreements: Direct contraventions by parties to the ISDA Master Agreement of other contractual obligations that are sufficiently serious to make the Non-Defaulting Party freak under the ISDA Master Agreement. Within this bucket we have:

    1. Default under Specified Transaction: The Defaulting Party fails directly to the Non-Defaulting Party to perform under a swap-like transaction, only one that is not documented under the ISDA Master Agreement itself, but under a different master trading agreement;
    2. Cross Default: The Defaulting Party fails directly to the Non-Defaulting Party to perform to someone else altogether under a loan-like Transaction, over a certain Threshold Amount;
  3. Unacceptable credit deterioration: The Defaulting Party or its third-party Credit Support Providers suffers a dramatic non-transactional reversal of fortunes such that the Non-Defaulting Party has credible doubts it will ever see its net in-the-money positions realised, whether or not they are currently in-the-money. Into this bucket goes:

    1. Bankruptcy: The Defaulting Party suffers one of the many different ways a merchant can go titten hoch. There are a lot of them, and they are fraught;
    2. Merger Without Assumption: The Defaulting Party is somehow taken over, reincorporated, reconstituted through a corporate event or otherwise magicked into a spiritual realm in which its earthly debts and obligations are not taken up by whomever the resulting entity is.

Events of Default by nature, speak to fundamental and time-honoured verities of the financial system, so it should not be a great surprise that they have not really changed throughout the three major versions of the ISDA Master Agreement. Honourable mention should also go to the Additional Termination Events that credit department will insist on shoehorning into the schedule in a bid to stay relevant: while these are not Events of Default as such, they tend to have a same credit-related quality to them

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