|
|
| (45 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| ==See Also==
| | {{newisdamanual|5(a)(vi)}} |
| *{{t|Cross Default}}
| |
| | |
| {{isdasnap|5(a)(vi)}}
| |
| | |
| ==Cross Default under the {{1992ma}}==
| |
| The text of Section 5(a)(vi) the [[1992 ISDA Master]] is as follows:
| |
| | |
| {{isdaquote|{{ISDA Master Agreement 1992 5(a)(vi)}}|5(a)(vi)|1992}}
| |
| | |
| ==Cross Default under the {{2002ma}}==
| |
| The text of Section 5(a)(vi) the [[2002 ISDA Master]] provides:
| |
| | |
| (vi) ''Cross-Default''. If “Cross-Default” is specified in the Schedule as applying to the party, the occurrence or
| |
| existence of:―
| |
|
| |
| (l) a default, [[event of default]] or other similar condition or event (however described) in respect of such party, any
| |
| {{isdaprov|Credit Support Provider|Credit Support Provider}} of such party or any applicable {{isdaprov|Specified Entity|Specified Entity}} of such party under one or more
| |
| agreements or instruments relating to {{isdaprov|Specified Indebtedness|Specified Indebtedness}} of any of them (individually or collectively) where
| |
| the aggregate principal amount of such agreements or instruments, either alone or together with the amount, if any, referred
| |
| to in clause (2) below, is not less than the applicable {{isdaprov|Threshold Amount|Threshold Amount}} (as specified in the
| |
| Schedule) which has resulted in such Specified Indebtedness becoming, or becoming capable at such time of being declared,
| |
| due and payable under such agreements or instruments before it would otherwise have been due and payable; or
| |
|
| |
| (2) a default by such party, such Credit Support Provider or such Specified Entity (individually or collectively) in making
| |
| one or more payments under such agreements or instruments on the due date for payment (after giving effect to any applicable
| |
| notice requirement or [[grace period]]) in an aggregate amount, either alone or together with the amount, if any, referred to in
| |
| clause (1) above, of not less than the applicable Threshold Amount;
| |
| | |
| | |
| ==Introduction==
| |
| [[Image:Cross Default Diagram.jpg|600px|right|Cross Default (Click to enlarge)]]
| |
| A cross default provision in an agreement allows a [[non-defaulting party]], on a [[default]] by the other party under any separate contract it may have entered for [[borrowed money]], to [[close out]] the agreement containing the cross default provision. Compare this with a [[cross acceleration]] provision, where the lender of the borrowed money must actually have taken steps to accelerate the borrowed money as a result of the default before the default becomes available as a termination right under the first agreement.
| |
| | |
| Cross Default is a potentially very damaging clause, as this picture to the right amply illustrates. To the extent it doesn't:
| |
| | |
| ===Cross Default===
| |
| a cross default provision against a party imports into the [[ISDA]] all of the termination rights upon default under any {{isdaprov|Specified Indebtedness}} owed by that party:
| |
| *It has the effect of dramatically (and indeterminately) widening the definition of Event of Default.
| |
| *Cross default entitles a [[Counterparty]] to [[cross accelerate|accelerate]] the ISDA whether or not the Specified Indebtedness in question itself has been accelerated.
| |
| *Depending on the market value of the transactions under the ISDA at the time of termination, therefore exercise of a cross default may lead to an immediate capital outflow.
| |
| | |
| ===Specified Indebtedness===
| |
| Specified Indebtedness means, generally, any [[borrowed money|borrowings]] that, in aggregate, exceed a designated {{isdaprov|Threshold Amount}}. Because of the aggregation right, even comparatively trivial agreements can trigger the provision where they are relatively homogenous and affected by the same local circumstances (for example, retail deposits). A low Threshold Amount, therefore, presents three challenges:
| |
| *It allows a more varied (and difficult to monitor) range of potential termination rights, because a greater number of agreements will qualify as Specified Indebtedness.
| |
| *It “lowers the bar” so failures to comply with comparatively trivial financial commitments could be aggregated to trigger the Cross Default.
| |
| *By not excluding bank deposits, it raises the possibility of being triggered by localised events unrelated to BBPLC’s credit (for example, political action in a single jurisdiction which affects BBPLC’s ability to pay on its local deposits)
| |
| *Note that [[repo]] is not considered specified indebtedness: see [[borrowed money]].
| |
| | |
| ===Derivatives as Specified Indebtedness===
| |
| {{Upload|Description=Powerpoint on Cross Default to Derivatives|Filename=Cross-Default to Derivatives.pptx}}
| |
| | |
| Derivatives should '''never''' be included in the definition of {{isdaprov|Specified Indebtedness}}, no matter how hight the {{isdaprov|Threshold Amount}}. the Cross Default language aggregates up all individual defaults, so even though a single ISDA would be unlikely to have a net out-of-the-money MTM of anything like 3% of shareholder funds, a large number of them taken together may, particularly if you’re selective about which ones you’re counting. Which the cross default language entitles you to be.
| |
| | |
| Thus, where you have a number of small failures, you can still theoretically have a big problem. This is why we don’t include deposits: operational failure or regulatory action in one jurisdiction can create an immediate problem.
| |
| | |
| The same could well be true for derivatives. Individual net [[MTM]]s under derivative [[ISDA Master Agreement|Master Agreement]]s can be very large. We have a lot of Master Agreements (18000+).
| |
| | |
| Say we have an operational failure (triggering a regulatory announcement, therefore public) or a government action in a given jurisdiction preventing us from making payments on all derivatives in that jurisdiction. We could have technical events of default on a large number of agreements at once – unlikely to be triggered, but for a cross default, that doesn’t matter.
| |
| | |
| The net MTM across all those agreements may well not be significant. But an opportunistic counterparty could tot up all the negative mark to markets, ignore the positive ones, and reach a large number very quickly.
| |
| | |
| Cross Default is a banking concept intended to reference borrowed money - indebtedness etc - and it really doesn’t make economic sense to apply it to derivatives – the fact that there’s a cross default in derivatives documentation at all is something of a historical accident. There are good points made below about the difficulty of calculating it and knowing what to apply it to ([[MTM]]? {{isdaprov|Termination Amount}}? Payments due on any day?) – bear in mind these values are not nearly as deterministic as amounts due wrt borrowed money: on a failure of a derivative contract the valuation of the termination amount (off which {{isdaprov|Cross Default}} would calculate) is extremely contentious. The market is still in dispute with Lehman, for example.
| |
| | |
| ===Credit Mitigation===
| |
| Cross Default is intended to be a tool for mitigating credit exposure. It should be set at a level which reflects a material credit concern in the context of the entire enterprise. By convention, the market generally imposes a Threshold Amount equating to between 2 and 3 percent of shareholders’ funds (as at 2009 annual report, 2% of {{Bank}} Shareholders’ funds would be £1.1bn).
| |
| | |
| ===Credit Support Annex===
| |
| There are other ways of mitigating credit exposure (such as a zero threshold {{csa}}). If a Counterparty's positive [[mark-to-market|exposure]] to {{Bank}} will be fully collateralised on a daily basis, meaning its overall exposure to {{Bank}} at any time will be intra-day movement in the net derivatives positions (a failure to post collateral itself is grounds for immediate termination).
| |
| | |
| ===Contagion risk===
| |
| It is important to maintain minimum standards which are reflective of genuine credit concerns against the bank so as to limit a “snowball” effect: were we to allow a £50mm Threshold Amount, we would potentially be open to a large number of derivative counterparties simultaneously (and opportunistically) closing out out-of-the-money derivatives positions, which in itself could have massive liquidity and capital implications.
| |
| | |
| =={{isdama}}==
| |
| Under the {{isdama}}, if the cross default applies, the occurrence with respect to a party of a payment default under, or other circumstance that could result in the early termination of, {{isdaprov|Specified Indebtedness}} above an agreed {{isdaprov|Threshold}} will give the other party the right to terminate transactions under the ISDA Master.
| |
| | |
| Specified Indebtedness is usually defined to any claim against a party (by any third party) for [[borrowed money]] (e.g. bank debt; [[deposits]] etc.) and the {{isdaprov|Threshold}} which triggers it is usually defined as a cash amount or a percentage of shareholder funds. For BBPLC, see [[Cross default - Treasury policy]], which and note in particular the requirement to carve out deposits in certain circumstances).
| |
| | |
| If the cross default applies, the terms of any Specified Indebtedness owed by the counterparty above the Threshold are, in effect, indirectly incorporated into the {{isdama}}. For example, the breach of a financial covenant in a qualifying loan facility, '''even if not acted upon by the lender of that facility''' would give a swap counterparty the right to terminate transactions under the ISDA Master even though the ISDA Master itself contains no financial covenants.
| |
| ===Cross Aggregation===
| |
| The [[2002 ISDA Master]] amends the [[1992 ISDA Master]] cross-default provision so that if the outstanding amount under the 2 limbs of cross-default added together breach the {{isdaprov|Threshold Amount|Threshold Amount}}, then that will trigger cross default. Normally, under the 1992 ISDA, cross-default is only triggered if an amount under one or the other limbs is breached.
| |
| | |
| As per the above, the two limbs are:
| |
| *a default or similar event under financial agreements or instruments that has resulted in indebtedness becoming capable of being accelerated and terminated by a Non-defaulting Party
| |
| *a failure to make any payments on their due date under such agreements or instruments after notice or the expiry of a grace period.
| |
| | |
| {{isdaanatomy}}
| |
| *{{t|Cross Default}}
| |
|
2002 ISDA Master Agreement
A Jolly Contrarian owner’s manual™
|
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.
| ISDA Text: 5(a)(vi)
- 5(a)(vi) Cross-Default. If “Cross-Default” is specified in the Schedule as applying to the party, the occurrence or existence of:―
- (1) a default, event of default or other similar condition or event (however described) in respect of such party, any Credit Support Provider of such party or any applicable Specified Entity of such party under one or more agreements or instruments relating to Specified Indebtedness of any of them (individually or collectively) where the aggregate principal amount of such agreements or instruments, either alone or together with the amount, if any, referred to in clause (2) below, is not less than the applicable Threshold Amount (as specified in the Schedule) which has resulted in such Specified Indebtedness becoming, or becoming capable at such time of being declared, due and payable under such agreements or instruments before it would otherwise have been due and payable; or
- (2) a default by such party, such Credit Support Provider or such Specified Entity (individually or collectively) in making one or more payments under such agreements or instruments on the due date for payment (after giving effect to any applicable notice requirement or grace period) in an aggregate amount, either alone or together with the amount, if any, referred to in clause (1) above, of not less than the applicable Threshold Amount;
|
Related agreements and comparisons
Resources and Navigation
|
Overview
The 2002 ISDA updates the 1992 ISDA’s Cross Default so that if the combined amount outstanding under the two limbs of Cross Default exceed the Threshold Amount, then it will be an Event of Default. Normally, under the 1992 ISDA, Cross Default requires one or the other limbs to be satisfied — you can’t add them together. This was a bit of a snafu.
The two limbs are:
- a default under a financial agreement that would allow a creditor to accelerate any indebtedness that party owes it;
- a failure to pay on the due date under such agreements after the expiry of a grace period.
Summary
Cross Default is intended to cover the unique risks associated with lending money to counterparties who have also borrowed heavily from other people.
Now, if — as starry-eyed young credit officers in the thrall of the moment are apt to — you apply this thinking to contractual relationships which aren’t “term loany” in nature — that is, that don’t have long spells where one party is deeply in the hole to the other, with not so much as interest payment due for months whose failure could trigger any acceleration — it will give you trouble. We go into this more in the premium JC.
Specified Indebtedness is generally any money borrowed from any third party (e.g. bank debt; deposits, loan facilities etc.). Some parties will try to widen this: do your best to resist the temptation. Again, more details on why in the premium section.
The Threshold Amount is a key feature of the Cross Default Event of Default in the ISDA Master Agreement. It is the level over which accumulated indebtedness defaults comprise an Event of Default. It is usually defined as a cash amount or a percentage of shareholder funds, or both, in which case — schoolboy error hazard alert — be careful to say whether it is the greater or lesser of the two.
Because of the snowball effect that a cross default clause can have on a party’s insolvency it should be big: like, life-threateningly big — because the consequences of triggering a Cross Default are dire, and it may create its own chain reaction beyond the ISDA itself. So expect to see, against a swap dealer, 2-3% of shareholder funds, or sums in the order of hundreds of millions of dollars. For end users the number may well be a lot lower (especially for thinly capitalised investment vehicles like funds — like, ten million dollars or so — and, of course, will key off NAV, not shareholder funds.
For those noble, fearless and brave folk who think Cross Default is a bit gauche; a bit passé in these enlightened times of zero-threshold VM CSAs[1] but can’t quite persuade their credit department to abandon Cross Default altogether — a day I swear is coming, even if it is not yet here — one can quickly convert a dangerous Cross Default clause into a less nocuous (but still fairly nocuous, if you ask me — nocuous, and yet strangely pointless) cross acceleration clause — meaning your close-out right that is only available where the lender in question has actually accelerated its Specified Indebtedness, not just become able to accelerate it, with some fairly simple edits, which are discussed in tedious detail here.
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 👇 |
- The JC’s famous Nutshell™ summary of this clause
- Dealer danger: why Cross Default is more of a boon than a bane, if you are a bank or dealer
- Specified Indebtedness, common tweaks, and the JC’s opinion thereof
- The Threshold Amount
- DUST v Cross Default: showdown
- The cherrypickability of individual bits of indebtedness to get you over the line and why this means you should not include derivatives
See also
References