When a SIP debit fails or bounces

At some point a SIP instalment will not go through, and the first reaction is often to worry that something has broken. Usually nothing has. A missed debit is one of the most ordinary things that can happen to a SIP, and it is easily put right. Here is what a failed instalment does — and, importantly, what it does not do.

Why a debit fails

An SIP is collected through a bank mandate — a standing instruction that lets the fund draw your instalment automatically. A debit fails when that instruction cannot be carried out, most often because:

• the balance was too low on the day — by far the commonest reason, and usually just a timing mismatch with when your income lands;
• the mandate is not active — for example a new one that has not finished registering, or an old one left behind after a bank change;
• the amount exceeds the mandate limit, or the account has been frozen or closed.

The first of these is why the SIP date is worth choosing for cashflow — setting it a few days after your income arrives keeps the balance there when the debit runs.

What happens to that instalment

The missed instalment is simply not collected, and no units are bought for that month. That is the whole of it: the month is skipped, not queued. You do not owe a back-payment, nothing doubles up next month, and one failure does not cancel the SIP. The instruction stays in place and tries again on the next scheduled date.

Is there a penalty?

The fund house does not charge a penalty for a missed SIP instalment — a SIP is not a loan or a committed contract, so there is nothing to fine. Your bank, separately, may apply a failed-mandate or return charge under your account terms, the same way a bounced auto-debit is treated. That is a matter between you and your bank, so if you want the exact figure, check your account’s schedule of charges.

What it does to the units you already hold

Nothing. A failed debit touches only the instalment that did not go through; the units you have already accumulated stay invested and remain yours, entirely unaffected. A missed month does not reach back into what you already own — it simply means one fewer instalment was added.

When repeated failures stop the SIP

One miss is nothing; a run of them is different. Many fund houses cancel a SIP after a set number of consecutive failed debits — often around three — because the mandate is then treated as inactive. If that happens, nothing is lost: your existing units are untouched, and you resume by registering a fresh SIP or mandate. It is an administrative reset, not a loss, but it is worth avoiding because re-registering a mandate takes a few working days.

How to get back on track

Three practical fixes cover almost every case. Keep the account funded a few days before the SIP date, so a timing mismatch cannot cause a miss. If your bank account has changed, register the new mandate before the old one lapses, so there is no gap. And in a genuinely tight month, it is cleaner to pause the SIP deliberately than to let a debit fail — pausing keeps the arrangement tidy and avoids a string of failures cancelling it.

The bottom line

A single failed SIP debit is a skipped month, not a crisis: no penalty from the fund, no effect on the units you already hold, and no need for a back-payment. Keep the money in the account on the day, fix the mandate promptly if your bank changes, and pause on purpose rather than by accident, and a missed debit stays the small thing it is.