How-to discrepancy with this stock buy average holdings Console off-market transfer

How to fix the 'there may be a discrepancy with this stock' message on Kite

From WebNotes, a public knowledge base. Last updated 21 June 2026. Reading time ~9 min. Level: Beginner.

Key facts

Exact message	There may be a discrepancy with this stock
What it means	The buy average for the holding is missing or unavailable, so a buy-average-dependent figure cannot be shown
Why it appears	Shares entered the demat through an off-market transfer, ESOP, IPO allotment, or a corporate action such as a bonus or split
Fix for off-market transfers	Manually update the buy average for the discrepant instrument in Zerodha Console
Fix for IPOs and corporate actions	No action needed; Zerodha automatically updates the buy average, so the alert clears on its own

Procedure

Read the exact alert and note the instrumentConfirm the message says ‘There may be a discrepancy with this stock’ and identify which holding it is attached to. The alert flags a single instrument whose buy average is missing, not your whole portfolio.
Identify how the shares entered your dematDetermine the source: an off-market transfer into the demat, an ESOP allotment, an IPO allotment, or a corporate action such as a bonus issue or stock split. The source decides whether you act or wait.
For an off-market transfer, update the buy average in ConsoleOpen Zerodha Console, go to the holdings view, and manually enter the buy average for the discrepant instrument. Use your actual acquisition cost so profit and loss and tax reports compute correctly.
For an IPO or corporate action, wait for the auto-updateFor shares from an IPO allotment or a corporate action, no action is needed. Zerodha automatically updates the buy averages, so you do not need to enter the information manually; the alert clears once the update runs.
Verify the holding and that the alert has clearedReopen the holding in Console and on Kite. Confirm the buy average now shows and the discrepancy alert no longer appears against the instrument before placing a sell order.
Raise a support ticket if it persistsIf the buy average is still missing after you updated it, or the auto-update has not run for an IPO or corporate action, create a ticket with Zerodha support naming the instrument and how the shares were received.

The “there may be a discrepancy with this stock” alert on Kite means the buy average for that holding is missing, so Zerodha cannot show a figure that depends on it; the fix is to manually update the buy average in Zerodha Console when the shares arrived by an off-market transfer , and to do nothing when they came from an IPO or a corporate action, because Zerodha updates those automatically. This guide identifies which case you are in and walks the correction.

The alert reads as alarming because it appears against a stock you genuinely hold, and a trader can mistake it for a holding that has gone missing or an order that is blocked. It is neither. The shares are in your demat; what is absent is the cost figure Zerodha needs to compute profit and loss and tax reports for that instrument. Shares that enter a demat outside a normal Kite buy, through a transfer from another demat, an employee stock plan, an IPO allotment, or a corporate action, can arrive without a cost attached, and the discrepancy alert is Zerodha flagging that gap. The remedy depends entirely on how the shares arrived, which is the first thing this guide establishes.

Conflict-of-interest disclosure. This guide is published by the WebNotes Editorial Team for informational purposes and is written independently. WebNotes operates a Zerodha account-opening referral programme, disclosed on the pages that carry the referral link; this guide does not carry it and earns no referral commission from the procedure described here.

Step-by-step procedure

The procedure infobox above lists the sequence. The detail below expands the two cases that decide your action: shares received by an off-market transfer, which you fix yourself, and shares from an IPO or corporate action, which Zerodha fixes automatically.

1. Read the exact alert and note the instrument

Confirm the message wording. The alert is “There may be a discrepancy with this stock,” and it is attached to one specific holding, not to your portfolio as a whole. Note which instrument carries it. The alert appears when the buy average for that instrument is missing or unavailable, so Kite cannot display the cost-dependent figures, the average price, the profit and loss, for that one holding. The shares themselves are present and saleable; only the cost reference is absent.

2. Identify how the shares entered your demat

The cause determines the cure, so establish the source of the shares. The discrepancy appears when shares were received through one of these routes: an off-market transfer into the demat account, an employee stock ownership plan (ESOP), an initial public offering (IPO) allotment, or a corporate action such as a bonus issue or a stock split. Each of these can deliver shares to the demat without a Kite buy order, and therefore without a buy average attached.

Split the four into two groups. Off-market transfers and ESOPs are ones where only you know the original cost, so you must supply it. IPO allotments and corporate actions are ones Zerodha can reconstruct, so it updates them itself.

3. For an off-market transfer, update the buy average in Console

If the shares came by an off-market transfer into your demat, you update the buy average yourself. Open Zerodha Console , go to the holdings view, find the discrepant instrument, and manually enter the buy average for it. Use your real acquisition cost, the price at which you actually bought the shares before they were transferred in, because this figure feeds the profit-and-loss report and the capital gains computation. An arbitrary or zero buy average will misstate your gains and your tax. The same manual-update route applies to ESOP shares, where you supply the perquisite-inclusive cost basis you actually hold the shares at.

