SIP Deducted but Units Not Allotted? Check These 5 Things

Your SIP money has left the bank. You open your investment app, refresh the portfolio, and the new units are missing. Should you wait, pay again, or raise a complaint? Start by finding out which part of the transaction is incomplete.

This guide covers routine SIP purchases in existing Indian mutual fund schemes. The NAV example is specifically for an ordinary domestic equity fund. Liquid funds, overnight funds, international schemes, NFOs and exchange-traded ETF purchases need their own applicable rules. Sources were checked on 15 September 2026. The checklist and sample message are practical suggestions, not a diagnosis of your account.

Why money can leave your bank before units appear

Think of a SIP as several records that need to agree, not one event. Your bank records a debit. The investment channel records an order. The fund needs the payment and a valid application. Finally, the allotment must be visible in the relevant statement or holding record.

This gap is not speculation: HDFC Mutual Fund's payment-mode disclosure explicitly explains that an investor's account can be debited before the scheme receives the money within its cut-off time. Different payment settlement cycles can delay allotment. That explains one possible reason, not the cause of every missing SIP.

A useful support request identifies the missing link. 'Where is my SIP?' is understandable. 'Please trace payment reference X to order Y and confirm its allotment or rejection status' gives the support team something specific to investigate.

The five checks to make now

1. Match the debit to the exact SIP instalment

Open the bank statement and the order history together. Note the amount, debit date, payment reference, scheme name and order number. If you run several SIPs for the same amount, do not identify the transaction by amount alone. Look for a reversal credit too, but ask the bank or platform to confirm the reference before deciding that a similar credit is your refund.

Save the relevant entries and status screenshots. Keep the full records privately; use masked account details in an initial support message. Do not post your PAN, folio number or bank statement in a public comment asking strangers to investigate.

2. Read the order status, not just the portfolio total

Open the individual instalment. Copy the exact status and any expected completion date. Labels such as 'payment received', 'processing', 'allotted' and 'rejected' describe different things, and their meaning can vary by platform. If there is a rejection message, ask for the specific reason and required action instead of assuming that every delay is a bank problem.

If the bank debit has no corresponding order, contact the platform and bank with the payment reference. If an order exists but its status is unclear, ask the platform to identify whether payment reconciliation, application processing or confirmation is outstanding. Do not change your KYC or register another mandate merely as an experiment.

3. Check the fund's record independently

Look for the AMC's confirmation email or SMS and request a recent transaction statement from the fund house or its registrar and transfer agent, usually called the RTA. Select a date range that includes the instalment and check the correct folio, plan and option. A summary balance alone is less useful than the individual transaction entry.

AMFI's CAS download page links to CAMS, KFintech and MFCentral for consolidated statements. A detailed CAS can help you reconcile transactions across funds. Check the statement period and generation date; an older statement cannot establish what happened to today's payment.

For CAMS-serviced funds, the CAMS Transaction Details service provides transaction history. CAMS also warns that its statement may not contain complete demat information. If you hold units in demat form, check with your depository participant, or DP, rather than treating an RTA statement as conclusive.

If the appropriate holding record confirms the allotment but your app does not, send that evidence to the app's support team and ask them to reconcile the display. If the records disagree, ask for a written explanation. A missing dashboard entry and a missing allotment are different problems.

4. Ask when the fund received the money and which NAV applies

For the domestic equity-fund example below, the key requirements are receipt of the purchase application and funds available to the scheme before the applicable cut-off. The fund-credit cut-off is 3:00 p.m. IST. Your bank's debit time is not a substitute for the scheme's receipt time. See SEBI's March 2026 Master Circular, paragraphs 9.4.2 and 9.4.3, pages 163-165.

Ask support for the fund-realisation date and time, the application's acceptance timestamp and the applied NAV date. AMFI's NAV explanation confirms that the funds-realisation rule includes SIPs regardless of investment amount. It is not a special rule only for large lump-sum purchases.

