Can we fet pledge benifit
@TheGouda / @Ruchi_Porwal / @siva / @nithin,
I am facing the duplicate entries issue in secondary holdings and have reported at least thrice about this issue and the worst is for some scrips i don’t see anything.
I am not understanding why this issues keep on occurring again and again and Z support is not providing any ETA and just stuck to boilerplate responses.To be fair nothing changed from August 2025 to March 2026 in terms of the issue that i see with respect to secondary demat.
ticket #20250821753404
Apologies, Manoj. While we’ve been able to fix most of the existing bugs, the ongoing transfers are updating fine. It’s the old transfer for specific dates in 2025 that are taking time to resolve; we’re on it. Let me check your case and have our team reach out to you.
MY Ticket #20260220735249 is not yet closed . Also facing these issues in portfolio
The view breakdown is linked to secondary so viewing from portfolio it show the breakdown from secondary holding . example ticker is SBISILVER
@sandeep_cs Apologies for the delay this is being looked into with the team. We’ll share an update soon.
1 Like
I am writing to formally raise a serious complaint regarding multiple discrepancies in my portfolio, P&L statement, and Tax P&L statement after availing your Secondary Demat Account facility.
Initially, I opted for this facility expecting better flexibility for tax harvesting. However, instead of providing benefits, it has resulted in significant inconsistencies and errors in my account.
I had transferred multiple holdings (including bonus shares) such as CDSL, BPCL, MOTHERSON, NMDC, CONCOR, PIDILITIND from my primary demat account to the secondary account. Subsequently, due to recurring system issues, I transferred all holdings back to my primary account.
Key Issues Observed:
• Several holdings are incorrectly reflected as “sold” in FY 2025–26, even though no sale transactions were executed.
• Bonus share records are missing, leading to incorrect holdings data.
• Incorrect transaction history is being displayed.
• Portfolio valuation mismatch due to wrong average price calculations.
• Tax P&L statement showing inflated/incorrect profits, which may lead to incorrect tax liability.
I would like to clearly state that:
• These shares were only transferred between demat accounts, not sold.
• I have already shared the global report, which confirms that no sale transactions took place.
Additionally, I received a response stating that P&L and buy averages were recalculated using the FIFO method. This is not acceptable in this case, as:
FIFO should not be applied to intra-account transfers.
The purpose of introducing the Secondary Demat Account facility was to avoid such complications and maintain flexibility in managing holdings and taxation.
My Concerns:
This issue appears to be a system-level error triggered by your secondary account feature, and it has:
• Distorted my financial records
• Impacted my portfolio accuracy
• Created serious complications for upcoming income tax filing.
Required Action:
I request you to conduct a thorough investigation using contract notes and the global report already shared
• Correct all incorrect “sold” entries
• Restore accurate bonus share records
• Fix average price calculations and portfolio valuation
• Provide a revised and accurate Tax P&L statement
This matter is extremely urgent as tax filing timelines are approaching. I expect a complete and permanent resolution, not a temporary fix.
If this issue is not resolved promptly, I will be compelled to escalate it further to higher authorities.
Regards,
Vikrant Gaurav
Client ID: UX2427
1 Like
Vikrant, we’ll check and update you over a ticket.
Any update on this ticket as don’t see any timelines with fixing the duplicate entries, buy avg, qty issue in secondary demat account.
ticket #20250821753404
I don’t see any useful responses over the ticket as the ticket is going back and forth from August 2025 to now.
Note: This is not specific to 2025 transfers even scrips that were transferred in 2026 are also impacted so please don’t give any default answers without investigation
@siva/@nithin,
don’t we have any specific timeline to fix this feature. Can you please train the support team on specifying the proper details of this issue.
just sharing some worknotes from the case:
“”" In the meantime, you can verify the tradebook details for buy average calculations. We will notify you as soon as the discrepancy is resolved. We appreciate your patience and cooperation in this matter.
“”"
We are almost at end of April and the issue is not sorted out. if this is how i need to do look for details then what benefit i am getting out of secondary demat account apart from stopping from impulse decisions to sell.
1 Like
Hi Manoj, a couple of fixes haven’t worked as expected. Last week we’ve closed majority of the issues and recalculated for the affected users. Let me check your ticket and update you tomorrow.
Thanks @TheGouda.
Hope this is a permanent fix and not a temporary fix done like during the months of Jan, February 2026 by manually updating the entries in the backend
Hello @TheGouda
Any update on the ticket no #20260220735249 - Discrepancy in shares transferred between primary and secondary demat accounts .
Checking this, Sandeep.
Secondary demat is a garbage product from Zerodha. I tried to transfer my holdings from secondary demat to primary demat on 23-Apr. I could not authenticate with CDSL so those transfer requests should have been cancelled and marked as failed by Zerodha after 24-48 hours as mentioned in their help link. Instead they were kept in some limbo state on Zerodha side.
When I tried to transfer the holdings again on 11-May, all the network requests returned a failure response from Zerodha but whoever the genius implemented this Recent Transfers section made it to add new rows even when Zerodha returned an error response.
I approached support team and raised a ticket with number #9986 requesting them to fix this and as usual, support team does not bother to read what is written and just replies saying that I need to authenticate on CDSL and support team proudly closed the tickets. I checked on CDSL and there was nothing to authenticate.
This product is only for people who want to save pennies. If you have any reasonable size of portfolio don’t bother using this product. They are using users as beta testers wasting lots of users’ time.
1 Like
Hi, we’re sorry to hear this. The previous status should have updated correctly.
This appears to be an issue where an error response may have resulted in duplicate entries being created in the history section. If you could share the complete ticket details or DM your user ID, we’ll verify the logs and check what went wrong in your case.
It seems like you are stuck at the authorisation stage. When transferring stocks back from the secondary account to primary, you’ll have to use a separate TPIN, which is different from what you would have used during the primary to secondary transfer. Whenever your secondary account is activated, you will receive the TPIN for your secondary demat account via email. You can also generate the TPIN by entering the BO ID for your secondary account.
Our support team will get in touch with you to discuss the issues you faced while making the transfers.
That being said, we are also working on a new flow for transfers, which will reduce the steps and make the process simpler.
1 Like
Thank you very much for the prompt response from your team. The stock transfer request is approved on Console. I will complete the next steps on CDSL.
1 Like
@Ruchi_Porwal , @TheGouda
Please note - ticket no #20260220735249 created on Feb 20th and today is 13 May , till now no actions or resolution happened on this . I am not expecting
Looking for a resolution instead of a casual reply from Zerodha support.
Hi,
Checking this and will keep you posted