Events of Default - NY CSA Provision

ISDA 1994 New York Law Credit Support Annex A Jolly Contrarian owner’s manual™ Go premium Overview — Summary — Premium — See also — Wikitext Crosscheck: →NY OG →Eng OG →NY VM →EngVM →Eng IM Events of Default 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. Original text: Para 7 Events of Default For purposes of Section 5(a)(iii)(1) of this Agreement, an Event of Default will exist with respect to a party if: 7(a)(i) that party fails (or fails to cause its Custodian) to make, when due, any Transfer of Eligible Collateral, Posted Collateral or the Interest Amount, as applicable, required to be made by it and that failure continues for two Local Business Days after notice of that failure is given to that party; 7(a)(ii) that party fails to comply with any restriction or prohibition specified in this Annex with respect to any of the rights specified in Paragraph 6(c) and that failure continues for five Local Business Days after notice of that failure is given to that party; or 7(a)(iii) that party fails to comply with or perform any agreement or obligation other than those specified in Paragraphs 7(i) and 7(ii) and that failure continues for 30 days after notice of that failure is given to that party. The varieties of ISDA CSA Subject 1994 NY 1995 Eng 2016 VM NY 2016 VM Eng 2018 IM Eng Preamble Pre Pre Pre Pre Pre Interpretation 1 1 1 1 1 Security Interest 2 - 2 - 2 Credit Support Obligations 3 2 3 2 3 Transfers, Calculations and Exchanges - 3 - 3 - Conditions Precedent, Transfer Timing, Calculations and Substitutions 4 - 4 - 4 Dispute Resolution 5 4 5 4 5 Holding and Using Posted Collateral 6 - 6 - 6 Transfer of Title, No Security Interest - 5 - 5 - Events of Default 7 6 7 6 7 Rights and Remedies 8 - 8 - 8 Representations 9 7 9 7 9 Expenses 10 8 10 8 10 Miscellaneous 11 9 11 9 11 Definitions 12 10 12 10 12 Elections and Variables 13 11 13 11 13 Resources and Navigation Index: Click ᐅ to expand: 1994 NY CSA 1995 CSA 2016 VM CSA

Overview

Transatlantic differences

Unlike the English law CSAs, the NY law CSAs, are not “Transactions” under the ISDA Master Agreement but separate Credit Support Documents. This means they need their own Events of Default, with grace periods, and cannot piggy-back off those in the ISDA Master Agreement.

Summary

Grace periods

Those of ISDA credit support arrangements that are standalone Credit Support Documents — the 1994 New York law CSA, 2016 NY Law VM CSA and the 2018 English law IM CSD, but not the 1995 CSA and the 2016 VM CSA — bake in their own two Local Business Day grace period into their own customised Events of Default.

The 1995 CSA and 2016 VM CSA, being Transactions, don’t need to and inherit the grace periods for the Events of Default in the ISDA Master Agreement.

That can, at the limit, create a dissonance for Americans and IM posters, as your CSA grace periods do not automatically track your ISDA ones. Two Local Business Days is an LBD longer than the standard one LBD grace period in the 2002 ISDA, and an LBD shorter than the standard 3 LBD grace period baked into the 1992 ISDA.

Which is nice. This is not a problem for the English law Credit Support Annexes that are Transactions.

Including “comprehensive” Termination Events

Consider expanding of the Default provision to include “Termination Events where all Transactions are Affected Transactions”. This is as per Section 3.2 of the 2001 ISDA Margin Provisions which recommend that Paragraph 6 of the CSA should apply where all Transactions are closed out following an Event of Default or “Specified Condition” — the latter of which is defined to include the Termination Events listed under the ISDA Master Agreement. All Transactions would likely be Affected Transactions should a Credit Event Upon Merger or Additional Termination Event occur.

The default paragraph explains how you value the 2016 VM CSA itself — being a Transaction in its own right, of course — when closing out an ISDA Master Agreement. The basic gist is that you treat the Credit Support Balance as of the Early Termination Date — being the total value of the Credit Support you have ponied up at any time — as an Unpaid Amount, rather than treating is as a contingent return obligation, the present value of which would go into the Close-Out Amount (or Loss, or Market Quotation, if you still labour under an antediluvian 1992 ISDA).

Why do title transfer CSAs reference “Unpaid Amounts”?

A title transfer CSA is technically a Transaction under the ISDA Master Agreement in its own right — that is deep ISDA lore — but it is still a weird Transaction, and the standard “replacement cost” of valuation method doesn’t work brilliantly: rather than having defined payments upfront, each of which can be valued and discounted back to now to reveal a present value, payment obligations under a title transfer CSA depend on the aggregate discounted cashflows of all the other Transactions under the ISDA Master Agreement. So good luck determining, in the abstract, the replacement cost of something like that.

The good news is you don’t have to: the Credit Support Balance isn’t calculated by reference to its own discounted future cashflows: rather, it is just the inverse of the aggregate present value of all the other Transactions under the ISDA Master Agreement. So the “replacement cost” on any day is just the prevailing value of the Credit Support Balance. It’s easier to treat that as an Unpaid Amount (none of this tedious mucking about with replacement costs and so on).

But that means you have to deem the Close-Out Amount (or Market Quotation/Loss, if under a 1992 ISDA) as zero.

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 👇

• JC’s “nutshell” summary of the clause
• Background reading and long-form essays