Template:Exposure under csa: Difference between revisions
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) No edit summary |
||
Line 13: | Line 13: | ||
The thing which, I think, causes all the confusion is the nature of payments under ''normal'' {{isdaprov|Transaction}}s are deterministic and generally specified in the {{isdaprov|Confirmation}}, whereas whether you need to make a payment at all under a CSA on any day depends, and how much you need to pay, depends on quite a lot of things and you only find out at the last minute. Therefore CSA payments are due “a regular [[settlement cycle]] after they are called” — loosey goosey, right? — whereas normal swap payments are due (say) “on the 15th of March” | The thing which, I think, causes all the confusion is the nature of payments under ''normal'' {{isdaprov|Transaction}}s are deterministic and generally specified in the {{isdaprov|Confirmation}}, whereas whether you need to make a payment at all under a CSA on any day depends, and how much you need to pay, depends on quite a lot of things and you only find out at the last minute. Therefore CSA payments are due “a regular [[settlement cycle]] after they are called” — loosey goosey, right? — whereas normal swap payments are due (say) “on the 15th of March” | ||
Day 1: Party A has an {{{{{1}}}|Exposure}} of 100 | *''Day 1'': Party A has an {{{{{1}}}|Exposure}} — is out of the money — to the tune of 100. Its prevailing {{{{{1}}}|Credit Support Balance}} is 90, so (let’s say, for fun, ''after'' the {{{{{1}}}|Notification Time}} on the {{{{{1}}}|Demand Date}}) Party B has called it for a {{{{{1}}}|Delivery Amount}} of a further 10, which it must pay, but not until tomorrow. | ||
*''Day 2'': Meanwhile, Party A has a {{isdaprov|Transaction}} payment of 10 that falls due to Party B, also tomorrow. The arrival of this payment will change Party A’s Exposure to Party B so it is 90. Assuming Party A also pays the Delivery Amount, by knock-off time tomorrow it will have posted a {{{{{1}}}|Credit Support Balance}} of 100, and its Exposure to Party B will only be 90. This means it will be entitled to call Party B for a {{{{{1}}}|Return Amount}} of 10. | |||
This seems rather a waste of operational effort, and will also take years off your credit officer’s life and may even cause his hair to catch fire. Can Party A just ''not'' pay the further Delivery Acount in anticipation of what will happen tomorrow? | |||
So it seems a little odd for Party A to be making a payment to Party B | |||
Fun times in the world of [[collateral]] [[operations]]. | Fun times in the world of [[collateral]] [[operations]]. |
Revision as of 15:24, 24 May 2021
Relevance of Section 6 to the peacetime operation of the Credit Support Annex
The calculation of {{{{{1}}}|Exposure}} under the CSA is modelled on the Section 6(e)(ii) termination methodology following a Termination Event where there is one Affected Party, which in turn tracks the Section 6(e)(i) methodology following an Event of Default, only taking mid-market valuations and not those on the Non-Defaulting Party’s side.
This means you calculate the {{{{{1}}}|Exposure}} as:
- (a) the Close-out Amounts for each Terminated Transaction plus
- (b) Unpaid Amounts due to the Non-defaulting Party; minus
- (c) Unpaid Amounts due to the Defaulting Party.
This is interesting because, as of its Termination Date the Transaction may be no more, but until those final exchanges are settled the obligations they represent — “Unpaid Amounts” in the argot of Section 6(e) — still exist and are included in the calculation of the {{{{{1}}}|Exposure}}.
Now, on the day you are meant to make that final settlement, which when (ahem — if) settled, would reduce your {{{{{1}}}|Exposure}}, you will call for your {{{{{1}}}|Delivery Amount}} or {{{{{1}}}|Return Amount}} assuming it has not (yet) been paid. By the time the Credit Support adjustment has been settled, that final settlement will have happened, meaning the person who paid the adjustment will be out of pocket, and will need to call it back (using the same process), and will be running overnight credit risk that, if she’d had the choice, she probably wouldn’t have.
The thing which, I think, causes all the confusion is the nature of payments under normal Transactions are deterministic and generally specified in the Confirmation, whereas whether you need to make a payment at all under a CSA on any day depends, and how much you need to pay, depends on quite a lot of things and you only find out at the last minute. Therefore CSA payments are due “a regular settlement cycle after they are called” — loosey goosey, right? — whereas normal swap payments are due (say) “on the 15th of March”
- Day 1: Party A has an {{{{{1}}}|Exposure}} — is out of the money — to the tune of 100. Its prevailing {{{{{1}}}|Credit Support Balance}} is 90, so (let’s say, for fun, after the {{{{{1}}}|Notification Time}} on the {{{{{1}}}|Demand Date}}) Party B has called it for a {{{{{1}}}|Delivery Amount}} of a further 10, which it must pay, but not until tomorrow.
- Day 2: Meanwhile, Party A has a Transaction payment of 10 that falls due to Party B, also tomorrow. The arrival of this payment will change Party A’s Exposure to Party B so it is 90. Assuming Party A also pays the Delivery Amount, by knock-off time tomorrow it will have posted a {{{{{1}}}|Credit Support Balance}} of 100, and its Exposure to Party B will only be 90. This means it will be entitled to call Party B for a {{{{{1}}}|Return Amount}} of 10.
This seems rather a waste of operational effort, and will also take years off your credit officer’s life and may even cause his hair to catch fire. Can Party A just not pay the further Delivery Acount in anticipation of what will happen tomorrow?
So it seems a little odd for Party A to be making a payment to Party B
Fun times in the world of collateral operations.