Template:M summ 2016 CSA Exposure: Difference between revisions

From The Jolly Contrarian
Jump to navigation Jump to search
No edit summary
No edit summary
 
Line 1: Line 1:
{{CSA Exposure summ|vvmcsaprov}}
{{CSA Exposure summ|vmcsaprov}}
{{csa credit support amount calculation|vmcsa}}
{{csa credit support amount calculation|vmcsa}}

Latest revision as of 10:41, 24 May 2021

The total mark-to-market exposure under your ISDA Master Agreement on a given day, not counting anything posted by way of credit support. That is, Exposure omits the mark-to-market exposure of the Transaction comprising the CSA itself,[1] because that would entirely bugger things up: the MTM of an ISDA including the CSA is, of course, more or less zero.

Relevance of Section 6 to the peacetime operation of the Credit Support Annex

The calculation of 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 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.

There aren’t really likely, in peacetime, to be Unpaid Amounts loafing about — an amount that you are due to pay today or tomorrow wouldn’t, yet, qualify as “unpaid”, but would be factored into the Close-out Amount calculation.

There is a little bit of a dissonance here, since “Exposure” is a snapshot calculation that treats all future cashflows, whether due in a day, a month or a year from today, the same way: it discounts them back to today, adds them up and sets them off. Your Delivery Amount or Return Amount, as the case may be, is just the difference between that Exposure and whatever the existing Credit Support Balance is. The future is the future: unknowable, unpredictable, but discountable, whether it happens in a day or a thousand years.

All the same, this can seem kind of weird when your CSA you have to pay him an amount today when he owes you an even bigger amount tomorrow. It’s like, “hang on: why am I paying you margin when, tomorrow, you are going to be in the hole to me? Like, by double, if I pay you this margin and you fail to me tomorrow.”

The thing which, I think, causes all the confusion is the dates and amounts of payments under normal Transactions are deterministic, anticipatable, and specified in the Confirmation, whereas whether one is required under a CSA on any day, and how much it will be, depend on things you only usually find out about at the last minute. CSA payments are due “a regular settlement cycle after they are called” — loosey goosey, right? — (or even same day if you are under a VMV CSA and you are on the ball with your calls) whereas normal swap payments are due (say) “on the 15th of March”

So, a scenario to illustrate:

  • Day 1: Party A has an Exposure — is out of the money — to the tune of 100. Its prevailing Credit Support Balance is 90, so (let’s say, for fun, after the Notification Time on the Demand Date) Party B has called it for a 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 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 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?

Fun times in the world of collateral operations.

Market Quotation and the 2002 ISDA

  • Market Quotation? But I have a 2002 ISDA: Note the references to Market Quotation and other 1992 ISDA specific things. If you are under a 2002 ISDA, these should be corrected. Of you could sign up to the 2002 ISDA Master Agreement Protocol and that would do it for you. In the 2016 VM CSA, note both versions of the ISDA Master Agreement, with their contrasting approaches to close-out valuation, are provided for in the alternative.
  • Mid-market?: A slight cognitive dissonance: It talks about your 6(e)(ii) amount - which is generally your replacement cost, at your side of the market, but then goes on to say determined at the mid-market price, which is fair, though, because you aren’t in default, and if each party used its own side of the market the Credit Support Balance could never find stability or happeness, even fleetingly, and the credit support world would be in some kinds of infinite loop.

Calculating your 2016 VM CSA

Superficially things are quite different between the 1995 CSA and the 2016 VM CSA, but this all boils down to the fact that the 2016 VM CSA is meant to be a zero-threshold, variation margin-only affair, so the concepts of Independent Amount and Threshold, both of which confuse the 1995 CSA, aren’t there to get in the way. Unless you go and put them in anyway, as we shall see...

1995 CSA

How the IA contributes to the Credit Support Amount — being the amount of credit support in total that one party must have given the other at any time[2] under the 1995 CSA can be mind-boggling.

It pans out for a Transferee like so:

This leaves you with a formula for a Transferee’s Credit Support Amount as follows: Max[0, (ETee + IATor - IATee + Threshold)].

Let’s plug in some numbers. Say:

Your Credit Support Amount is therefore the greater of zero and 10,000,000 + 2,000,000 - 0 + 5,000,000) = 7,000,000.

Now, whether you have to pay anything or receive anything as a result — whether there is a Delivery Amount or a Return Amount, in other words — depends whether your Credit Support Amount is greater or smaller than your prevailing Credit Support Balance, by at least the Minimum Transfer Amount.

2016 VM CSA with no IA amendment

Since the 2016 VM CSA assumes there is no Independent Amounts and no Thresholds, it is quite a lot easier. It is just the Exposure. So much so, that there isn’t even a concept of the “Credit Support Amount” under the 2016 VM CSA, unless you have retrofitted one, and who in their right mind would do that?

Oh.

You have, haven’t you. You’ve gone and co-opted the Credit Support Amount (VM/IA) concept in your Paragraph 11 elections. Yes you did. No, don’t blame your credit department; don’t say you were just following orders. You did it.

2016 VM CSA with a customised IA amendment

Never mind. Well, just for you, the formula is a sort of half-way house: Under this unholy bastardisation of a 2016 VM CSA, a Transferee’s Credit Support Amount will be: Max[0, (ETee + IATor - IATee)].

  1. Assuming you are on a proper, sensible, English law title transfer CSA, which counts as a Transaction, and not one of those silly American ones, which doesn’t.
  2. As opposed to the amount required to be transferred on that day, considering the “Credit Support Balance” the Transferee already holds — that’s the Delivery Amount or Return Amount, as the case may be.
  3. There’s something faintly absurd both parties exchanging Independent Amounts by title transfer — they net off against each other — but that’s as may be. Stupider things have happened. SFTR disclosure, for example.