Merger Without Assumption - ISDA Provision

From The Jolly Contrarian
Revision as of 17:16, 11 April 2020 by Amwelladmin (talk | contribs) (Replaced content with "{{manual|MI|2002|5(a)(viii)|Section|5(a)(viii)|medium}}")
Jump to navigation Jump to search

2002 ISDA Master Agreement
A Jolly Contrarian owner’s manual™

Resources and navigation

[[{{{1}}} - 1992 ISDA Provision|This provision in the 1992]]

Resources Wikitext | Nutshell wikitext | 1992 ISDA wikitext | 2002 vs 1992 Showdown | 2006 ISDA Definitions | 2008 ISDA | JC’s ISDA code project
Navigation Preamble | 1(a) (b) (c) | 2(a) (b) (c) (d) | 3(a) (b) (c) (d) (e) (f) (g) | 4(a) (b) (c) (d) (e) | 55(a) Events of Default: 5(a)(i) Failure to Pay or Deliver 5(a)(ii) Breach of Agreement 5(a)(iii) Credit Support Default 5(a)(iv) Misrepresentation 5(a)(v) Default Under Specified Transaction 5(a)(vi) Cross Default 5(a)(vii) Bankruptcy 5(a)(viii) Merger Without Assumption 5(b) Termination Events: 5(b)(i) Illegality 5(b)(ii) Force Majeure Event 5(b)(iii) Tax Event 5(b)(iv) Tax Event Upon Merger 5(b)(v) Credit Event Upon Merger 5(b)(vi) Additional Termination Event (c) (d) (e) | 6(a) (b) (c) (d) (e) (f) | 7 | 8(a) (b) (c) (d) | 9(a) (b) (c) (d) (e) (f) (g) (h) | 10 | 11 | 12(a) (b) | 13(a) (b) (c) (d) | 14 |

Index: Click to expand:

Section 5(a)(viii) in a Nutshell

Use at your own risk, campers!
5(a)(viii) Merger Without Assumption. The party (or a Credit Support Provider) merges with or transfers or all or substantially all its assets to another entity and:―
(1) the resulting entity does not assume all the original party’s obligations under this Agreement (or Credit Support Document); or
(2) the Credit Support Document does cover the resulting party’s obligations under this Agreement.

Full text of Section 5(a)(viii)

5(a)(viii) Merger Without Assumption. The party or any Credit Support Provider of such party consolidates or amalgamates with, or merges with or into, or transfers all or substantially all its assets to, or reorganises, reincorporates or reconstitutes into or as, another entity and, at the time of such consolidation, amalgamation, merger, transfer, reorganisation, reincorporation or reconstitution:―
5(a)(viii)(1) the resulting, surviving or transferee entity fails to assume all the obligations of such party or such Credit Support Provider under this Agreement or any Credit Support Document to which it or its predecessor was a party; or
5(a)(viii)(2) the benefits of any Credit Support Document fail to extend (without the consent of the other party) to the performance by such resulting, surviving or transferee entity of its obligations under this Agreement.

Related agreements and comparisons

Click here for the text of Section 5(a)(viii) in the 1992 ISDA
Click to compare this section in the 1992 ISDA and 2002 ISDA.

Comments? Questions? Suggestions? Requests? Insults? We’d love to 📧 hear from you.
Sign up for our newsletter.

Content and comparisons

ISDA’s crack drafting squad™ giveth and ISDA’s crack drafting squad™ taketh away. As it neatly excises one square of flannel here, it inserts another one, further itemising ways in which a company might reorganise itself, there. In practical terms — ones that might make a difference were they to be considered by the King’s Bench Division, that is — no real change between 1992 ISDA and 2002 ISDA.

Template

Summary

When a firm merges into, or is taken over by, another, some magical — or unexpected — things can happen. Not for nothing does the ISDA Master Agreement labour over the very description: that this might be a “consolidation, amalgamation, merger, transfer, reorganisation, reincorporation or reconstitution” — prolix even by the lofty standards of ISDA’s crack drafting squad™ — should tell you something. Generations of corporate lawyers have forged whole careers — some never leaving the confines of their law practices for forty or more years — out of the manifold ways one can put companies together and take them apart again.

Your correspondent is not one of those people and has little more to say about mergers, except that what happens to live contracts at the time of such chicanery will depend a lot on just how the companies and their assets are being joined together or torn assunder.

If the ISDA Master Agreement and its extant Transactions carry across — which, in a plain merger, they ought to — all well and good - though watch out for traps: what if both merging companies have ISDAs with the same counterparty, but on markedly different terms? Which prevails? Do they both? Which one do you use for new Transactions? This you will have to hammer out across the negotiating table.

But in some cases, Transactions might not carry across. Perhaps the resulting entity has no power to transact swaps. Perhaps it is in a jurisdiction in which they — or ISDA’s sainted close-out netting provisions, about which so many tears and so much blood is annually spilled — cannot be enforced. Perhaps the new entity just refuses to honour them.

Merger Without Assumption addresses all of these contingencies.

This is the clause that would have been covered by Section 5(a)(ii)(2) repudiation, had the resulting entity accepted the contract at all in the first place. It can be triggered if the resulting party repudiates any outstanding Transactions under the ISDA Master Agreement (or otherwise they are not binding on it); or any Credit Support Document stops working as a result of the merger.

Template

General discussion

And “all or substantially all” means what exactly?

There’s not a lot of case law on it. Some say 90%. Some say 75%. Some people — your correspondent included — say “shoot me”.

But, interestingly, Merger Without Assumption doesn’t seem to bite where one entity transferred all of its assets, half-half, into two distinct entities. I dunno — could it happen? Search me. You’ll have to go and find one of those corporate lawyers I was talking about before to find that out. They love that kind of stuff.

Template

See also

Template

References