When an autopay fails, first find out which payment it was and when its due date is. Then pay it manually if the due date is near, and check every other mandate on the same account for the same problem. A failed debit is rarely a one-off: the cause, such as low balance, an expired card or a changed limit, often affects several payments.
What do I check first?
- The name of the merchant or lender and the amount.
- The due date or the date after which the service stops or a late charge could apply. This is the figure that sets your deadline.
- The reason shown in the message or the app. Common ones are insufficient balance, expired card, a transaction limit, or a mandate that has ended.
- Whether the payment will be retried, and on what date. Some services retry, some do not.
Do this on the day you notice the failure. Waiting for the retry is risky when the due date is close.
How do I pay it now?
Use the merchant's own app or page and pay manually by the method you trust. Keep the confirmation. If it is a loan EMI or credit card bill, note the date you paid against the due date, because that is the record you will want if a late charge appears. If you are unsure whether a late charge applies, ask the lender; do not guess.
Which other mandates should I re-check?
Look at the account or card the failed payment came from. Everything that debits from it shares the same risk.
| What to check | Why it matters | Your note |
|---|---|---|
| Balance on debit dates | Several autopays on the 1st to 5th can exceed a small balance | Lowest balance this month |
| Card expiry date | A replaced card may leave old mandates unlinked | Expiry month and year |
| UPI autopay limits | A mandate can fail if the amount rose above its limit | Limit versus current price |
| Mandates ended or paused | Some end on a date you set when you created them | End dates found |
| Linked mobile number | Alerts and approvals go to it | Current or not |
How do I record the due-date risk?
Add one line for each affected payment in a small log: payment, due date, amount, how it failed, what you did and the date. Add a column for status such as Paid manually, Retry expected, or Still open. That simple log becomes your evidence if a late fee or a service lapse needs to be raised later. It also shows you, after two or three entries, if the real cause is a recurring low balance at month start.
How do I stop it happening again?
- Keep a buffer in the account that carries the autopays, enough to cover the largest recurring debit plus a little.
- Move the biggest or most important autopays, such as EMIs and insurance, away from the days when your salary is not yet credited.
- Set reminders three days before the dates that matter most.
- Review the mandate list once a quarter and close ones you no longer use.
Using your records to confirm nothing was missed
At month end, compare the list of payments you expected with the statement. Anything expected that is missing is a failed or skipped payment. If you import statements into SpendixAI, grouping recurring payments under their categories makes the missing lines easier to spot, and the Possible duplicate charges report can also flag a payment that was retried and charged twice. A manual list does the same job if you keep it up to date.
When to contact the bank or merchant
If a payment failed but money left your account, or you were charged twice, raise it with the merchant first and then the bank, with your dated log and screenshots. Rules on fees and timelines differ by product, so read the terms of the loan or card, or ask the lender directly.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

