Template:M gen 1992 ISDA 2(c): Difference between revisions

From The Jolly Contrarian
Jump to navigation Jump to search
Created page with "{{M gen 1992 ISDA 2(c)}}"
 
No edit summary
 
Line 1: Line 1:
{{M gen 1992 ISDA 2(c)}}
{{M gen 2002 ISDA 2(c)}}

Latest revision as of 22:44, 27 March 2020

Transaction flows and collateral flows

In a fully margined ISDA Master Agreement, all other things being equal, the termination of a Transaction will lead to two equal and opposite effects:

The strict sequence of these payments ought to be that the Transaction termination payment goes first, and the collateral return follows, since it can only really be calculated and called once the termination payment has been made.

I know what you’re thinking. Hang on! that means the termination payer pays knowing this will increase its Exposure for the couple of days it will take for that collateral return to find its way back. That’s stupid!

What with the regulators’ obsession minimise systemic counterparty credit risk, wouldn’t it be better to apply some kind of settlement netting in anticipation, to keep the credit exposure down?

Now, dear reader, have you learned nothing? It might be better, but “better” is not how ISDA documentation rolls. The theory of the ISDA and CSA settlement flows puts the Transaction payment egg before the variation margin chicken so, at the moment, Transaction flows and collateral flows tend to be handled by different operations teams, and their systems don’t talk. Currently, the payer of a terminating transaction has its heart in its mouth for a day or so.

Industry efforts to date have been targeting at shortening the period between the Exposure calculation and the final payment of the collateral transfer.