When a bank connection made through a service like Plaid stops working, the link between your app and your bank has broken somewhere, and the quickest repair is usually to reconnect from inside the app that asked for it. If that keeps failing, you can fill the gap another way: download a statement for the missing days and import it, which needs no live connection at all.
Why would a bank link break?
We cannot see inside the service or your bank, so these are things to check rather than diagnoses.
- The bank asked you to confirm your identity again, or you changed your login details, so the old link no longer works.
- The bank was down for maintenance when the app tried to refresh.
- Your phone or browser blocked a pop-up the connection needs.
- The account was closed, renamed, or replaced with a new one.
- A VPN or a poor network interrupted the connection midway.
Steps to try, in order
- Check the bank's own site or app. If you cannot log in there, the problem is with your bank, not the link.
- Turn off any VPN and allow pop-ups for the app.
- Remove the broken connection inside the app and add it again.
- Update the app, restart the phone, and retry once.
- Contact the app's support, giving the bank name, the date it stopped and the exact message.
How big is the gap, and how do I fill it?
Say the link broke on the 9th and you only repaired it on the 24th. The missing stretch is the 9th to the 24th, and that stretch is the only part you need to recover. Download a statement for exactly those dates from your bank, in the format it offers, and bring it in.
| Item | Value |
|---|---|
| Last day the link worked | 9 March |
| First day after repair | 24 March |
| Days to recover | 9 March to 23 March, 15 days |
| Statement to download | 10 March to 23 March, or a few days either side |
Downloading a few extra days on each side is safer than too few, as long as you can spot the overlap afterwards.
How do I avoid counting things twice?
Overlap is the real risk. If your statement starts on 8 March but the link already captured the 8th and 9th, those rows will appear twice. Before importing, sort by date and compare the first rows of the new file with the last rows you already have. SpendixAI flags possible duplicate imports and keeps an import history with the status of every file, so you can see what went in and when.
Or work without a link at all
SpendixAI does not use a bank connection. It takes bank or card statements as PDF, CSV or Excel, and never asks for net-banking logins. You choose the account before importing so each row keeps its account, and you review the rows before saving. The trade-off is plain: nothing updates until you upload, and it does not read SMS, so cash needs to be added by hand.
What if your bank is not in India?
That approach is built around India and INR, so we would not promise it for statements from banks elsewhere. If you hold foreign accounts, check first with a single file and see whether the rows read correctly.
One last practical point: when a link has been down for weeks, import the statement in month-sized pieces rather than one giant file. A month at a time makes the overlap check quicker, and if one file fails you lose only one month of effort.
Checklist for next time
- Note the date a link stops working.
- Keep your latest statements downloaded.
- Reconnect from inside the official app only.
- Check overlap before importing.
- Compare your closing balance with the bank's figure after every repair.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

