Events of Default - GMSLA Provision
GMSLA Anatomy™
A Jolly Contrarian owner’s manual™ Go premium
Crosscheck: 10 in a Nutshell™
Original text
Resources and Navigation
|
Comparisons
Redlines
2010 ⇒ 2018: Redline of the 2010 GMSLA vs. the 2018 Pledge GMSLA: comparison (and in reverse)
Discussion
The major differences between the 2010 GMSLA and 2018 Pledge GMSLA Events of Default are:
- Collateral obligations: Under the 2010 GMSLA it is bilateral and refers to Cash Collateral and the Delivery, but not return, of non-cash Collateral, whereas the 2018 Pledge GMSLA makes any failure to meet Collateral obligations an Event of Default.
- Manufactured income: Under the 2010 GMSLA it is bilateral; under the 2018 Pledge GMSLA it applies against the Borrower only.
- Failure to Pay or Deliver: Under the 2010 GMSLA it is bilateral; under the 2018 Pledge GMSLA it applies against the Borrower only.
- Insolvency: There is an Automatic Early Termination trigger under the 2010 GMSLA but not the 2018 Pledge GMSLA.
- The remainder of the Events of Default are the same as between the two versions, but the 2018 Pledge GMSLA surprises us at the last moment with a new subparagraph 10.1(j) containing a brand new “breach of security agreement” Event of Default.
Which is nice.
Basics
The consequences and ramifications of Events of default under the 2010 GMSLA and the 2018 Pledge GMSLA are different so this section varies quite a bit between the editions.
The reason for divergence
Why the differences in sections (a) through (d)? These reflect the different theoretical underpinnings. Unlike in the 2010 GMSLA the provider of Collateral in a 2018 Pledge GMSLA does not give up either title to it, or control over it: it sits quietly in a darkened corner of the triparty system, in a pledge account, immobilised, held for the security of a passive principal lender, but not going anywhere.
Unlike most pledge arrangements for financial assets in the derivatives trading world, which are a bit of a pantomime and ultimately a sham,[1] a 2018 Pledge GMSLA pledge really is a pledge. The pledged Collateral assets don’t get re-optimised, they can’t be rehypothecated, sold, used, or eaten by the 2018 Pledge GMSLA (at least not unless, and until, the Borrower goes titten hoch). So the Borrower owns them, and has a degree of control over them throughout. If they are not returned, this is likely to be a failure of the custodian, or the triparty system, and not the Lender (who is likely to be a passive participant in an agent lending programme, and not involved in the operational process at all.
The same therefore goes for manufactured income off posted collateral, and a failure to redeliver pledged Collateral.
Automatic Early Termination
Unusually for a securities financing arrangement, there is an Automatic Early Termination provision. There is a separate article on that because it is a bit of an oddity.
No Event of Default without notice
Note that (unlike the ISDA Master Agreement an event only becomes an Event of Default once the Non Defaulting Party has given the Defaulting Party notice of it.
The dog that didn’t bark in the nighttime
More interesting than the Events of Default that are there are the ones that are not: There is no equivalent of:
- Cross Default
- Default under Specified Transaction
- Credit Support Default
- Merger without Assumption
- Illegality
- Tax Event
- Credit Event Upon Merger
- Tax Event Upon Merger
Why not? Well, unlike an ISDA Master Agreement, generally, securities financing transactions are generally short-dated (if repos) or callable on notice (if stock loans) and (unlike an ISDA, where margin is a function of an independent credit support arrangement which may or may not be there) daily margin is a structure feature of the transaction. If your counterparty suffers any kind of credit deterioration, your margin (or its failure to pay it) should cover you, and if it doesn’t, you can immediately — or at least quickly — get out of your exposure. If they unwind okay—great. If they don’t, you have them bang to rights on a Failure to Pay. Simples.
Your more perfidious counterparties might want to start crow-barring these events in — at least, ones like Illegality — especially if you, like many brokers, are in the habit of doing trades on term. An Illegality event ought not poop the nest, but a credit deterioration-related default events like DUST or Cross Default may, seeing as the very point of the term trade is to prove to your accountants you have stable financing of your margin loan operations.
Failures to deliver are not Events of Default
Failures to deliver Securities under a 2010 GMSLA are not Events of Default because failure to deliver securities to initiate a Loan is not a breach of agreement, and if a Borrower fails to redeliver Equivalent Securities at the end of a Loan, the Lender may buy in Securities to cover the fail, and may execute a mini close-out, but that is not an Event of Default either.
But a failure to deliver Collateral at inception or to redeliver Equivalent Collateral on termination is an Event of Default.
Deliveries frequently fail in the stock lending market for many reasons:
- Operational failures, such as a mismatch of instructions.
- A Lender may lose its expected supply (for example a rehypothecating prime broker intending to rehypothecate client’s securities where the client recalls and sells the securities before the Loan settles)
- A market counterparty may fail against the party expecting to deliver under the Loan
- Market events may cause a lack of liquidity — for example, if the shares go “special”
Making delivery failures an Event of Default would put participants in a perpetual state of default even though there were no credit concerns for the "failing” counterparty. Events of Default are really only meant to address counterparty insolvency risk: The innocent party can immediately terminate all outstanding transactions upon an Event of Default and so end its exposure.
Where the creditworthiness of a counterparty is not in question the innocent party can rely on normal contractual remedies for breach of contract.
Allowing a party to declare an Event of Default allows extraordinary leverage for what is often a technical or minor breach.
Compare that with Collateral delivery failures. The Borrower can choose what it delivers as Collateral. If, having done so, the party still fails to deliver, the recipient has grounds for a credit concern.
What is the protection for delivery failures then?
Deliveries in stock lending are usually free of payment: cash collateral moves after the shares settle. This is for 3 reasons:
- The cash collateral is not usually in the same currency as shares, meaning that a delivery versus payment is not practical anyway.
- Requiring DVP would increase an already high failure rate.
- Because of the high failure rate, the cash would frequently be transferred against failed settlements, presenting an inverted credit risk.
In practice, each day participants determine the securities and collateral that are currently held by each party, calculate their values as at market close, and make a collateral calls for any shortfall. A Borrower expecting to be delivered securities would wait for them to settle before paying away cash against a margin call by the Lender. If they were not delivered, the margin call against the Borrower would be reduced.
All other things being equal:
- If a Lender failed to settle at inception there would be no loan and neither party would have any exposure.
- If a Borrower failed to settle at redemption, the Lender would not return Collateral, and (but for intraday market moves) each party would have the same exposure it had previously.
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👇
|
See also
References
- ↑ Sorry, Americans, but it is true.