Failure to Pay, DUST and Cross Default under the ISDA
For those who think it is useful to understand the interaction between Failure to Pay, DUST and Cross Default. Generally, the risks get bucketed into three:
- That you default ona transaction under this actual ISDA Master Agreement;
- That you default under any analogous transaction with me under a different master trading agreement;
- That you default under a transaction with someone else in the world, the implications of that default being so heinous it should entitle me to terminate the risk I have under my transactions with you.
- FTP covers payment under delivery defaults directly under the ISDA Master Agreement. Obviously straightforward. You don't need any special cross-termination rights here.
- DUST covers default under transactions governed by other master trading agreements (and distinct ISDA Master Agreements — unlikely, but not impossible) between the two of us.
- Cross Default covers defaults under “Specified Indebtedness” (unless you’re odd, that just means normal indebtedness, or borrowed money) between the counterparty and any third party, provided the default is so material (by reference to a Threshold) that it casts doubt on the counterparty’s ongoing viability (and hence its ability to perform its obligations to me uinder the ISDA Master Agreement).
Failure to Pay and DUST are meant to be mutually exclusive by reference to governing agreement (FTP is stuff under this specific ISDA Master Agreement right here, DUST being stuff under any other master trading agreement). DUST and Cross Default are meant to be mutually exclusive by reference to contract type (Specified Transactions under master trading agreements tend not to be “funded” and thus are not, by design, contracts of indebtedness, especially in these times of mandatory collateralisation). This does not stop well-meaning but ignorant risk teams expanding Cross-Default to cover obligations that are not in the nature of indebtedness