Template:M summ 2002 ISDA Specified Transaction: Difference between revisions
Amwelladmin (talk | contribs) Created page with " Used in the {{isdaprov|Default under Specified Transaction}} {{isdaprov|Event of Default}} under Section {{isdaprov|5(a)(v)}} — fondly known to those in the know as “{{is..." |
Amwelladmin (talk | contribs) No edit summary |
||
Line 1: | Line 1: | ||
Used in the {{isdaprov|Default under Specified Transaction}} {{isdaprov|Event of Default}} under Section {{isdaprov|5(a)(v)}} — fondly known to those in the know as “{{isdaprov|DUST}}”. | |||
===Credit support annexes?=== | |||
[[Specified Transaction - 1992 ISDA Provision|We]] are going to go out on a limb here and say that little parenthetical “(including an agreement with respect to any such transaction)” is, if not deliberately ''designed'' that way, is at least ''[[calculated]]''<ref>In the sense of being “likely”.</ref> to capture failures under a [[credit support annex]] which, yes, is a {{isdaprov|Transaction}} under an {{isdama}} but no, is not really a swap or anything really like one. | |||
There is enough chat about {{isdaprov|Credit support Provider}}s (yes, yes, the counterparty itself is of course not a {{isdaprov|Credit support Provider}}) to make us think, on a [[fair, large and liberal]] interpretation, that a default under the [[CSA]] to a swap {{isdaprov|Transaction}} is meant to be covered. | |||
===What?=== | ===What?=== | ||
{{isdaprov|Specified Transaction}}s are those financial markets transactions between you and your counterparty ''other than those under the present {{isdama}}'', default under which justifies the wronged party closing out the present {{isda}}. “Specified Transactions” therefore specifically ''exclude'' {{isdaprov|Transactions}} under the ISDA itself for the sensible reason that a default under those is covered by by {{isdaprov|Failure to Pay or Deliver}} and {{isdaprov|Breach of Obligation}}. It might lead to a perverse result if misadventure under an {{isdama}} {{isdaprov|Transaction}} which did not otherwise amount to an {{isdaprov|Event of Default}}, became one purely as a result of the {{isdaprov|DUST}} provision, however unlikely that may be. | {{isdaprov|Specified Transaction}}s are those financial markets transactions between you and your counterparty ''other than those under the present {{isdama}}'', default under which justifies the wronged party closing out the present {{isda}}. “Specified Transactions” therefore specifically ''exclude'' {{isdaprov|Transactions}} under the ISDA itself for the sensible reason that a default under those is covered by by {{isdaprov|Failure to Pay or Deliver}} and {{isdaprov|Breach of Obligation}}. It might lead to a perverse result if misadventure under an {{isdama}} {{isdaprov|Transaction}} which did not otherwise amount to an {{isdaprov|Event of Default}}, became one purely as a result of the {{isdaprov|DUST}} provision, however unlikely that may be. |
Revision as of 18:25, 8 March 2022
Used in the Default under Specified Transaction Event of Default under Section 5(a)(v) — fondly known to those in the know as “DUST”.
Credit support annexes?
We are going to go out on a limb here and say that little parenthetical “(including an agreement with respect to any such transaction)” is, if not deliberately designed that way, is at least calculated[1] to capture failures under a credit support annex which, yes, is a Transaction under an ISDA Master Agreement but no, is not really a swap or anything really like one.
There is enough chat about Credit support Providers (yes, yes, the counterparty itself is of course not a Credit support Provider) to make us think, on a fair, large and liberal interpretation, that a default under the CSA to a swap Transaction is meant to be covered.
What?
Specified Transactions are those financial markets transactions between you and your counterparty other than those under the present ISDA Master Agreement, default under which justifies the wronged party closing out the present ISDA. “Specified Transactions” therefore specifically exclude Transactions under the ISDA itself for the sensible reason that a default under those is covered by by Failure to Pay or Deliver and Breach of Obligation. It might lead to a perverse result if misadventure under an ISDA Master Agreement Transaction which did not otherwise amount to an Event of Default, became one purely as a result of the DUST provision, however unlikely that may be.
Enter the fiddlers
ISDA’s verbal profligacy won’t stop enthusiastic credit officers amplifying the list even further, of course. What about precious metal transactions? Letter of credit reimbursement obligations? Indebtedness? What indeed?
An odd cognitive dissonance
The framers of DUST deliberately neglected to include borrowed money or indebtedness, because these are picked up under the wider scope of the Cross Default provision which, of course, applies to indebtedness your counterparty owes to anyone, not just you. Still, there is weirdness: Cross Default contemplates a Threshold Amount before it can be triggered. DUST doesn’t. So this leads to an odd gap:
- A (sub Threshold Amount) default under Specified Indebtedness between the two contractual parties would not entitle the innocent party to close out;
- A default under any other Specified Transaction between them would even if a smaller quantum of default. This is kind of counterintuitive. If you were to define DUST to include indebtedness, of course, you'd be covered.
- ↑ In the sense of being “likely”.