How an IPO application works in India: a simple step-by-step guide

An IPO application is not just a form. It is a chain of issue terms, an applicant identity, a demat account, a payment authorisation and a later allotment result. Keeping those pieces together is the easiest way to avoid an incorrect total.

1. Read the issue before you count accounts

Start with the current issue information, not a forwarded message. Note the issuer, exchange, issue type, price band, lot size, category rules, opening date, closing date and any published post-issue schedule. The price band is not the same thing as a market price, and the closing time or category rules can be issue-specific.

2. Calculate the planned application amount

For a simple planning estimate, multiply the chosen bid price by the number of shares in one lot and then by the number of lots. Keep the planned amount separate from the final amount debited: allotment may be partial, unsuccessful or subject to issue-specific rules.

3. Submit through a permitted channel

Applications may be submitted using an authorised broker, bank or other permitted intermediary. The payment path can involve ASBA or a UPI mandate. The account holder, PAN and demat details should match the application requirements; never assume that another person's payment identity can be substituted.

SEBI explains that ASBA blocks the application amount while it remains in the investor's account until allotment, and that UPI applications involve bidding, a block request and a later debit or unblocking based on allocation. See the SEBI ASBA explainer ↗ and current issue documents for the applicable rules.

4. Approve the mandate carefully

Before approving a UPI or bank request, compare the displayed applicant, IPO name, amount and payment account with your planned record. A successful application screen is not the same as a successful allotment. Save the application reference or acknowledgement when available.

• Applicant name and PAN are correct.
• The demat account label is the account actually used.
• The amount matches the selected lots and bid price.
• The payment account belongs to the permitted applicant flow.
• The approval status and application reference are recorded.

5. Record each application as its own relationship

If one person uses two demat accounts, create two account-level application records. Do not combine them because the allotment, bank source, refund state and result can differ. A clean identifier is:

That is the model IPOxCards uses. The account label stays visible when an admin reviews applications, allotments, bank funding or listing results.

6. Close the loop after the issue closes

When the issue closes, update the application state instead of overwriting the original row. Later mark the result as allotted, not allotted or pending, and then reconcile any debit or unblocking. The dates published by the exchange or registrar should be treated as the source of truth; if a date is not published, show “awaiting publication” rather than inventing a date.

Common mistakes to avoid

• Treating an approved mandate as an allotment.
• Counting a person instead of the exact demat account.
• Using a copied closing date without checking the current issue notice.
• Calling the planned application amount a final debit.
• Deleting an unsuccessful application instead of retaining its audit history.
• Publishing sensitive PAN, bank or demat information in a public tracker.

Quick answers

Next: map the same process across multiple demat accounts →