DEV Community

Cover image for Why Your Budgeting App Keeps Asking You to Reconnect Your Bank
pedro acosta
pedro acosta

Posted on Originally published at finsight.it.com

Why Your Budgeting App Keeps Asking You to Reconnect Your Bank

If you use any budgeting app that connects to your bank, you have seen it. A banner says your connection needs attention, your balances stop updating, and a budget you trusted yesterday is suddenly wrong.

I build FinSight for a living, so I see this from the inside. Here is the plain version: it breaks for a handful of reasons, most are not your fault, and only some of them need anything from you.

First, how the connection works

Most budgeting apps do not talk to your bank directly. They use a connection provider, and for FinSight that provider is Plaid. You sign in to your bank through Plaid, your bank approves it, and the app gets permission to read your accounts. The app never sees your bank password.

That middle layer is why things break in ways that look random. There are three parties, your bank, the provider and the app, and any of them can cause a problem.

Reason 1: Your bank wants you to log in again

This is the most common one. The message usually reads something like "login required."

It happens when your bank asks you to verify yourself again. A password change, a new phone for two-factor codes, or a routine security review at the bank can all trigger it. The old permission stops working until you approve it again.

What to do: reconnect. In FinSight, go to Dashboard, then Accounts, find the bank, and click Reconnect. Your bank will ask you to sign in again. It takes a minute and your history stays put.

Reason 2: The bank is down

Banks have outages and maintenance windows. Sometimes their systems just do not answer for a while.

This one is not yours to fix. If the message says your bank is temporarily unavailable, do nothing. FinSight keeps retrying on its own until the bank comes back. Reconnecting will not help, because the problem is on the other side.

Reason 3: The connection is about to expire

Some connections have an expiry. When one is close, you will see a warning before anything breaks. Reconnect early and syncing never stops.

Reason 4: Access was removed

Sometimes access to a bank is removed, usually from the bank's side. You can reconnect to restore it. If you removed it on purpose, disconnect it instead.

Reason 5: You are not actually broken, it is just slow

Before you reconnect anything, check the timing. New transactions usually show up within a few hours, because banks send them on their own schedule. Pending transactions can take one to three business days to settle.

If something looks missing, wait a day and run a manual sync from the Accounts page. A lot of "broken sync" is a bank that has not posted the charge yet.

A short checklist

  • Read the banner. It names the reason.
  • If it says login required, reconnect.
  • If it says the bank is unavailable, leave it alone.
  • If a transaction is missing, wait a day, then sync manually.
  • If it still fails after reconnecting, email support with the bank name. A human should look at that.

Will I lose my data if I disconnect?

No. In FinSight, disconnecting a bank stops future syncing and archives its accounts, but every transaction already synced stays. You can reconnect the same bank later.

The honest part

Bank sync is the least reliable piece of any budgeting app, mine included. No app fully controls it, and anyone who tells you theirs never breaks is selling something. What you can fairly ask for is a clear message about what happened, one button to fix the ones you can fix, and no lost history. That is what I tried to build.

If you want a budget that does not depend on perfect sync, a monthly system built around your lowest month helps. I wrote about that in how to budget with irregular income. And if a sync problem is what made you start looking at other apps, read why YNAB feels hard before you switch, and try a subscription audit with a fresh file while you are at it.

Originally published at finsight.it.com.

Top comments (0)