Interpretation - ISDA Provision

From The Jolly Contrarian
Jump to navigation Jump to search

2002 ISDA Master Agreement
A Jolly Contrarian owner’s manual

Section 1 in a Nutshell
Use at your own risk, campers!

1 Interpretation
1(a) Definitions. Most of the definitions are in Section 14 but some are scattered throughout the Master Agreement.
1(b) Inconsistency. Where they conflict, each Confirmation overrides the Schedule, and the Schedule overides the Master Agreement.
1(c) Single Agreement. When they enter each Transaction the parties are relying on the Master Agreement and all outstanding Confirmations being a single agreement. They would not otherwise enter into any Transaction.
view template

Section 1 in full

1 Interpretation
1(a) Definitions. The terms defined in Section 14 and elsewhere in this Master Agreement will have the meanings therein specified for the purpose of this Master Agreement.
1(b) Inconsistency. In the event of any inconsistency between the provisions of the Schedule and the other provisions of this Master Agreement, the Schedule will prevail. In the event of any inconsistency between the provisions of any Confirmation and this Master Agreement, such Confirmation will prevail for the purpose of the relevant Transaction.
1(c) Single Agreement. All Transactions are entered into in reliance on the fact that this Master Agreement and all Confirmations form a single agreement between the parties (collectively referred to as this “Agreement”), and the parties would not otherwise enter into any Transactions.
view template

Related agreements and comparisons

Related Agreements
Click here for the text of Section 1 in the 1992 ISDA
Comparisons
Click to compare this section in the 1992 ISDA and 2002 ISDA.

Resources and navigation

Resources Wikitext | Nutshell wikitext | 1992 ISDA wikitext | 2002 vs 1992 Showdown | 2006 ISDA Definitions | 2008 ISDA | JC’s ISDA code project
Navigation Preamble | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14
Events of Default: 5(a)(i) Failure to Pay or Deliver5(a)(ii) Breach of Agreement5(a)(iii) Credit Support Default5(a)(iv) Misrepresentation5(a)(v) Default Under Specified Transaction5(a)(vi) Cross Default5(a)(vii) Bankruptcy5(a)(viii) Merger without Assumption
Termination Events: 5(b)(i) Illegality5(b)(ii) Force Majeure Event5(b)(iii) Tax Event5(b)(iv) Tax Event Upon Merger5(b)(v) Credit Event Upon Merger5(b)(vi) Additional Termination Event

Index — Click ᐅ to expand:

Get in touch
Comments? Questions? Suggestions? Requests? Sign up for our newsletter? Questions? We’d love to hear from you.
BREAKING: Get the new weekly newsletter here Old editions here

Content and comparisons

But for some refreshing loosie-goosiness in the 2002 ISDA about where one might otherwise define terms, the text of Section 1 is the same in each version of the ISDA Master Agreement.
Template

Summary

Section 1 is a gentle introduction indeed to the dappled world of the ISDA Master Agreement: much coming from the “goes without saying, but let’s say it anyway” dept of legal wordwrightery — a large department indeed, in the annals of modern legal practice. It starts getting a bit tasty in Section 1(c) with the Single Agreement, but it’s not until the Section 2(a)(iii) flawed asset provision that you’re properly in the ISDA ninja twilight zone.

In a nutshell: DO NOT ADJUST THIS PROVISION. It does no-one any harm. How could it?
Template

General discussion

Section 1(c): the Single Agreement

Most of Section 1 may be theatrical throat-clearing, but section 1(c) is important — by some lights, the main reason one even has an ISDA Master Agreement: it vouchsafes your close-out netting analysis, purporting to inextricably bind together all Transactions under the ISDA Master Agreement as part of a single, concerted, nettable whole. Should (God forbid) your counterparty have imploded, an unthinking administrator might feel the three-year jet fuel swap you traded in July 2012 had nothing really to do with your six-month interest rate swap from February last year and when it comes to considering who owes who what, the two should be treated as separate, unitary transactions. It might think this quite enthusiastically if one of those transactions happens out-of-the-money to you, and the other one in-the-money. This, at any rate, has been the dominant fear of the Basel Committee on Bank Supervision since it hit upon the idea of capital relief for master netting agreements in 1986.

“Why, that’s dashed bad luck, old man! You have to pay me that out-of-the-money exposure[1] and while this dead parrot owes you on the other trade, the end of the creditors’ queue is that one you can see over there in the far distance, should you have a telescope on you.”

You might be inclined to say, “but wait: we should be able to set these off surely! This is all the same stuff, right! Swaps! They all go together! They’re not unitary transactions at all!”

Well, Section 1(c) — the one that says “it is all a single agreement, and we would never have done any of this if we had thought for a moment it might not be, and to prove it we are saying this out loud at the very inception of our derivatives relationship” is your friend in making that argument. There are similar provisions in other agreements, but none is so classic or elegant as the ISDA Master Agreement’s.
Template

For details freaks

Assignment and its effect on netting and set-off

Could a right to assign by way of security upset close-out netting such that one should forbid parties making assignments by way of security of their rights under the ISDA Master Agreement, for fear of undermining your carefully organised netting opinions?

Generally: No.

  • An assignment by way of security is a preferred claim in the assignor’s insolvency over the realised value of certain rights the assignor holds against its counterparty. It is not a direct transfer of those rights to an assignee: the counterparty is still obliged to the assignor, not the assignee, and any claim the assignee would have against the counterparty would only be by way of subrogation of the assignor’s claim, should the assignor have imploded in the meantime or something.
  • Nemo dat quod non habet”:[2] the unaffected counterparty’s rights cannot be improved (or worsened) by assignment and, it being a single agreement, on termination of the agreement the assignee’s claim is to the Termination Amount determined under the ISDA Master Agreement, which involves terminating all Transactions and determining the aggregate mark-to-market and applying close-out netting. No one can give what they do not have.[3]

At the point of close-out, the assignee’s right is to any Termination Amount payable to the Counterparty. Therefore any assignment of rights is logically subject to the netting, as opposed to potentially destructive of it.

But: This is only true insofar as your netting agreement does not actively do something crazy, like disapplying netting of receivables which have been subject to an assignment and dividing these amounts off as “excluded termination amounts not subject to netting”. I know what you are thinking. “But why on God’s green earth would anyone do that?” This is a question you might pose to the FIA’s crack drafting squad™, who confabulated the FIA’s Professional Client Agreement, which does exactly that.

Happily, ISDA’s crack drafting squad™ was never quite so cavalier with the ISDA Master Agreement, though.
Template

See also

Equivalents in other agreements

Template

References

  1. Yes I know: Section 2(a)(iii). We’ll get to that. And in some jurisdictions mandatory insolvency set-off would also spike an administrator’s guns. But for now, let’s say.
  2. “A chap cannot give away what he doesn’t own in the first place.”
  3. Except under New York law — isn’t that right, rehypothecation freaks?