BankSync

Troubleshooting Guide

Solutions for common issues with bank connections, feed syncs, integrations, and data problems.

4 min read

On this page

This guide helps you diagnose and resolve common issues you might encounter when using BankSync. Find solutions for connection problems, sync failures, and data issues.

Connection Issues

Problems connecting to banks or integrations

Sync Failures

Feeds not running or completing properly

Integration Errors

Issues writing to Notion, Sheets, or Airtable

Data Problems

Missing, duplicate, or incorrect data

Fixing a bank that stopped syncing by reconnecting it.

Bank Connection Issues#

Connection Troubleshooting Steps

  1. Check your bank's status

    Visit your bank's website or app to ensure online banking is working. Some banks have maintenance windows.

  2. Verify your credentials

    Ensure you're using the correct username and password. Try logging into your bank directly first.

  3. Complete any MFA challenges

    Look for text messages, emails, or app notifications for verification codes.

  4. Reconnect if needed

    Go to the Banks tab, find the connection, and click Reconnect to re-authenticate.

Security Lockouts

Multiple failed connection attempts may trigger your bank's security measures. Wait 15-30 minutes before trying again, or contact your bank to unlock your account.

Common Bank Connection Errors#

Invalid Credentials

Double-check username/password. Some banks use different credentials for third-party access.

Session Timeout

The connection took too long. Try again when you have a stable internet connection.

MFA Required

Complete the multi-factor authentication challenge sent to your phone or email.

Bank Maintenance

Your bank may be performing maintenance. Try again in a few hours.

For region-specific connection guidance, see the guides for US banks, Canadian banks, and Australian banks.

Feed Sync Issues#

Feed Troubleshooting Steps

  1. Check feed status

    Go to your Feeds tab and look for error indicators. Red status means a failure occurred.

  2. Review the sync job

    Click on the feed, then "History", to see the latest sync job details and any error messages with remediation suggestions.

  3. Verify bank connection

    Ensure the underlying bank connection is healthy in the Banks tab. Expired bank connections are the most common cause of failed syncs.

  4. Check the integration

    Verify the integration the feed writes to (Google Sheets, Excel, Notion, Airtable, or a database) is still authorized in the Integrations tab.

  5. Retry the sync

    Use the Run Now button to manually trigger a new sync attempt. Retried jobs restart failed chunks only, and deduplication prevents already-written rows from being duplicated.

Pro Tip

If a feed consistently fails, try pausing it, waiting a few minutes, then resuming. This can clear transient errors.
The Feed History dialog showing a completed run with transaction counts, a failed run whose error reads that the bank connection needs to be re-authorized, and an in-progress run, with full run details for the selected job.
The feed History dialog is the first place to look: every run, its counts, and the exact error.

Scheduled syncs not running#

If a scheduled feed doesn't seem to fire when you expect:

  • Check the time zone: schedule times are interpreted in UTC, not your local time. A "06:00" schedule runs at 06:00 UTC.
  • Check the cadence is allowed on your plan: Free and Starter plans support Weekly schedules, Standard adds Daily, and Hourly requires Professional or above. See Setting Up Scheduled Feeds.
  • Check the toggle: the "Automatically sync periodically" toggle in the Schedule tab must be on.

Integration Issues#

Notion#

Permission Denied

Re-authorize Notion and ensure BankSync has access to the target database.

Database Not Found

The database may have been deleted or moved. Select a new database in your feed's Destination tab.

Property Mismatch

Database properties changed. Update your field mappings to match the current schema.

Rate Limited

Notion API limits reached. The sync will automatically retry later.

Google Sheets#

Access Revoked

Re-authorize Google Sheets in the Integrations tab to restore access.

Sheet Not Found

The spreadsheet may have been deleted or unshared. Select a new sheet in your feed's Destination tab.

Row Limit Reached

Google Sheets has a 10 million cell limit. Archive old data or use a new sheet.

Quota Exceeded

Google API quota reached. Syncs will resume automatically.

Airtable#

Token Expired

Re-authorize Airtable in the Integrations tab.

Base Not Found

The base may have been deleted. Select a different base for your feed.

Field Type Mismatch

Field types changed in Airtable. Update your mappings to match.

Record Limit

Free Airtable plans have record limits. Upgrade or archive old data.

Data Issues#

Missing Data#

Resolving Missing Data

  1. Check the sync window

    Run Sync Now first: it picks up anything new since the last run. If data is still missing, use "Start from the beginning" in the Sync Now dialog to re-fetch all available history (note: this can create duplicate rows for data that was already written).

  2. Verify bank data

    Check if the transactions appear in your bank's online portal. A bank can take a day or more to post new transactions.

  3. Consider pending transactions

    If the feed filters pending transactions, recent purchases appear only once they post. Australian (CDR) bank connections filter pending transactions by default because their IDs can change when the transaction posts.

  4. Review filters and mappings

    Check whether enrichment rules or feed settings exclude certain transactions, and confirm the relevant fields are mapped to columns.

Duplicate Data#

How Deduplication Works

BankSync keys every record on the unique ID issued by the bank provider and remembers what it has already written for each account, so re-runs, retries, and overlapping date ranges don't duplicate rows. Duplicates usually mean two feeds are writing the same account to the same place (each feed deduplicates independently), or the bank changed its transaction IDs.

Fixing Duplicates

  1. Check for duplicate feeds

    Ensure only one feed syncs a given bank account into each sheet, table, or database.

  2. Clean up your sheet or table

    Remove the duplicate rows manually or with filters.

  3. Reset the feed

    If duplicates persist, you may need to delete the feed and create a new one.

Getting More Help#

Contact Support

If you've tried these troubleshooting steps and still need help, contact our support team with details about your issue, including any error messages and steps to reproduce the problem.

Contact Support

Related guides#

Use this page with your AI assistant

Every BankSync doc is available as plain Markdown for agents and LLMs.

View as MarkdownOpen in ChatGPTOpen in Claude