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 what to do when your bank feed stops working, shows duplicates, or is missing transactions.

First stop: reconnect your bank

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 a prompt to update your login 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 or emailed code, or security questions) if prompted.

Once the connection is healthy again, 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. Go to Fund Accounting → Transactions → Bank Integration.
2. Remove the affected bank.
3. Add the bank again and re-map its accounts to the correct Aplos registers. See Bank Integration: Connecting Your Bank.

Heads up: reconnecting or re-adding a bank can bring recent history in again, including transactions you've already imported. Nothing is posted to your registers automatically, so review the list before importing:

• Hide rows you've already recorded using the eye icon (one at a time, or in bulk with Hide Selected).
• Where Aplos suggests a match to an existing register entry, accept the match instead of importing the transaction again.

Common connection problems

Your username or password isn't accepted

Log in to your bank's website directly to confirm your username and password work. Also check you picked the right institution: many banks list separate personal and business options, and choosing the wrong one causes this error.

Your bank needs you to take action

Some banks need you to do something on their side before they'll share data, such as accepting updated terms, opting into a program like e-statements, or updating your password or security questions. Log in to your bank directly, complete any prompts, then return to Aplos and reconnect.

Multi-factor authentication or security questions

If your bank asks for a code or security questions, answer each one in the Plaid window. Some banks send them one at a time, so you may need to answer several. If the prompt disappears, use Update Login to go through your credentials and verification again.

Manual refresh is temporarily unavailable

To protect the connection, the manual refresh 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

Check whether your bank is supported at plaid.com/institutions. If it isn't, you can import a file of transactions downloaded from your bank instead. See Importing Transactions into an Account Register.

File import is also the way to bring in older transactions. How far back your bank shares history varies: often about 90 days, and up to 24 months for some banks.

No transactions after connecting

• Give a new connection a few minutes to finish loading. Data pulls in the background.
• Check that the connection shows as active on your connections screen.
• Check that you're viewing the bank account you expect, and that it's mapped to the correct Aplos register.
• If you have more than one login at the same bank, make sure the account was added under the right login. See Bank Integration: Connecting Your Bank.

Duplicate or missing transactions

• Duplicates: when Aplos suggests a match to an existing register entry, accept the match to link them, or hide the bank transaction if it's already recorded. For transfers between your own accounts or credit card payments, import from one side only.
• A few transactions missing: check they weren't hidden or imported to a different register. Search your transactions with the Hidden filter turned on to find them.
• Entered in the register first? Matching happens when you review bank transactions and isn't re-checked afterwards. For the cleanest results, import or match from Bank Integration first. See Importing and Hiding Transactions with Bank Integration.

Common Questions

Still stuck?

If none of the above resolves it, reach out to our team. Having your bank's name, the affected account, and a screenshot of the error banner ready will speed things up.