How to update or correct your buy average on Zerodha Console

Most of the time you never touch your buy average. Zerodha computes it automatically from your trades using the FIFO method and adjusts it for corporate actions on its own. There is one situation where Console genuinely cannot work the number out for itself: shares that entered your demat account without a matching buy trade in your Zerodha account, most often shares transferred in from another broker . In that case Console flags a discrepancy and lets you supply the missing purchase details so the cost basis is complete. This guide walks through that correction, the rules Console enforces, and the handling for transferred shares.

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.

When you should update the buy average

Add a trade only when Console is actually missing purchase information. The legitimate cases are:

• Shares transferred in from another demat account. When shares move into your Zerodha demat, only the units are transferred. The buy average and the date of acquisition are not automatically included, so Console has no cost to work with and raises a discrepancy.
• Off-market receipts and similar credits where a quantity landed in your demat without a corresponding Zerodha buy trade.

Do not add a trade to “correct” a buy average that looks off because of a recent bonus , split or other corporate action. Those are adjusted automatically and the process typically takes around two weeks; adding a manual trade on top will double-count the cost. If you are not sure which case you are in, read why your buy average shows N/A or looks wrong first.

Step-by-step: adding the missing trade

Step 1: Open Holdings on Console

Sign in to console.zerodha.com and go to Portfolio, then select Holdings from the dropdown. Any holding with a cost discrepancy carries a warning symbol next to the scrip name.

Step 2: Open the discrepancy view

Click the warning symbol on the flagged stock and choose View discrepancy. Console lists the securities whose buy average or acquisition details are incomplete, identified by their ISIN and quantity.

Step 3: Select the stock and click Add trade

Pick the affected stock from the discrepancy list and click Add trade. A short form opens where you provide the details Console is missing.

Step 4: Enter the purchase date, price and quantity

Enter the purchase date, price and quantity for the trade, and click Add. Two rules apply to the date, and Console will reject the entry if you break them:

• The purchase date should be on or before the demat credit date. You cannot claim to have bought the shares after they were credited to your account.
• You cannot enter a weekend or trading holiday as the purchase date. If you do, Console returns the error “Required information to perform this action is not available.”

Step 5: Repeat per date, then wait for the recalculation

If the shares arrived across more than one date, add one entry for each date (see the transferred-shares rules below). Once your entries are in, the buy average is recalculated using FIFO and updates within 24 working hours.

The ISIN and date rules for transferred shares

Shares transferred in from another broker are the most common reason to use this tool, and they come with a specific constraint. Console allows only one entry per ISIN per date. An ISIN is the twelve-character code that uniquely identifies a security, so this rule means you can record only one purchase lot for a given security on any given calendar date.

If your shares were received across three different dates, you add three separate entries, one for each date. Any additional entry for the same security on the same date will be rejected. The practical workflow is therefore:

1. Get the acquisition history for the transferred shares from your previous broker: the quantity, price and date of each lot.
2. Group the lots by date. If two lots share a date, combine them into a single quantity for that date, using the appropriate weighted cost, because Console will accept only one entry for that ISIN on that date.
3. Add one entry per distinct date, entering the price and quantity for that date.

This is important because a share transfer moves only the units. The buy average and date of acquisition are not carried across, so unless you enter them the position will remain a discrepancy and your tax P&L will be wrong when you eventually sell. Sourcing the figures from the previous broker’s contract notes or holding statement keeps your cost basis defensible for capital gains reporting .

What can go wrong

• “Required information to perform this action is not available.” You entered a weekend or trading holiday as the purchase date, or a date after the demat credit date. Change the date to a valid trading day on or before the credit date.
• A second entry for the same stock on the same date is rejected. This is the one-entry-per-ISIN-per-date rule. Merge same-date lots into a single quantity and cost, or split them across the actual different dates.
• The buy average has not changed yet. The recalculation takes up to 24 working hours. Check again the next working day before assuming something is wrong.
• You cannot edit an entry any more. Editing and deletion are possible only while the status is Pending. After the update, the entry is locked; if it is genuinely wrong you will need to raise a support ticket.
• The stock is inactive or a corporate action is still processing. You cannot self-correct in these cases. Follow the escalation path in how to fix a holdings discrepancy , which covers inactive stocks, CAS mismatches and raising a Console support ticket.

After the update

Once the buy average is set, verify it on your holdings screen and, if you export records, on the Console holdings report . The corrected cost basis now feeds your unrealised P&L and, when you sell, your realised gains under FIFO. If you want to understand exactly how Console will average your entries against future buys and sells, read how the buy average is calculated on Console .

See also

• How the buy average is calculated on Zerodha Console
• Why your buy average shows N/A or looks wrong
• How to fix a holdings discrepancy
• How to fix CAS discrepancies
• How to transfer shares between demat accounts
• What is an ISIN
• How to view holdings on Kite vs Console
• Understanding the Console holdings report

References

1. Zerodha Support, How to update the buy average on Console?, support.zerodha.com.
2. Zerodha Support, Editing discrepant holdings on Console, support.zerodha.com.
3. Zerodha Support, How is the buy average calculated in Console?, support.zerodha.com.
4. CDSL India, Consolidated Account Statement and demat transfers, cdslindia.com.