NAV trigger

Hedge Funds & Prime Brokerage Anatomy™ Go Premium There is no industry standard prime brokerage agreement, so this is not so much an anatomy as a collection of resources about an amorphous subject. Hedge fund | AIFMD | Depositary | Prime broker | prime brokerage agreement | synthetic prime brokerage | margin lending | custody asset | CASS Anatomy | reuse & rehypothecation | hedge fund | leveraged alpha | greeks | short selling Index: Click ᐅ to expand: Prime Brokerage Securities Financing Investment Strategies Comments? Questions? Suggestions? Requests? Insults? We’d love to 📧 hear from you. Sign up for our newsletter.

The right to terminate a master agreement as a result of the decline in net asset value of a hedge fund counterparty (other counterparty types generally won't have a “net asset value” to trigger).

Often there are three levels of trigger: Monthly; Quarterly and Annually. You may find yourself embraced in a tedious argument about whether these should be “rolling” (that is, judged for the period from any day) or “point-to-point” (that is, judged from a defined day to the end of the period following that day).

In practice an official NAV is only “cut” once for every “liquidity period”, and it is hard to see how a credit officer, however enthusiastic, could determine what the net asset value was at any other time. On the other hand, credit officers don’t usually monitor NAV triggers anyway, so what do they care?

All rather tiresome, and quite unnecessary if you have the right, as most prime brokers do, to jack up initial margin at your discretion.

Even though generally they’re not actively monitored, NAV triggers lead to the tedious cottage industry of waiving their breach. This is because while a prime broker’s credit risk department won’t have the inclination (or bandwidth) to monitoring the thousands of NAV triggers it has buried in its corpus of legal documentation, each hedge fund who has granted one will and, if it suffers a significant drawdown, won’t like an unexploded Additional Termination Event sitting on its conscience.It will ask for a waiver. If it has clever lawyers, it will explain that it has heightened cross default risk as a result. It may insist on one, even though you would think it ought to be in no position to be insisting anything.

Thanks to the no oral modification clause in Section 9(b) — which extends to waivers — a NAV trigger waiver must be given in writing. This then leads to an argument between legal and the credit department as to whose job it is to send out this waiver.

Legal: “You imposed the stupid NAV trigger, so you can damn well send out waivers for it.”

Credit: “Help! Help! It’s a legal agreement! I am not qualified to do this! I cannot opine!”

You’ll never guess where the JC’s sympathies lie.

Practical solution

Presuming you have reserved the right, as any sensible prime broker will, to increase your initial margin at any time, there is a way out of this, which ought to work perfectly well, but which your credit department will not like. That is to relegate the NAV triggers to any margin lockup you have agreed.

This means the NAV trigger is no longer, of itself, a Termination Event under the ISDA Master Agreement. All it entitles you to do is raise initial margin. Calling for more IM will achieve one of two things:

• The counterparty will deliver it, in which case your credit position, if precarious, can be sated;
• The counterparty can fail to deliver it, in which case you have a Failure to Pay or Deliver, being a much more robust Event of Default to take action.

Thus, it doesn’t trouble fastidious types who fuss about cross default or DUST, and the consequences of the trigger are in any case less apocalyptic for the fund, and less demanding of a waiver.

“But I don’t want to have a margin lockup just so I can have my NAV trigger”, your credit will wail. Sigh.

See also

• Credit mitigants
• Additional Termination Events