Zerodha Buy average Holdings Console Zerodha Corporate actions Discrepancy

Why your Zerodha buy average shows N/A or looks wrong

From WebNotes, a public knowledge base. Last updated . Reading time ~9 min. Level: Intermediate.

A buy average that reads “N/A” or looks obviously wrong on your holdings screen is unsettling, because it makes a position look like it has no cost basis or an impossible profit. In almost every case the number is not lost and nothing has gone wrong with your shares. It is a display state that reflects either an adjustment Zerodha is still processing or a cost that was never supplied to it. This article explains the situations that produce an N/A or an incorrect buy average on Zerodha Console , which ones fix themselves, and how to correct the ones that need your input.

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 anything described here.

Why the buy average shows N/A

The buy average is shown as N/A when Console cannot yet display a cost for the holding. The main situations that produce this are:

  • A pending corporate action. When a stock is undergoing a corporate action such as a bonus issue or a stock split , the buy average will need to be adjusted, and it can read N/A while that adjustment is being worked out.
  • ESOP shares. Shares received under an Employee Stock Ownership Plan can show N/A, because the acquisition cost is not established the way an ordinary market purchase is.
  • Shares that need manual entry. Where a holding arrived without a matching Zerodha buy trade, most often shares transferred in from another demat account , the cost has to be entered manually on Console before an average can be shown.

The common thread is that Console has no reliable cost figure to display. It shows N/A rather than guessing. Which of these applies determines whether you wait or act: the first fixes itself, the third needs you to supply the cost.

Why the buy average looks incorrect

A related but distinct complaint is that the buy average shows a value, but the wrong one. Zerodha calculates the buy average using the FIFO method , yet your buy average may become inaccurate after a corporate action. The events that cause this are, in Zerodha’s own words, “bonus, splits, rights issue, de-merger, merger, and others.”

Each of these changes the relationship between your quantity and your cost. A bonus issue increases your quantity without a cash outflow, so the per-share cost must fall. A split multiplies your quantity and divides your price. A de-merger or merger reallocates cost across securities. Until Console has applied the adjustment, the buy average it shows is based on the pre-event figures and therefore looks wrong against your post-event quantity.

Which problems fix themselves

For corporate actions, the correction is automatic. Zerodha manually updates the adjustment for such corporate actions once they are completed, and this process typically takes around two weeks from the date of the corporate action. During that period the buy average may show N/A or an incorrect value, and this is expected behaviour rather than a fault.

The important discipline here is patience. If you add a manual trade to “fix” a buy average that is only mid-adjustment, you will double-count the cost once the automatic adjustment lands, leaving the position more wrong than before. Wait out the roughly two-week window first. If the split shares have not even appeared in your holdings yet, that too is part of the same processing and resolves when the action completes.

Which problems you fix yourself

Where the cost was never supplied to Console, waiting will not help; you have to enter it. The classic case is shares transferred in from another broker . When shares are transferred into your Zerodha demat, only the units move. The buy average and the date of acquisition are not carried across, so the holding shows a discrepancy with an N/A or missing cost until you provide the purchase details.

You do this from the discrepancy view on Console: Portfolio > Holdings > View discrepancy > Add trade, entering the purchase date, price and quantity for each lot. Console allows only one entry per ISIN per date, so multiple transfer dates need multiple entries. The full procedure, including the date rules and the recalculation window, is set out in how to update or correct your buy average on Console . Take the cost figures from your previous broker’s contract notes or holding statement so your cost basis stands up for tax reporting .

The special case of newly listed and IPO shares

Freshly allotted shares can also show an N/A or unusual buy average briefly. If you received shares through an IPO allotment and the average cost is not displaying correctly on Kite , the causes and the fix are specific enough to warrant their own guide: see why the IPO average cost shows N/A on Kite . As with corporate actions, IPO-related adjustments are processed on Zerodha’s side and should not be manually overridden while they settle.

When you cannot fix it and must escalate

Some discrepancies cannot be self-corrected at all. You cannot resolve a discrepancy while a stock is inactive, for instance when it is unlisted, suspended, awaiting listing or has no trading volume. Once the stock becomes active again, its twelve-digit ISIN is displayed on Console alongside the quantity, and you can then resolve the discrepancy. Similarly, you cannot self-correct during trading holidays or while a recent corporate action or IPO is still being processed.

If none of the automatic windows apply and the manual tool will not let you resolve the position, raise the issue with Zerodha. The escalation path, including creating a support ticket and the handling for inactive stocks and CAS mismatches , is covered in how to fix a holdings discrepancy . Raising a ticket is the correct final step once the self-service options are exhausted.

Quick diagnosis

  • Recent bonus, split, rights, de-merger or merger? Wait about two weeks for the automatic adjustment. Do not add a manual trade.
  • Shares transferred in from another broker? Add the missing trade yourself in the discrepancy view, using costs from the source broker.
  • IPO or newly allotted shares? Give the allotment adjustment time; see the IPO-specific guide.
  • Stock inactive, suspended or awaiting listing? You must wait until it is active; the ISIN then appears and you can resolve it.
  • None of the above, or still wrong after the window? Raise a Console support ticket.

Whatever the cause, the underlying FIFO logic that drives the number never changes. An N/A or off-looking buy average is almost always a timing or a missing-data issue, not a mistake in the calculation itself.

Frequently asked questions

Why does my buy average show N/A on Zerodha Console?
The buy average shows N/A when Console does not yet have a cost to display for the holding. This typically happens when the stock is undergoing a corporate action whose adjustment is still pending, when the shares are Employee Stock Ownership Plan (ESOP) shares, or when the cost has to be entered manually on Console, such as for shares transferred in from another demat account.
Why is my buy average incorrect after a bonus or split?
Zerodha uses the FIFO method, but your buy average can become inaccurate after corporate actions such as bonus issues, splits, rights issues, de-mergers and mergers, because your quantity and per-share cost change. Zerodha updates the adjustment automatically once the action is completed, which typically takes around two weeks from the date of the corporate action.
Do I need to fix a pending corporate-action adjustment myself?
No. Corporate-action adjustments are applied automatically once the action is completed, usually within about two weeks. Adding a manual trade during this window would double-count the cost. Wait for the adjustment to reflect before deciding anything is wrong.
Why is the buy average missing for shares I transferred from another broker?
When shares are transferred into your Zerodha demat, only the units move. The buy average and date of acquisition are not carried across, so Console has no cost to display and flags a discrepancy. You supply the missing purchase details yourself using the Add trade option in the discrepancy view.
How do I get an incorrect buy average corrected?
If it is a pending corporate action, wait about two weeks for the automatic adjustment. If the cost is genuinely missing, such as for transferred shares, add the trade yourself in Console. If you cannot resolve it because the stock is inactive or still processing, raise a Console support ticket.

See also

References

  1. Zerodha Support, Why is the buy average for some shares shown as N/A?, support.zerodha.com.
  2. Zerodha Support, Why is the buy average for some shares I’ve purchased incorrect?, support.zerodha.com.
  3. Zerodha Support, Editing discrepant holdings on Console, support.zerodha.com.
  4. CDSL India, Consolidated Account Statement and demat transfers, cdslindia.com.

Related articles

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
Conflicts of interest
WebNotes is independent. No relationship with any broker, registrar or bank named in this article.