NAV cut off time for liquid funds and over night funds

I have gone through the NAV cut off times published by dhan. It is showing 12.30 pm for liquid funds to get same day NAV. Then what is the cut off time for liquid and over night funds to get previous day NAV. In groww platform it is 12pm and in coin it is 12.30pm to get previous day NAV for liquid and over night funds. Why in dhan no cut off time published for previous day NAV for liquid and over night funds?

Hi @Nagasahitya

On Dhan, 12:30 PM is the only cut-off you need to think about for liquid and overnight funds.

We don’t publish a second cut-off because the app already does the heavy lifting on your behalf. The moment you place an order, the order-status screen shows the confirmation and allotment dates. You don’t have to figure out which NAV applies or decode multiple timings - we show you the final outcome directly.

Our intention is simple: make the experience clearer and reduce the effort on the user’s side. If anything still feels confusing, happy to hear it

One simple question @Saurav.P . Coin and groww are giving previous day NAV for liquid funds and overnight funds if We place the order before cut off time. Why dhan unable to provide it? See groww cut off time in attached screenshot. Liquid and overnight are safest funds to park emergency fund, if I get previous day NAV it will be beneficial.

see the attached unit allocation screenshot from groww where I have placed the order on 19 Nov 11.57 am which is before the cut off time proposed by groww, see i got 18 Nov NAV which is previous day.

Hi @Nagasahitya

Thanks for calling this out so clearly.

You’re right - having a visible previous-day NAV cut-off helps users who track these funds closely. We’ve taken your feedback in, and we’ll get this added in the upcoming release so the behaviour is consistent and transparent for everyone.

I have placed the order on 19 Nov, 8.12 am in Jio BlackRock liquid fund but i didn’t got previous day NAV . I got 19 Nov NAV.

Hey @Nagasahitya, as discussed over the call, we’ve addressed the NAV query from our end. Thank you for your patience and understanding.