5. Trace a rejected transaction through to its refund

If support confirms rejection, ask four questions: What was rejected? Who is returning the payment? When was the refund initiated? What reference and expected bank-credit date can you use to track it? Keep following the same ticket until the response reconciles with your bank statement.

Do not assume that 'refund initiated' means the bank has already credited the money. Equally, do not use an internet promise of 'every failed SIP is refunded in seven days' as a substitute for the payment channel's actual terms. Ask for the timeline applicable to your case, and escalate when it is missed or no traceable explanation is provided.

A worked example: Friday debit, Monday NAV

This is a hypothetical example, not a customer case. Assume a valid SIP order in a domestic equity fund is accepted on Friday morning. Friday and Monday are scheme business days, the weekend is not, there are no intervening holidays, and the money remains available once received.

This illustration applies AMFI's published cut-off examples. If the money arrived before Friday's cut-off with the valid order already accepted, Friday's closing NAV would apply instead. A later confirmation message does not, by itself, tell you which NAV date was used. Read the transaction record.

How long should you wait before contacting support?

You can raise a query as soon as a debit is unexplained. For a clearly acknowledged order still inside its published processing window, note the expected date and check again. If that date passes, the status contradicts the bank record, or nobody can trace the payment, follow up in writing. These are practical follow-up triggers, not a statutory waiting period.

HDFC Mutual Fund's SIP payment disclosure gives different indicative timing for NACH and other auto-debit routes, and explicitly says actual timing can differ. That is why this article does not give one guaranteed allotment deadline for every bank and platform.

Do not import an NFO refund deadline into an ordinary failed-SIP complaint. They are different transaction types. If your investment is actually an NFO, use its offer documents and allotment schedule rather than the ongoing-SIP example above.

A support message you can copy and adapt

Use the official support channel inside your investment platform or on the AMC's website. The following is an original template. Replace every placeholder, include only facts you can document, and provide sensitive identifiers only through a verified secure channel when required.

Attach the relevant evidence, not an unfiltered folder of financial documents. If support asks for another document, ask which fact it establishes. Keep a short log of ticket numbers, response dates and promises so you do not have to reconstruct the story during an escalation.

If the transaction remains unresolved

1. Start with the entity handling the problem. Ask the platform to trace its order and payment; ask the AMC or its RTA for the fund-side record. For a bank payment or refund-credit issue, raise a trace request with the bank too.
2. Use the formal grievance channel. If routine support does not resolve the issue, write to the relevant entity's designated grievance contact with the earlier ticket and supporting evidence. Obtain the address from its official website.
3. Use the appropriate escalation route. For an unresolved securities-market complaint within SEBI's scope, consider SCORES after approaching the concerned entity. Do not assume that SCORES handles a purely banking complaint.

The SCORES portal directs investors to approach the concerned entity first. Its current FAQs, question 20, say the entity must resolve the complaint and upload its Action Taken Report within 21 calendar days of receiving the complaint on SCORES. If dissatisfied with that report, the investor can request review within 15 calendar days of the report. These are complaint-handling timelines, not a guaranteed refund date or a required delay before your first support query.

SCORES facilitates grievance redressal; it does not adjudicate disputes or guarantee compensation. Follow the portal's current instructions and preserve your evidence. A documented transaction trail is more useful than an unsupported allegation about who caused the delay.

Before you pay again or stop the SIP

Do not make a duplicate purchase solely to remove uncertainty from an app screen. First establish whether the original instalment is pending, allotted or rejected. Any replacement investment should be a deliberate decision after you know what happened to the first payment.

For the basics of how the arrangement works, see our SIP guide. Once the transaction is reconciled, the SIP calculator can help with planning assumptions. It cannot locate a missing payment, access your folio or predict actual returns.

This is educational guidance, not personalised investment or legal advice. No AMC, RTA or regulator endorses this article. The cited sources explain the underlying rules and services; only the relevant providers can confirm what happened to your transaction. Report a correction through our editorial policy.