Tax Event Upon Merger - ISDA Provision: Difference between revisions
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) No edit summary |
||
Line 1: | Line 1: | ||
{{ | {{manual|MI|2002|5(b)(iv)|Section|5(b)(iv)|short}} | ||
Revision as of 21:00, 13 April 2020
2002 ISDA Master Agreement
Section 5(b)(iv) in a Nutshell™ Use at your own risk, campers!
Full text of Section 5(b)(iv)
Related agreements and comparisons
|
Content and comparisons
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
Tax Event Upon Merger: Note the missing “indemnifiable” from the fifth line of the 2002 ISDA version and the expanded description of “merger events” towards the end of the clause. And the renumbering as a result of the Force Majeure Event clause in the 2002 ISDA.
Summary
This is you can imagine, a red letter day for ISDA’s crack drafting squad™ who quite outdid itself in the complicated permutations for how to terminate an ISDA Master Agreement should there be a Tax Event or a Tax Event Upon Merger. Things kick off in Section 6(b)(ii) and it really just gets better from there.
So, Tax Event Upon Merger considers the scenario where the coming together of two entites — we assume they hail from different jurisdictions or at least have different practical tax residences — has an unfortunate effect on the tax status of payments due by the merged entity under an existing Transaction.
It introduces a new and unique concept — the “Burdened Party”, being the one who gets slugged with the tax — and who may or may not be the “Affected Party” — in this case the one subject to the merger.