82,972
edits
Template:Isda 1(c) summ: Difference between revisions
no edit summary
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
===Section 1(c)=== | ===Section 1(c)=== | ||
Section 1(c) starts getting a bit tastier in that it comprises the [[Single Agreement]]. This is deep ISDA lore, from which all the [[close-out netting]] that gives the {{isdama}} its capital efficiency wings flows. | Section 1(c) starts getting a bit tastier in that it comprises the [[Single Agreement]]. This is deep ISDA lore, from which all the [[close-out netting]] that gives the {{isdama}} its capital efficiency wings flows. | ||
Here several pieces of ISDA magic come together to create the capital foundation of the {{isdama}}. The challenge was creating an architecture that allowed discrete, unitary, complete {{isdaprov|Transaction}}s, such that creating a new one or terminating an old one didn’t upset the economic or legal integrity of other {{isdaprov|Transaction}}s that were currently on foot, while at the same time creating an umbrella framework so that, should something regrettable happen to either party, all Transactions can be quickly rounded up, evaluated, stopped and then netted down to a single sum. | |||
This latter piece involved some canny financial engineering. The general rules of [[set-off]] require not just a mutuality of parties to the off-setting claims, but also amounts falling due on the same day and in the same currency — neither of which was necessarily true of independent {{isdaprov|Transaction}}s executed under an multi-currency, cross-border {{isdama}}. | |||
The answer was this concept of the “{{isdaprov|Single Agreement}}”: the over-arching agreement that, however independent and self-contained Transactions are for any other purpose, when it comes to their Early Termination they transmogrify themselves into the single host agreement, and are reduced to calculation inputs to the final amount which one party must pay the other. | |||