Couples rarely bounce an auto-debit because anyone overspent; they bounce it because each assumed the other had topped up the right account. List every mandate against the account it runs from, agree who funds that account and by when, and repeat the same top-up on the same day each month.
Start with one shared mandate list
Sit down together with last month's statements from both accounts. Write each auto-debit on one page: what it is, its amount, the date, and the account that pays. Surprises appear at once, such as an insurance premium that nobody remembers setting up.
| Mandate | Amount | Date | Paid from | Funded by |
|---|---|---|---|---|
| Home loan instalment | ₹32,000 | 5th | Account A | Partner A |
| Society maintenance | ₹3,500 | 10th | Account B | Partner B |
| School fees plan | ₹8,200 | 10th | Account B | Partner B |
| Internet plan | ₹1,099 | 12th | Account A | Partner A |
All amounts are invented for the example. Account A carries ₹32,000 + ₹1,099 = ₹33,099. Account B carries ₹3,500 + ₹8,200 = ₹11,700.
Why do mandates bounce even when the household can afford them?
Because the money sits in the wrong place. Say Partner A is paid on the 7th, two days after the loan instalment on the 5th. The household has plenty, but Account A holds ₹14,000 on the 5th, and the ₹32,000 debit fails. The problem is date order, not affordability.
Set a standing top-up day
- Choose a day after both salaries land, for example the 8th.
- Transfer from the account with spare money to cover the other's mandates for the whole month.
- Move any mandate that runs before that day to a later date, if the biller allows.
- Keep a small cushion in each account so a charge that rises does not trip the debit.
How do we talk about it without a fight?
- Keep it factual: which debit, which account, which date.
- Treat the fix as a system, not a blame game. The system had a gap.
- Agree who watches the balance on the 4th, the day before the biggest debit.
- Decide in advance who covers a bounce charge if there is one.
Where does SpendixAI fit?
Each import is tied to the account you choose, so statements from both accounts can sit in one workspace and show which debits belong where. It is a single personal workspace, not a shared team space, so decide which of you keeps it and share the monthly view by screenshot or export. Pro includes bills and budgets if you want upcoming payments listed alongside balances.
What about debits one of you has forgotten?
Old mandates are the quiet risk: a gym plan from two years ago, an app on a spouse's card, a premium set up by a parent. Scan three months of both statements together and circle anything neither of you can explain in ten seconds. Cancel what is unused, and ask the biller for confirmation in writing that the mandate is closed.
Also look at who is named on each mandate. If a debit runs on an account that is in only one name, the other partner may not get the alert when it fails. Forward alerts to a shared email, or agree that whoever receives one posts it in your household chat the same day.
Who sees the alerts?
Bank messages go to the account holder's phone. In a couple, the partner who is not on the account may never see a failed-debit alert. Decide where alerts get shared: a household chat is enough. A failed mandate noticed on the day is a ten-minute job; noticed a week later it may be a late charge.
A monthly household check
- Compare each account's balance on the 4th with the debits due in the next week.
- Confirm the top-up transfer happened.
- Review any failed debit together within the same week.
Useful ideas start with a clearer picture of your own spending.
Explore your reports