This is a deliberate design choice: Zerodha cannot know the cost of shares you acquired elsewhere and transferred in, so it asks you to supply it once, after which the holding reports correctly.

4. For an IPO or corporate action, wait for the auto-update

If the shares came from an IPO allotment or a corporate action such as a bonus or split, no action is needed. Zerodha automatically updates the buy averages for these, so you do not need to enter the information manually. The discrepancy alert is transient in this case; it clears once Zerodha’s update runs, typically after the corporate action or allotment is processed on its books. For a bonus or split, the buy average is recomputed across the enlarged share count, which Zerodha handles on the back end.

Resist the urge to manually overwrite the buy average for an IPO or corporate-action holding, because doing so can conflict with the automatic update and leave the cost basis wrong. Wait for the auto-update and verify.

5. Verify the holding and that the alert has cleared

After you update the buy average for a transfer, or after the auto-update runs for an IPO or corporate action, reopen the holding in Console and on Kite. Confirm the buy average now shows a value and the discrepancy alert no longer appears against the instrument. Verify before you sell: a sale placed while the cost is still missing will produce a profit-and-loss and tax figure that is wrong until the cost is corrected, even though the sale itself executes.

6. Raise a support ticket if it persists

If the alert remains after you updated the buy average, or the automatic update has not run for an IPO or corporate-action holding after a reasonable period, create a ticket with Zerodha support. Name the exact instrument, state how the shares entered the demat, and attach the transfer record or allotment advice. The article that explains the alert directs unresolved cases to “create a ticket,” and support can correct a buy average that the standard routes did not.

Does the alert block orders?

The discrepancy alert is about a missing buy average, not an order block. The shares are in your demat and can be sold; what is affected is the accuracy of the cost-dependent reporting, the average price, the realised and unrealised profit and loss, and the capital gains statement for that instrument. If you sell while the buy average is missing or wrong, the sale goes through, but the gain is misstated until the cost is corrected.

This distinguishes the discrepancy alert from genuine order-blocking states. A stock you cannot buy at all is a different problem, covered in why you cannot buy a stock that is trading on the exchange , and an order that vanishes is covered in why a rejected order does not appear in the order book . The discrepancy alert sits in the holdings layer, not the order layer, so fix the buy average for clean reporting, but do not expect it to stop you transacting.

Why the cost basis matters for tax

The buy average is the cost of acquisition that drives every downstream tax figure for the holding. A wrong or zero buy average inflates the apparent gain on sale and overstates the capital gains tax, while the holding period determines whether the gain is short-term or long-term. For shares received by transfer, gift, or inheritance, the cost and the holding period generally carry over from the original acquisition rather than resetting on transfer, so the figure you enter should reflect the original purchase, not the transfer date.

For any sizeable holding, confirm the cost basis with a chartered accountant before relying on the Console figure for your tax return, because the carry-over rules for transferred, ESOP, and corporate-action shares interact. Tax rules change with each Finance Act; this guide reflects the position for FY2026-27.

What can go wrong

Entering a zero or guessed buy average. A wrong cost misstates profit and loss and overstates capital gains tax. Use the actual acquisition price for transferred or ESOP shares.
Manually overwriting an IPO or corporate-action holding. Zerodha updates these automatically; a manual entry can conflict with the auto-update and leave the cost wrong. Wait and verify instead.
Reading the alert as a missing holding. The shares are present; only the cost figure is absent. Do not assume the holding has vanished.
Selling before the cost is fixed. The sale executes, but the gain and tax are misstated until the buy average is corrected. Verify the cost first.
Skipping the support ticket when it persists. If the buy average will not save or the auto-update has not run, raise a ticket with the instrument and the receipt route rather than leaving the holding mis-reported.

External references

References

Zerodha support, “What does the error ‘There may be a discrepancy with this stock’ mean?” (accessed 21 June 2026), missing buy average and the off-market-transfer, ESOP, IPO, and corporate-action causes.
Zerodha support, Kite error messages and Console holdings documentation (accessed 21 June 2026).
Income Tax Act 1961, Sections 48 and 49, cost of acquisition and carry-over of cost on transfer; reflects FY2026-27.
CDSL operating instructions on off-market transfers and demat credits.

Reviewed and published by

WebNotes Editorial Team

The WebNotes Editorial Team covers Indian capital markets, payments infrastructure and retail investor procedures. Every article is fact-checked against primary sources, principally SEBI circulars and master directions, NPCI specifications and the official support documentation published by the intermediary in question. Drafts go through a second-pair-of-eyes review and a separate compliance read before publication, and revisions are tracked against the SEBI and NPCI rule changes referenced in the methodology section.

Last reviewed: 21 June 2026
Conflicts of interest: WebNotes is independent. No relationship with any broker, registrar or bank named in this article.