Budgeting app bank sync not working: a troubleshooting checklist before you switch apps

Understand the chain first

A bank feed has three links: your bank, an aggregator that logs in and normalises the data, and the budgeting app. Lunch Money uses Plaid; YNAB uses MX and Plaid; Monarch uses Plaid, Finicity and MX; PocketSmith names Yodlee and Plaid in North America, Salt Edge in the UK and EU, and Basiq and Mastercard in Australia. Lunch Money's help page is blunt that, being downstream, all it can do is report problems upstream.

That matters for the decision to switch: if your bank's connection through Plaid is broken, another Plaid-based app may break in the same way.

This is research from official vendor pages and help articles read on 29 October 2026, not firsthand testing. We have not connected a bank, invited a partner or run a forecast in any of these apps for this guide.

Step 1: confirm what the bank actually shows

Log in to your bank directly. If the transaction is pending there, wait: Monarch notes a pending duplicate may be a bank or merchant error, and PocketSmith says duplicates often come from pending transactions that later post with a different date or merchant name. Then check when data last arrived. Lunch Money shows three timestamps: its last successful import, Plaid's last fetch from your bank and its last fetch from Plaid. If Plaid's timestamp is old, the problem is upstream.

Step 2: refresh, then re-authorise

• Lunch Money: trigger a refresh from Overview or Accounts; if that fails, use Relink on the account; if a relink still yields nothing, create a new connection and merge it with the existing account to keep history.
• PocketSmith: Manage, Feeds, the feed's menu, then Edit authorisation; PocketSmith asks you not to remove a Plaid feed.
• YNAB: resetting the connection is its first troubleshooting step; there is a limit on how often you can reset a connection.
• Monarch: if one provider is unreliable for your bank, switch the connection to another provider on web; your history moves with it.

Step 3: handle MFA and expiring consent

Frequent prompts are often by design. YNAB says repeated passcodes or security questions do not mean the connection is broken and that you only need to authorise when you want new transactions. PocketSmith says MFA feeds only sync when you log in and enter the code, because codes change about every two minutes. Lunch Money lists jurisdictions that require renewal every 90 or 120 days and suggests checking whether your bank offers trusted devices or app passwords.

If codes never arrive, YNAB suggests confirming the phone or email on file at your bank, checking spam and notification settings, keeping the connection window open, and asking your bank whether two-factor delivery is enabled for third-party connections.

Step 4: clean up duplicates and gaps

• PocketSmith's Find duplicates tool only catches same-date matches, so check results before deleting.
• In YNAB, transactions you delete after importing cannot be imported into that account again.

Step 5: bridge the gap with a file import

While a ticket is open, import a bank file so your budget stays current. PocketSmith's procedure is specific: unlink the affected accounts (not the whole feed), Quick import the file, choose "Replace transactions on overlapping dates", then relink when the feed works. Monarch's "Prioritize CSV" replaces existing transactions between the file's first and last dates; imports cannot be undone, so test with a small file. YNAB skips transactions with identical date and amount. Lunch Money will not de-duplicate manual transactions against newly imported ones, so set an import start date when you go back to syncing.

When it really is time to switch

Switching makes sense when the same bank fails repeatedly for more than a couple of billing cycles, support confirms the issue is with the provider, and the other app reaches that bank through a different aggregator. Monarch publishes a connection status dashboard and Lunch Money a /status command in Discord, which can show whether a problem is widespread. Before switching, export your data and start the new app's trial with the problem bank first.