Profit and Loss Mismatch in Console and Kite

Zerodha Zerodha platforms
1

Hello Team,

I’m facing an issue that I believe may affect other users as well. I’ve noticed a mismatch in the Profit and Loss values shown in Console and Kite for several of my stocks.

I suspect the root cause is related to shares that were transferred from Zerodha demat account to Groww account. Since there is currently no option to manage long-term and short-term portfolios separately, I had to transfer shares to a different company’s demat account.

Issue:
When I purchase new shares of stocks that were previously transferred, Zerodha Console and Kite display incorrect Profit and Loss values. Additionally, when I use the “breakdown” option, it shows an inflated number of shares for those particular stocks.

Is there any possibility of enabling a reconciliation process—monthly, user-initiated, or even a weekly batch mode—that compares CDSL data with the holdings shown in Zerodha Console for specific stocks?

Thank you.

2

@sandeep_cs Could yu please DM me the ID?

Also, tagging @TheGouda @Ruchi_Porwal

3

DM sent. Just curious—am I the only one facing this Issue?

4

If you transfer shares to Zerodha demat - we won’t have trade details for such quantity; hence, it shows a discrepant tag. The user can add buy details, and our reports will be adjusted using the FIFO method.

However, if you transfer out, stocks are not available to trade in Kite, which can be the case for different reasons like suspension, delisting, etc., making recon difficult. However, you can always contact our team to sort the excess breakdown issue in case of transfer out. Since you’ve DM’ed us, we’ll get in touch.

5

As I mentioned in my initial post, I transferred shares from Zerodha to Groww. These are my long-term holdings, so I don’t want to sell them in the short term—especially since FIFO (First In, First Out) applies, and Zerodha currently doesn’t offer the option to maintain separate portfolios for long-term and short-term holdings. I’ve raised several tickets regarding this issue but haven’t received a resolution yet:

  1. #20240710557824
  2. #20250128294000
  3. #20240506783943
  4. #20231221172520
6

@sandeep_cs The team is checking this, and someone from our side will get in touch. Unlisting this since it’s support related.