Merger Without Assumption - 1992 ISDA Provision
|
1992 ISDA Master Agreement A Jolly Contrarian owner’s manual™
5(a)(viii) in all its glory
Related agreements and comparisons
Resources and Navigation
|
Overview
Redlines
- 1987 ⇒ 1992: Redline of the ’92 vs. the ’87: comparison (and in reverse)
- 1992 ⇒ 2002: Redline of the ’02 vs. the ’92: comparison (and in reverse)
- 1987 ⇒ 2002: Redline of the ’92 vs. the ’87: comparison (and in reverse)
Discussion
ISDA’s crack drafting squad™ giveth and ISDA’s crack drafting squad™ taketh away.
In 1992, ISDA’s crack drafting squad™ added references to a party’s Credit Support Providers and Credit Support Documents — the 1987 ISDA did not have a concept of a Credit Support Provider at all (though it does contemplate Credit Support Documents).
In 2002 some further enhancements: ISDA’s crack drafting squad™ had contrived some different ways of describing how a company might reorganise itself (specifically, “reorganisation, reincorporation or reconstitution”). It also, uncharacteristically, deletes the text “by operation of law or pursuant to an agreement reasonably satisfactory to the other party to this Agreement”. This removes an unnecessary restriction on the foregoing event (the surviving entity failing to assume all the obligations under the ISDA) so makes sense: the squad here is just correcting its own verbal profligacy.
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.
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
See also
Template:M sa 1992 ISDA 5(a)(viii)