Credit Support Document - ISDA Provision: Difference between revisions

From The Jolly Contrarian
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
{{isdaanat|Credit Support Document }}
{{manual|MI|2002|Credit Support Document|Section|Credit Support Document|medium}}
Being the document by which {{isdaprov|Credit Support}} is provided by a {{isdaprov|Credit Support Provider}}.
Being the document by which {{isdaprov|Credit Support}} is provided by a {{isdaprov|Credit Support Provider}}.
===The {{csa}} is ''not'' a Credit Support Document...===
{{credit support annex as a credit support document}}
Note that a {{tag|CSA}}<ref>and its VM update, the {{vmcsa}}.</ref> is '''not''' a {{isdaprov|Credit Support Document}}, and you should not list it as one in {{isdaprov|Part 4}} of the {{isdaprov|Schedule}}, however satisfying it might be to do so. I mean it sounds like one, right? But no: the counterparty cannot be its own {{isdaprov|Credit Support Provider}}. The {{csa}} is, rather, a {{isdaprov|Transaction}} under the {{isdama}}. This is rather important to the whole issue of [[close-out netting]]. Deep [[ISDA lore]].
 
===... But the {{nycsa}} ''is'' a {{isdaprov|Credit Support Document}}===
Because it is a {{sfca}} arrangement and not a {{ttca}}, transfer of credit support under a {{nycsa}}<ref>and its VM update, the {{nyvmcsa}}.</ref> does not change the net liabilities between the parties, the {{nycsa}} (and its regulatory VM successor, the {{nyvmcsa}} is a {{isdaprov|Credit Support Document}} and not a transaction under the {{isdama}}. Fun, huh?


===[[Guarantees]] under the {{isdama}}: why {{isdaprov|Transaction}}-specific {{isdaprov|guarantee}}s don't work===
===[[Guarantees]] under the {{isdama}}: why {{isdaprov|Transaction}}-specific {{isdaprov|guarantee}}s don't work===
{{isdaguaranteewarning}}
{{isdaguaranteewarning}}
{{ref}}
{{ref}}

Revision as of 10:58, 25 February 2020

2002 ISDA Master Agreement
A Jolly Contrarian owner’s manual™

Resources and navigation

[[{{{1}}} - 1992 ISDA Provision|This provision in the 1992]]

Resources Wikitext | Nutshell wikitext | 1992 ISDA wikitext | 2002 vs 1992 Showdown | 2006 ISDA Definitions | 2008 ISDA | JC’s ISDA code project
Navigation Preamble | 1(a) (b) (c) | 2(a) (b) (c) (d) | 3(a) (b) (c) (d) (e) (f) (g) | 4(a) (b) (c) (d) (e) | 55(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 5(b) Termination Events: 5(b)(i) Illegality 5(b)(ii) Force Majeure Event 5(b)(iii) Tax Event 5(b)(iv) Tax Event Upon Merger 5(b)(v) Credit Event Upon Merger 5(b)(vi) Additional Termination Event (c) (d) (e) | 6(a) (b) (c) (d) (e) (f) | 7 | 8(a) (b) (c) (d) | 9(a) (b) (c) (d) (e) (f) (g) (h) | 10 | 11 | 12(a) (b) | 13(a) (b) (c) (d) | 14 |

Index: Click to expand:

Section Credit Support Document in a Nutshell

Use at your own risk, campers!
Credit Support Document” means anything described as such in the Schedule.

Full text of Section Credit Support Document

Credit Support Document” means any agreement or instrument that is specified as such in this Agreement.

Related agreements and comparisons

Click here for the text of Section Credit Support Document in the 1992 ISDA
Click to compare this section in the 1992 ISDA and 2002 ISDA.

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

Content and comparisons

No changes between the versions of this rather unnecessary definition. The men and women of ISDA’s crack drafting squad™ must have stood back and admired the handiwork of their 1992 forebears, high-fived each other and gone, “nice job, dudes and dudettes”.

Template

Summary

Being the document by which Credit Support is provided by a Credit Support Provider.

Template

General discussion

Template:M gen 2002 ISDA Credit Support Document

Template

See also

Template

References

Being the document by which Credit Support is provided by a Credit Support Provider.

The 1995 CSA is not a {{{{{1}}}|Credit Support Document}}...

Among the countless good examples of just how contrived, over-engineered, and fiddly for the sake of being fiddly the ISDA canon is, there is none better than the fact that a New York law Credit Support Annex is a {{{{{1}}}|Credit Support Document}}, while the English law equivalent is not. If that were not silly enough, according to User’s Guide best practice one should not designate the counterparties themselves as {{{{{1}}}|Credit Support Provider}}s to either, though it unclear which portion of the sky would fall in if one did.

A CSA[1] is not a {{{{{1}}}|Credit Support Document}}, and you should not list it as one in {{{{{1}}}|Part 4}} of the {{{{{1}}}|Schedule}}, however satisfying it might be to do so. I mean it sounds like one, right? But no: the counterparty cannot be its own {{{{{1}}}|Credit Support Provider}}. The 1995 CSA is, rather, a {{{{{1}}}|Transaction}} under the ISDA Master Agreement. This is rather important to the whole issue of close-out netting. Deep ISDA lore.

But the 1994 New York law CSA is a {{{{{1}}}|Credit Support Document}}: because it is a security financial collateral arrangement arrangement and not a title transfer collateral arrangement, transfer of credit support under a 1994 New York law CSA[2] does not change the net liabilities between the parties, the 1994 New York law CSA (and its regulatory VM successor, the 2016 NY Law VM CSA is a {{{{{1}}}|Credit Support Document}} and not a transaction under the ISDA Master Agreement. But, because the parties cannot be their own {{{{{1}}}|Credit Support Provider}}s, there are no Credit Support Providers under a New York law CSA. It is like some kind of self-animating poltergeist. Fun, huh?

Guarantees under the ISDA Master Agreement: why Transaction-specific guarantees don't work

Guarantees and the ISDA Master Agreement: why Transaction-specific guarantees don’t work

Should a client request a {{{{{1}}}|transaction}}-specific parental {{{{{1}}}|guarantee}} (or letter of credit) for a {{{{{1}}}|Transaction}} under an ISDA Master Agreement instead of the usual “all obligations” guarantee of all the counterparty’s obligations under the ISDA Master Agreement, hit the alarm button.

You should never agree to the {{{{{1}}}|guarantee}} of individual {{{{{1}}}|Transaction}}s (nor accept a letter of credit with respect to individual {{{{{1}}}|Transactions}}) under an ISDA Master Agreement. If you do, because of the way ISDA Master Agreements are closed out under Section {{{{{1}}}|6(e)}} — or rather, aren’t closed out, you might find that just when you want your guarantee to pay, the {{{{{1}}}|Transaction}} it is guaranteeing isn’t there anymore:

On a close-out, each {{{{{1}}}|Transaction}} is terminated, the individual close-out amounts are determined, they’re aggregated up to a single net sum (i.e. negative exposures are netted off against positive ones) and a single {{{{{1}}}|Close Out Amount}} is payable with respect to all terminated {{{{{1}}}|Transactions}} under {{{{{1}}}|6(e)}} ({{{{{1}}}|Payments on Early Termination}}) of the ISDA Master Agreement.[3]

That is to say, payments following termination of a {{{{{1}}}|Transaction}} are not payable under the {{{{{1}}}|Transaction}} at all - they are payable under the ISDA Master Agreement itself. Therefore, if the guarantee relates to the single {{{{{1}}}|Transaction}}, at the point you wish to rely on it (i.e., upon the party’s default), it will have gone, with no payment required. Vanished, like tears in the rain.

References

  1. and its VM update, the 2016 VM CSA.
  2. and its VM update, the 2016 NY Law VM CSA.
  3. The ISDA Master Agreement itself is never actually terminated, but carries impotently on in undead twilight, roaming the badlands like Nosferatu or the Flying Dutchman, unloved, unredeemed, until the end of days.