Events of Default - GMSLA Provision: Difference between revisions

10.1(b) Unremedied failure to manufacture Income: Lender or Borrower fails to manufacture Income on Loaned Securities or Collateral when due and has not remedied that failure within three Business Days of notice from the Non Defaulting Party requiring remediation;

10.1(c) Mini-Closeout failure: Either party failing to pay any sum when due following a mini-closeout (that is, under paragraphs 9.1(b) or 9.2(b) or 9.3;

10.1(d) Act of Insolvency: An Act of Insolvency occurring to Lender or Borrower. If Automatic Early Termination applies, if anyone presents a winding up petition or appoints a liquidator, it will be an Automatic Early Termination and the Non Defaulting Party need not serve written notice.

10.1(e) Breach of warranty: any Lender’s Warranty, or any of the Borrower’s Warranties except the ast one (14(e), about voting on Borrowed Securities) is materially incorrect when made or “deemed”;

10.1(f) Repudiation: Either party admitting that it cannot or will not perform any of its obligations hereunder where, upon completion of formalities, that non-performance would be an Event of Default;

10.1(g) Seizure of assets: a material part of its assets are ordered to be transferred to a trustee by a regulatory authority under any legislation.

10.1(h) Regulatory default: It is declared in default by the appropriate authority or is suspended or expelled from any securities exchange or other self-regulatory organisation, or is suspended from securities dealing by any government agency, for not meeting any requirements relating to financial resources or credit rating;

10(i) Other unremedied breach of agreement: Either party defaults on any of its other obligations under this Agreement and does not remedy them within 30 days of the Non Defaulting Party’s written notice requiring remedy.

10.2 Each Party must formally notify the other it if suffers any Event of Default or potential Event of Default.
10.3 There are no remedies for any Event of Default other than those set out in this Agreement. 10.4 Subject to the Failure to Deliver and Consequences of an Event of Default clauses, neither Party may claim consequential losses if the other Party breaches this Agreement.

view template

Failures to deliver

Why Bank does not apply an Event of Default to stock lending failures to deliver

The position under the GMSLA and OSLA master agreements

A failure to deliver Securities in not an Event of Default: a failure to deliver securities to initiate}} a loan is no breach of agreement, and a failure to redeliver Equivalent Securities at the end of a loan to complete it allows the Lender to buy in Securities to cover the fail.

Failure to deliver Collateral

By contrast a failure to deliver Collateral or Equivalent Collateral is an Event of Default.

Delivery Failures

Delivery failures are a feature of the market: deliveries frequently fail in the stock lending market - a 10% delivery failure rate is not uncommon, and it can be over 50% in emerging markets. They occur for a number of reasons:

Operational failure, such as a mismatch of instructions
A lender may lose its expected supply (for example a custodian may expect to lend but the owner of the securities sells before the loan settles)
A third party may fail to deliver to the party expecting to deliver under the securities loan
Lack of availability of the securities to deliver, for example, due to the shares going “special”
Exceptionally, due to lack of funds at the deliverer

Making delivery failures an Event of Default would put participants in a perpetual state of default for reasons not necessarily related to the solvency or creditworthiness of the "failing" counterparty.

The purpose of Events of Default

Events of Default are protections for use if a counterparty is in a potentially insolvent position. A non-defaulting party is able to immediately terminate all outstanding transactions prior to upon an Event of Default and so end its exposure.

They are not intended for breaches where the creditworthiness of a counterparty is not in question. Here, the parties can rely on the normal contractual remedies for breach of contract.

Allowing a party to declare an Event of Default allows extraordinary leverage over a minor breach – a failure to comply with a trivial term of the contract would allow a party to threaten to terminate all outstanding transactions. In the context of frequent delivery failures in a stock lending relationship, the moment a party wants to end the relationship it could pick one of the many delivery failures as grounds to terminate all trades and inflict considerable loss on the other party.

Importantly, the failures to deliver unrelated to solvency vastly outnumber those related to solvency. If a party wished to treat a failure to deliver as an indicator of insolvency, the instances where a true concern existed would be swamped by the false alarms where the delivery failure didn’t indicate a cause for concern.

A contrast must be drawn between delivery failures of the underlying security and delivery failures concerning collateral. A party has a choice whether to deliver securities as collateral. The party can select which collateral to deliver, and so can control the process better. If a party takes that choice and fails to deliver, the expected recipient is entitled to consider that the failure may represent a credit concern. In the market generally, most participants use cash collateral to avoid the risks involved with using securities as collateral.

Why does the GMSLA take a different approach to the OSLA?

When the GMSLA was being drafted in 1999, the International Stock Lenders’ Association released a draft that made a redelivery failure an Event of Default. ISLA members were concerned at the frequency with which borrowers failed to return securities at the end of loans, and wanted to tighten up on this. The London Investment Bankers’ Association (representing the intermediary market) responded that this was unreasonable. ISLA was determined that the Event of Default must remain, and as a compromise made a delivery failure to initiate a loan an Event of Default as well. This went against what lenders did in practice, as no lender would consider that if it failed to deliver to commence a loan that it had breached contract, let alone caused an Event of Default. Only if the lender agreed “guaranteed delivery” would a borrower consider that there was a breach of contract for a failure to deliver. Unfortunately, the final published version made all failures to deliver an Event of Default, and as a consequence the intermediary market generally has had to adopt the approach of amending the GMSLA to disapply a delivery failure being an Event of Default.

