Bank Integration connects to your bank through Plaid, our secure connection provider. Most problems come down to a connection that needs re-authorizing. This guide covers the alerts you may see and how to clear them.

First stop: reconnect the connection

Banks periodically require you to re-authorize access for security. When that happens, you'll see a connection error banner on your Bank Integration screen and an Update Login prompt on the affected connection.

1. Click Update Login (or Reconnect) on the connection.
2. Re-enter your online banking credentials in the secure Plaid window.
3. Complete any multi-factor authentication (a texted/emailed code or security questions) if prompted.
4. Once the connection returns to a healthy state, your transactions resume pulling in.

Most feed problems clear up with this single step.

Still not working: remove and re-add the bank

If reconnecting doesn't refresh the feed:

1. Open Manage Connections
2. Click Delete Institution next to the affected bank.
3. Add the bank again from scratch and re-map its accounts.

⚠️ Re-adding or reconnecting a bank on the new integration can re-surface transactions you've already imported. The one-time reconnection triggers a full refresh that pulls in transactions regardless of whether they were previously imported, so duplicates may appear. To avoid importing them twice: Hide the duplicate rows using the eye icon (single, or in bulk with Hide Selected), and use Suggested Matches (next to All Transactions) to confirm matches against existing register entries instead of re-importing. Volume should settle after the initial transition; a fix for lingering duplicates is in progress.

Common connection alerts

⚠️The numbered error codes below come from Aplos's provider-level connection checks. If a code isn't shown, rely on the on-screen banner text and the reconnect steps above.

🚧 Needs verification: The numbered codes below (103, 108/109, 185, 325) predate the July 2026 Plaid-only replatform and may reflect legacy provider behavior. The rebuilt Bank Integration surfaces connection issues through error banners and connection-status UX rather than these specific numbers. Confirm which codes still appear on Plaid-only connections before relying on this section.

Invalid credentials (Error 103)

The login you entered didn't work. Log in to your bank's website directly to confirm your username and password. Also check you picked the right institution — many banks list a personal and a business option, and choosing the wrong one causes this error.

Action required at your bank (Error 108 / 109)

Your bank needs you to do something on their side before it will share data — accept updated Terms of Service, opt into a program like e-statements (108), or update your password/security questions (109). Log in to your bank directly, complete the prompts, then return to Aplos and reconnect.

Missing multi-factor authentication (Error 185)

Your bank requires MFA or security questions to link. Click the link in the alert and answer each question — banks send them one at a time, so you may need to repeat this a few times. If the alert disappears, use Update Login to walk through credentials and MFA again.

Aggregation in progress (Error 325)

After you connect, the provider needs time to establish access. This error appears if you click Retrieve Transactions before that finishes. Check Manage Institutions — once the connection status shows Active, retrieve again.

Manual refresh is temporarily disabled

To protect the connection, the manual Refresh / Sync button is rate-limited. If it's greyed out or shows a wait message, that's expected — wait for the cooldown rather than clicking repeatedly. New transactions also arrive automatically as your bank posts them.

Your bank isn't available

If you can't find your institution, it may not be supported for a direct connection.

• Confirm support at plaid.com/institutions by searching your bank's name.
• If it isn't supported, use Upload File (Manual Import) to bring transactions in from a downloaded bank file. This is also the way to import transactions older than the feed's typical 30–90 day window.

No transactions after connecting

• Confirm the connection status is Active in Manage Institutions (see aggregation, above).
• Confirm the Source account you're viewing is the one you expect and that it's mapped to the correct Target register.
• Check the Needs Input tab — coded transactions only appear as importable once required fields are complete.
• Give a first-time connection a minute or two to finish pulling; data loads in the background.

Duplicate or missing transactions

• Duplicates: Aplos flags a transaction that matches an existing register entry (same amount within five days). Accept the suggested match to link it, or Hide the bank entry if it's already recorded. Avoid importing internal transfers or credit card payments from both accounts — import from one side only.
• A few transactions missing from an otherwise good feed: confirm they weren't hidden or imported to a different register, then use Search Transactions (including the Hidden filter) to locate them.

Still stuck?

If none of the above resolves it, contact the Aplos Customer Care team. Having your institution name, the affected account, and a screenshot of the error banner ready will speed things up.