Why the blocked amount is unchanged after modifying an IPO bid
The blocked amount staying unchanged after an IPO bid modification is a recurring source of confusion, and in almost every case it is one of two things: the new UPI mandate has not yet been approved, or the modified bid does not require more money than is already blocked. The block is a lien placed on your bank account by the UPI ASBA mandate, valued at the bid quantity times the upper end of the price band , and it changes only when a new mandate raising that value is authorised. A modification that lowers the bid, or one whose new value is already covered, leaves the existing block in place.
This article explains the mandate mechanics behind the behaviour: how the block is valued at the maximum payable amount at the cut-off , why an upward modification blocks only the incremental rise rather than a fresh full amount, why a downward modification does not free funds until the basis of allotment , and the approval step that catches most people who see no change. It is written for the investor who modified a bid on Zerodha Kite or Console and is trying to read their bank balance against their expectation.
Conflict-of-interest disclosure. This article 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 article does not carry it and earns no referral commission from the procedure described here.
How the block is valued: the maximum at cut-off
When you place an IPO bid through UPI ASBA, the self-certified syndicate bank does not transfer money to the issuer. It places a lien on your savings account for the amount you could be required to pay. That amount is the bid quantity times the highest applicable price. For a cut-off bid, where you accept whatever price is discovered within the band, the highest applicable price is the upper end of the price band, so the mandate blocks quantity times the upper-band price. This is the maximum payable value.
The consequence is that the block is sized to the worst-case payment, not to the final issue price, which is unknown at bidding time. If the issue later prices below the upper band, the allotment consideration is lower than the block, and the surplus is released after allotment. So even before any modification, the block often looks larger than the eventual payment. This is by design, not an error.
Why an upward modification adds only the increment
Exchanges allow an IPO application to be modified up to three times, during market hours on trading days, until the issue’s closing day. When you increase the bid, Kite or Console sends a fresh UPI mandate to your app for the new, higher maximum value. The bank does not stack a second full block on top of the first. It blocks only the difference between the new required value and what is already held.
The mechanics are clearest in numbers. Suppose you bid 2 lots and the bank blocks Rs 30,000. You then modify to 3 lots, which requires Rs 45,000. The new mandate is for Rs 45,000, but once you approve it the bank blocks an additional Rs 15,000, taking the total held to Rs 45,000, not to Rs 75,000. The incremental design means an upward modification that you have approved should show your total block rising to the new value, with only the gap newly deducted from available balance.
If after an upward modification your block has not risen at all, the new mandate is almost certainly still pending. The increase does not take effect until you authorise the new mandate with your UPI PIN.
The approval step that catches most people
A bid modification is not complete when Kite shows it submitted. An upward modification generates a new mandate request that lands in your UPI app, and the block only updates when you approve that request with your UPI PIN. Until then, the bank continues to hold the old block, so the displayed blocked amount is unchanged. This is the most common reason an investor sees no change after modifying.
The fix is to open your UPI app, find the pending mandate request for the IPO, and authorise it. The deadline to approve any IPO mandate, including a modification mandate, is 5 pm on the issue’s closing day. A modification mandate approved after that cutoff does not take effect, and if the original mandate was never approved either, the application can be left void. Mandate requests can also be delayed by UPI-app or bank-server load, especially near the deadline, which overlaps with the failure mode covered in how to fix a UPI mandate timeout for an IPO . If no mandate appears in your app at all after an upward modification, the practical recovery is to delete the application and reapply with a fresh bid while the window is still open.
When no new mandate is needed at all
The second reason the block does not change is that your modification did not raise the required value above what is already blocked. Two situations produce this.
The first is a downward modification. If you reduce the quantity or the price, the new maximum payable value is lower than the existing block, so no new mandate is generated; there is nothing more to block. The block stays at the earlier, higher figure.
The second is a modification whose new value still sits at or below the existing block. If you had bid at the upper band and then modify to a different price within the band without increasing the quantity, the maximum payable value may not exceed what is already held, so again no new mandate is sent. In both situations the system correctly leaves the block unchanged, because the existing lien already covers the highest amount you could owe.
Why a reduction does not release funds mid-issue
Investors who lower a bid often expect the surplus to be freed immediately. It is not. Under the UPI ASBA design, the lien for an application is released or reduced only at defined points: at the basis of allotment, or if the application is deleted, or if the whole issue is withdrawn. A mid-issue downward modification does not trigger a partial release. The mandate continues to hold the earlier, higher amount through the bidding window, and the excess is unblocked after allotment on the standard timeline, T+1 release reflected in the bank by T+2, the same path as a non-allotment, set out in how to release blocked IPO funds after non-allotment .
This is the counterpart to the upward case: blocks ratchet up on approval during the issue, but they only ratchet down at allotment. For the period in between, the held amount reflects the high-water mark of your bid, not your latest reduced bid.
How this fits the IPO lifecycle
The block behaviour is one stage in the broader sequence from bid to listing. After the mandate is approved and the funds are blocked, the bid is forwarded to the exchange, the issue closes, the registrar finalises the basis of allotment, and only then are blocks converted to debits for allottees or released for non-allottees and surpluses. The full sequence is described in what happens after an IPO bid is placed . Reading the blocked amount in isolation, without the lifecycle, is what makes a perfectly normal unchanged block look like a fault.
Quick diagnosis
To diagnose an unchanged block after a modification, first establish whether the bid was raised or lowered. If you raised it, open your UPI app and look for a pending mandate; an unchanged block almost always means it is waiting for your approval, which must happen before 5 pm on the closing day. If you lowered it, or kept the required value at or below the existing block, the unchanged block is expected, and the surplus will release after allotment. If you raised the bid, approved a mandate, and the block still has not risen by the next day, check the bid and mandate status on the registrar or NSE portal, and raise a ticket with Zerodha support quoting the bid reference and mandate reference.
References
- SEBI (Issue of Capital and Disclosure Requirements) Regulations, 2018, Regulation 62 on basis of allotment and release of blocked amounts.
- SEBI, FAQs on UPI in the public issue process, July 2019 (mandate approval cutoff at 5 pm on the closing day; block at maximum payable value).
- NPCI UPI 2.0 one-time mandate (block) specification for public issues, incremental block on modification.
- SEBI circular SEBI/HO/CFD/TPD1/CIR/P/2023/140 dated 9 August 2023, T+3 listing timeline governing the post-close release.
See also
- UPI ASBA
- UPI mandate
- ASBA
- How to modify an IPO bid on Zerodha
- How to modify or withdraw an IPO bid on Zerodha
- How to withdraw an IPO bid on Zerodha
- What happens after an IPO bid is placed
- How to release blocked IPO funds after non-allotment
- How to fix a UPI mandate timeout for an IPO
- How to handle an IPO UPI mandate timeout
- How to avoid an IPO rejection on Kite
- How to improve IPO allotment chances
- Cut-off price
- IPO price band
- IPO lot size
- Basis of allotment
- IPO oversubscription allotment
- Self-certified syndicate bank
- Registrar to an issue
- IPO process in India
- How to apply for an IPO on Kite web
- How to apply at cut-off price for an IPO on Zerodha
- Zerodha Console
- Kite by Zerodha
- Zerodha
- How to create a ticket with Zerodha
External references
- Zerodha support: modified IPO bid, blocked amount in bank has not changed
- Zerodha support: how to modify IPO bids
- Zerodha support: IPO mandates
- SEBI: FAQs on UPI in the public issue process
- NPCI: UPI product overview
WebNotes Editorial Team prepares factual reference articles based on publicly available regulatory documents and broker disclosures. WebNotes is not affiliated with Zerodha Broking Limited. Mandate and block mechanics are subject to change; verify current behaviour at support.zerodha.com before acting.