Quickbooky

Accounting News

Banking & Feeds

Fix QuickBooks Online banking error 324 when downloads stop

Error 324 in QuickBooks Online stops bank feeds when account details no longer match. Here is how to reconnect and keep your history.

COMMUNITY ISSUESQUICKBOOKY

QuickBooks Online users have been running into banking error 324 when transactions stop downloading from their bank. The error means QuickBooks can no longer find the bank account it is supposed to sync. The account may still be active on the bank’s side, but the link between the two systems has broken. The cause is usually a mismatch between the account details QuickBooks has on file and what the bank now shows. The fix is to restore that connection and map the updated account to the same QuickBooks account.

The usual causes of error 324

The most common trigger is a change on the bank’s side. A new account number, a replacement debit card, or a renamed account can break the match. QuickBooks is still looking for the old details, so it cannot find the account. You may only notice it when the bank feed goes quiet. The bank itself can be perfectly healthy. The connection is the problem, not your money.

A second trigger is a closed or suspended account. When the bank stops sharing data for an account, QuickBooks cannot reconnect it. If you try, the connection fails again or the error returns. The account has to be disconnected before you can move on.

Run Fix now first

The starting point is the Fix now option in the Bank transactions area. Sign in to QuickBooks Online, open the Accounting menu, and go to Bank transactions. Find the account showing error 324 and select Fix now. QuickBooks will walk you through signing in with your current bank credentials. When the bank asks which accounts to share, choose All Accounts or Consent All. Then map the updated account to your existing QuickBooks account.

Mapping is the step that protects your data. If you map to the same account, your transaction history and your categorization rules stay intact. You do not need to disconnect the account in this scenario. QuickBooks updates the stored details and resumes the feed.

When Fix now does not work

If the updated account does not appear after Fix now, the reliable fallback is to disconnect and reconnect. Find the affected account, choose Fix now, then select Disconnect. Confirm the disconnection. QuickBooks will remove the connection. Then choose Add Account, search for your bank, and sign in again with your current credentials. Select the updated account.

Here again, map the new account to the existing QuickBooks account. Do not create a new one. A new account means a new ledger entry, and your prior history stays on the old one. The goal is to reconnect to the same account, not to start over. If you accidentally create a duplicate, you will be reconciling two ledgers for the same bank account.

When the account is closed or suspended

If the underlying account is closed or suspended, none of the reconnect steps will work. The bank will not share data for an account it no longer recognizes as active. The right move is to disconnect the old account before adding a replacement. Otherwise, QuickBooks shows an error that the account is already connected.

Before you disconnect, review any pending transactions and post them. Once disconnected, the account stops syncing for good. You cannot get later transactions for that account. So clear it out first, then disconnect, then add the new account.

Habits that reduce connection errors

Community guidance points to two habits that prevent many of these errors. First, have one person handle all bank connection setup and maintenance for the company. When multiple people reconnect accounts, change permissions, or map accounts, details can fall out of sync. One owner keeps the connection stable.

Second, always select All Accounts when the bank asks which accounts to share. Even when you only use a few accounts in QuickBooks, sharing everything keeps the connection whole. It also makes future reconnects simpler, because the bank credentials line up with what QuickBooks expects.

The takeaway

Error 324 is not a sign that your bank data is lost. In most cases, a reconnect restores the feed and keeps your history intact. Run Fix now first. If that does not work, disconnect, reconnect, and map to the existing account. If the bank account is closed, disconnect it, post pending transactions, and start fresh with a new account. The key move every time is mapping to the same QuickBooks account, never a new one.

← Back to Community Issues