What is the protection for an expected recipient if a delivery failure occurs?

Deliveries in stock lending typically occur free of payment, with the cash moving after the shares are confirmed as settling. This is for 3 principal reasons:

The cash collateral is frequently not in the same currency as the domestic market of the security, meaning that a delivery versus payment could not be arranged.
Attempting to match payment instructions to delivery instructions on a DVP basis would increase an already high failure rate.
The high failure rate means that if cash were due to move at the same time or prior to the shares moving, the cash would frequently be transferred against shares that fail. As mentioned earlier, if the lender fails to deliver shares to initiate the trade, the normal intention of parties is that no loan would be initiated. So it would be anomalous for cash to be transferred to the lender for a securities loan that might never occur.

In practice, each day market participants determine the securities and collateral that have settled and are currently held by each party, calculate the value of those securities and collateral at the most recent market close available to that party, and make a collateral call for any shortfall. If a party were expecting a delivery of securities, it would not have delivered cash overnight when the securities were due to settle but would instead be waiting until the following day to pay the cash against a margin call by the deliverer. If the securities were never delivered, the consequence would be that the amount of the margin call against the expected recipient would be reduced. (Or if securities prices on other stock loans had moved in the expected recipient’s favour, the expected recipient’s call against the failed deliverer would be increased.) If the failed stock loan were the only trade between the parties, then:

If the failure was by the lender at the start of the loan, no loan would be entered into, and neither party has any exposure.
If the failure was by the borrower at the end of the loan, the lender would not return the cash, and each party has the same exposure that it did the previous day (other than market movements on the securities).

The correct approach is that under the OSLA agreement:

A delivery failure by a lender when initiating a loan has no consequence – it is neither an Event of Default, nor a breach of contract.
A redelivery failure by a borrower at the end of the loan is not an Event of Default. Rather, the lender is free to buy in the securities using the procedure under section 9.4 of the GMSLA.
A failure by either party to deliver collateral when required is an Event of Default.

This correctly addresses the credit concerns that a party may justifiably have under a stock lending relationship, while also reflecting the intentions of the transacting parties when entering into securities loans. update to anat|gmsla

Navigation 2010 GMSLA 1 · 2 · 3 · 4 · 5 · 6 · 7 · 8 · 9 · 10 · 11 · 12 · 13 · 14 · 15 · 16 · 17 · 18 · 19 · 20 · 21 · 22 · 23 · 24 · 25 · 26 · 27 · Schedule · Agency Annex · Addendum for Pooled Principal Agency Loans 2018 Pledge GMSLA 1 · 2 · 3 · 4 · 5 · 6 · 7 · 8 · 9 · 10 · 11 · 12 · 13 · 14 · 15 · 16 · 17 · 18 · 19 · 20 · 21 · 22 · 23 · 24 · 25 · 26 · 27 · 28 · Schedule · Agency Annex Stock lending agreement comparison: Includes navigation for the 2000 GMSLA and the 1995 OSLA

Index: Click ᐅ to expand:

GMSLA

Pledge GMSLA

OSLA

2010 GMSLA: Full wikitext · Nutshell wikitext | GMLSA legal code | GMSLA Netting
Pledge GMSLA: Hard copy (ISLA) · Full wikitext · Nutshell wikitext |
1995 OSLA: OSLA wikitext | OSLA in a nutshell | GMSLA/PGMSLA/OSLA clause comparison table
From Our Friends On The Internet: Guide to equity finance | ISLA’s guide to securities lending for regulators and policy makers

@@ Line 1: / Line 1: @@
 {{2010 GMSLA Section 10 TOC}}
-{{subst|gmslap|10}}
+{{gmslasnap|10}}
+{{comm}}
+{{nuts|GMSLA|10}}
+====See Also====
+{{gmslaanatomy}}
 ===Failures to deliver===

Events of Default - GMSLA Provision: Difference between revisions

Revision as of 17:04, 7 November 2016

Contents

Commentary

See Also

Failures to deliver

The position under the GMSLA and OSLA master agreements

Failure to deliver Collateral

Delivery Failures

The purpose of Events of Default

Why does the GMSLA take a different approach to the OSLA?

What is the protection for an expected recipient if a delivery failure occurs?

Navigation menu

Events of Default - GMSLA Provision: Difference between revisions

Revision as of 17:04, 7 November 2016

Commentary

See Also

Failures to deliver

The position under the GMSLA and OSLA master agreements

Failure to deliver Collateral

Delivery Failures

The purpose of Events of Default

Why does the GMSLA take a different approach to the OSLA?

What is the protection for an expected recipient if a delivery failure occurs?

Navigation menu

Search