When QuickBooks Desktop bank feed is not working, new transactions may stop downloading, the Bank Feeds Center may show an error, the bank connection may repeatedly ask for credentials, or the account may remain connected without receiving current transactions.
The problem does not always originate inside the QuickBooks company file. A bank can change its connection method, require additional authentication, experience a service interruption, or change information used by the financial institution directory. Internet connectivity, inactive accounts with online banking enabled, company-file issues, unsupported QuickBooks versions, and incompatible bank files can also affect Bank Feeds.
QuickBooks Desktop currently supports Direct Connect and Web Connect, depending on the financial institution. Direct Connect communicates with the bank’s server, while Web Connect uses a .QBO file downloaded from the bank and imported into QuickBooks. This guide explains why QuickBooks bank feed is not updating, how to identify the source of the problem, and how to refresh or reconnect the affected account without unnecessarily changing your company data.
Why Is QuickBooks Desktop Bank Feed Not Working?
The symptom you see can help identify where to start troubleshooting.
| What you see | What to check first |
| No new transactions download | Bank connection, bank service, account connection |
| Bank Feed update returns an error | Error code, bank connection, internet |
| Bank asks for credentials repeatedly | Bank login, connection method, authentication |
| One account is not updating | Account-specific Bank Feed setup |
| Several accounts stop updating | Bank service, connection method, QuickBooks environment |
| Bank changed its online banking system | Reconnect Bank Feeds |
| .QBO file will not import | File format or bank-generated file |
| Inactive account still has a lightning bolt | Bank Feed connection remains active |
| Bank works outside QuickBooks but not inside it | QuickBooks connection or company-file issue |
| Problem appears only in one company file | Company-file configuration or data issue |
Intuit identifies bank-side problems, internet problems, inactive bank accounts, outdated financial-institution information, incompatible bank files, and unsupported QuickBooks versions among the possible causes of Bank Feed errors.
- Bank Connection Changed: Banks can change the way they provide online banking services. Intuit specifically notes that a financial institution may change between Web Connect and Direct Connect or require customers to reconnect using an updated connection. If transactions stopped downloading after your bank changed its online banking process, reconnecting the account may be more appropriate than repeatedly selecting Download Transactions.
- Bank Website Requires Attention: A bank may require you to accept a new agreement, complete a security verification, respond to an alert, or update account information before third-party connections can continue. Intuit recommends signing in to the bank’s website outside QuickBooks and checking for alerts or messages before troubleshooting the QuickBooks connection further.
- Incorrect or Outdated Connection Information: If your bank username, password, or other required information has changed, the existing Bank Feed connection may no longer authenticate correctly. The same can happen when a bank changes the connection service that QuickBooks uses.
- Inactive Account Still Connected to Bank Feeds: An inactive QuickBooks account can still have online banking enabled. Intuit specifically identifies this configuration as one possible source of Bank Feed errors.
- Financial Institutions Directory Needs Updating: QuickBooks Desktop uses a Financial Institutions Directory, commonly referred to as FiDir, for bank-feed information. Intuit recommends keeping this information current when troubleshooting Bank Feed problems.
- Company File or Account Issue: If Bank Feeds works in a test company but fails in your normal company file, the problem may be specific to the company file or one of its bank accounts. Intuit also recommends backing up the company file before performing troubleshooting that changes Bank Feed configuration.
How to Fix QuickBooks Desktop Bank Feed Not Working
Work through these checks in order. Start with the least disruptive tests before disconnecting and reconnecting the bank account.
1. Check Your Bank’s Website First
Before changing anything in QuickBooks, sign in to your bank’s website directly. Look for:
- Security alerts
- New terms or agreements
- Messages requiring confirmation
- Password or username changes
- Maintenance notices
- Problems accessing the account
- Changes to online banking services
Intuit recommends signing in to the bank outside QuickBooks and checking for alerts before troubleshooting Bank Feed errors. If the bank itself will not let you sign in, resolve that issue with the financial institution first. If you can sign in normally and there are no messages requiring action, continue with QuickBooks troubleshooting.
What the result means:
- Bank website also has problems: Focus on the financial institution first.
- Bank website works normally: Continue checking the QuickBooks connection.
- Bank says its online banking method changed: Reconnect Bank Feeds using the appropriate connection method.
2. Back Up the QuickBooks Company File
Before making significant changes to Bank Feed connections, create a backup of your company file. This is particularly important if you are preparing to deactivate Bank Feeds, rebuild a company file, or make other configuration changes.
Intuit specifically advises backing up the company file before proceeding with Bank Feed troubleshooting and before certain account changes. Also review any transactions already downloaded into the Bank Feeds Center. You do not want to troubleshoot a connection while overlooking transactions that are waiting to be matched or added.
3. Try to Download the Transactions Again
If the bank connection appears normal, manually initiate another download. In QuickBooks Desktop for Windows:
- Open the company file.
- Select Banking.
- Select Bank Feeds.
- Open Bank Feeds Center.
- Select the affected bank account.
- Select Download Transactions.
Intuit’s current instructions use the Bank Feeds Center to download transactions through the connected bank account. If the download succeeds, review the downloaded transactions before matching or adding them. If the same error returns, note the exact error code or message instead of repeatedly retrying.
4. Check Whether Your Bank Requires a New Connection
One of the most important causes of QuickBooks bank feed not updating is a change in the connection between the bank and QuickBooks. Intuit currently documents cases where certain financial institutions require customers to reconnect using a specified bank connection. The required connection can vary by financial institution and account type.
If your bank recently changed its online banking system or you received a notice about reconnecting, follow the bank-specific reconnection instructions. Do not randomly select another financial institution with a similar name. The correct connection can depend on the bank and the type of account being connected.
5. Check for Inactive Accounts With Bank Feeds Enabled
An inactive account can sometimes retain an online banking connection. To check for this in QuickBooks Desktop for Windows:
- Go to Company.
- Select Chart of Accounts.
- Select Include Inactive.
- Look for an inactive account showing the Bank Feeds lightning bolt.
- If you find one, right-click the account.
- Select Edit Account.
- Open Bank Feed Settings.
- Select Deactivate All Online Services.
- Select OK.
- Select Save & Close.
Intuit specifically recommends checking inactive accounts with online banking enabled when troubleshooting OL and OLSU Bank Feed errors. After making the change, close and reopen the company file and confirm that the lightning bolt is no longer displayed.
6. Check the Bank Feed Connection Method
QuickBooks Desktop can use Direct Connect or Web Connect, depending on what your financial institution supports.
A. Direct Connect
With Direct Connect, QuickBooks communicates directly with the bank’s server. Some banks require special enrollment or credentials for this method.
B. Web Connect
With Web Connect, you download a .QBO file from the bank’s website and import it into QuickBooks. The current QuickBooks Desktop process is:
- Sign in to the bank website.
- Download the available transactions in .QBO format.
- In QuickBooks Desktop, select Banking.
- Select Bank Feeds.
- Select Import Web Connect Files.
- Select the .QBO file.
- Select Open.
- Choose the appropriate existing QuickBooks account when prompted.
- Continue through the import process.
- Review the transactions in the Bank Feeds Center.
If the .QBO file imports successfully but Direct Connect does not work, the issue is more likely related to the live connection rather than the QuickBooks bank account itself.
7. Check Whether the Downloaded File Is a Valid .QBO File
If your bank uses Web Connect, the file format matters. Intuit states that QuickBooks Desktop Web Connect works with .QBO files. Other formats such as QIF and QFX are not accepted as standard Web Connect files.
If your bank downloads a different file type, do not simply rename the extension and expect QuickBooks to accept it. Instead, check whether the bank provides a QuickBooks-compatible .QBO download option. If the bank provides a .QBO file but QuickBooks cannot read it, Intuit recommends testing the file and contacting the bank if the file itself appears to be incompatible.
8. Update the Financial Institutions Directory
If the bank connection is returning unexpected results, make sure the Financial Institutions Directory is current. Intuit states that the Financial Institutions Directory in QuickBooks Desktop updates automatically when you send and receive transactions through Bank Feeds.
If QuickBooks has not successfully communicated with the bank recently, the directory or bank connection information may need to refresh as part of the troubleshooting process. This is one reason a successful test download can be useful: it can help determine whether the issue is with the connection information or with the specific company file.
9. Check the Intuit Account and Primary Admin
Some Bank Feed connection errors are related to the Intuit Account associated with the company file. For example, Intuit documents error 7500 as a situation that can occur when there is a permissions issue with the Intuit Account. Bank Feed downloads may require the primary admin associated with the company file.
To check the primary admin:
- Open the QuickBooks company file.
- Press Ctrl + 1 or F2.
- Find the Primary admin email in the Intuit Account Information section.
- Go to Company.
- Select My Company.
- Check the user ID shown in the upper-right area.
Intuit says the user ID should correspond to the primary admin associated with the company file when performing the affected Bank Feed download. If the wrong user is signed in, sign out and sign back in with the appropriate Intuit Account credentials.
10. Test the Bank Feed in a New Company File
If the bank connection still fails, testing it in a new company file can help determine whether the issue is specific to your existing company file. Intuit’s current troubleshooting process recommends creating a test company and setting up Bank Feeds for the affected account.
The diagnostic result is important:
If the same bank error appears in the test company: The problem may involve the bank, bank connection, or financial institution service.
If the test company downloads transactions successfully: The problem may be specific to the original company file or account configuration. This comparison is more useful than immediately rebuilding or recreating the original company file.
11. Disconnect and Reconnect the Bank Feed
If the connection itself appears damaged or outdated, disconnecting and setting up Bank Feeds again can refresh the connection. Before disconnecting, review the pending transactions. Intuit recommends matching or deleting pending downloaded transactions before deactivating Bank Feeds. For QuickBooks Desktop for Windows:
- Go to Lists.
- Select Chart of Accounts.
- Right-click the affected account.
- Select Edit Account.
- Open Bank Feed Settings.
- Select Deactivate All Online Services.
- Select OK.
- Select Save & Close.
Afterward, set up Bank Feeds again using the appropriate connection method. Intuit’s current setup process allows you to reconnect through Banking → Bank Feeds → Set Up Bank Feed for an Account.
Do not disconnect the account simply because transactions are delayed by a few hours. Use this step after checking the bank, connection method, credentials, and other less disruptive causes.
QuickBooks Bank Feed Not Updating After a Bank Password Change
If you recently changed your bank password, the existing QuickBooks connection may need updated credentials. Start by signing in directly to the bank website with the new credentials. If the bank login works, return to QuickBooks and update or reconnect the Bank Feed connection as appropriate.
For some connection changes, Intuit’s documented workflow is to disconnect the existing Bank Feed and set it up again with the updated information. If the bank uses additional authentication, such as a one-time password or external browser authentication, complete the bank’s verification process when prompted. Intuit notes that some financial institutions require authentication outside QuickBooks during reconnection.
QuickBooks Desktop Bank Feed Stopped Working Suddenly
When Bank Feeds worked previously and suddenly stopped, determine what changed immediately before the problem began. Consider:
- Did the bank change its website?
- Did the bank change its online banking service?
- Did the bank require a new security agreement?
- Did the bank require reconnection?
- Did you change your banking password?
- Did a QuickBooks update occur?
- Did the problem begin with only one account?
- Are other bank accounts still downloading?
- Is the bank website working normally?
Intuit specifically lists changes in bank service offerings, bank-server problems, inactive online-banking accounts, outdated financial-institution information, and unsupported QuickBooks versions as possible causes of Bank Feed errors. The timing of the failure can therefore provide an important clue.
QuickBooks Bank Feed Not Updating One Account
If several connected accounts continue downloading transactions but one account does not, focus on the affected account rather than rebuilding all Bank Feeds. Check:
- Whether the account is active.
- Whether Bank Feeds is still enabled.
- Whether the bank connection is correct.
- Whether the account’s bank credentials changed.
- Whether the bank requires reconnection.
- Whether there are pending downloaded transactions.
- Whether the account works through a test company.
QuickBooks allows individual bank accounts to be connected and managed separately, so an issue affecting one account does not automatically mean that every Bank Feed connection is broken.
QuickBooks Desktop Bank Feed Not Working With Direct Connect
Direct Connect communicates directly with the financial institution’s server. Some banks require enrollment or specific credentials before the connection can work. If Direct Connect suddenly stops working:
- Sign in to the bank website first.
- Check for bank alerts.
- Confirm the bank has not changed its online banking service.
- Check whether your financial institution requires reconnection.
- Confirm the correct QuickBooks bank connection is selected.
- Check whether the Intuit Account user is correct.
- Test the connection in a test company if necessary.
If the bank has stopped supporting the particular Direct Connect service, changing QuickBooks settings alone will not restore that discontinued bank service.
QuickBooks Desktop Bank Feed Not Working With Web Connect
Web Connect is different because transactions are downloaded from the bank website as a .QBO file and then imported into QuickBooks Desktop. If Web Connect stops working, check:
- Whether the bank still offers .QBO downloads.
- Whether the downloaded file actually has the .QBO extension.
- Whether you selected the correct QuickBooks account during import.
- Whether the bank generated the file correctly.
- Whether the same file imports into a test company.
If QuickBooks cannot read a valid .QBO file, Intuit recommends investigating the file and bank connection rather than converting it into an unsupported format.
QuickBooks Bank Feed Error Codes
QuickBooks Desktop can display different OL and OLSU error codes when Bank Feeds encounters connection or authentication problems. Intuit’s current troubleshooting documentation includes codes such as:
- OLSU-1011
- OLSU-1013
- OLSU-1014
- OLSU-1016
- OL-202
- OL-203
- OL-205
- OL-206
- OL-209
- OL-221
- OL-231
- OL-232
- OL-249
- OL-301
- OL-332
- OL-334
- OL-392
- OL-393
The exact troubleshooting path depends on the error and the connection method. When an error code appears, record it before closing the message. The code can help distinguish a bank-service problem from an account, connection, or QuickBooks environment problem.
When QuickBooks Bank Feeds Still Do Not Update
If Bank Feeds remains stuck after the earlier checks, avoid repeatedly disconnecting and reconnecting the same account. At this point, compare the results:
| Test | What the result suggests |
| Bank website fails | Bank-side access problem |
| Bank website works, QuickBooks fails | QuickBooks connection or configuration |
| Other QuickBooks bank accounts work | Account-specific issue |
| Test company also fails | Bank/connection problem is more likely |
| Test company works | Original company file may need investigation |
| .QBO file imports successfully | Web Connect file is usable |
| .QBO file cannot be read | Bank-generated file or compatibility issue |
| Error occurs only under one Intuit user | Account permissions may be involved |
This type of comparison prevents unnecessary changes to a working company file. If the issue appears to involve company-file data, Intuit’s documented troubleshooting includes verifying and rebuilding the company file after creating a backup.
How to Prevent QuickBooks Desktop Bank Feed Problems
Bank Feed issues cannot always be prevented because financial institutions can change their online banking services or experience service interruptions. However, several practices can make future problems easier to diagnose.
- Keep QuickBooks Desktop Supported: Intuit identifies unsupported QuickBooks versions as one possible reason for Bank Feed errors. Keeping your supported QuickBooks environment current can reduce compatibility-related problems.
- Monitor Bank Notifications: If your bank announces a change to its online banking service or asks you to reconnect a third-party application, address the notification before Bank Feeds stops downloading.
- Keep Company File Backups: Create regular backups, especially before making changes to Bank Feed connections. Intuit specifically recommends a backup before several Bank Feed troubleshooting procedures.
- Review Pending Transactions: Before disconnecting a Bank Feed account, review downloaded transactions. Intuit advises matching or deleting pending transactions before deactivating Bank Feeds.
- Record Bank Connection Details: Know whether each bank account uses Direct Connect or Web Connect. This makes it easier to identify whether a problem involves the live connection or the .QBO download process.
- Avoid Unnecessary Reconnection: If transactions are temporarily delayed, do not immediately deactivate the account. First check the bank website, error message, connection method, and service status.
Conclusion
When QuickBooks Desktop bank feed is not working, the cause can range from a bank-side alert or connection change to an inactive account, outdated financial-institution information, incorrect credentials, an incompatible .QBO file, or an issue specific to the company file. Start by checking the bank website and recording any error message. Then verify the affected account, connection method, Intuit Account permissions, and Financial Institutions Directory. If the connection still fails, testing Bank Feeds in a new company file can help determine whether the problem is specific to the original company.
For QuickBooks bank feed not updating, reconnecting the account can be effective when the bank has changed its connection requirements, but it should not be the first step in every situation. Review pending transactions and create a backup before disconnecting Bank Feeds. The most useful troubleshooting approach is to isolate the problem: bank vs. QuickBooks connection vs. individual account vs. company file. Once that distinction is clear, you can apply the appropriate solution without making unnecessary changes to the rest of your bookkeeping setup.
FAQs of QuickBooks Desktop Bank Feed Not Working:
A Bank Feed may stop updating because of a bank connection problem, bank-side alert, changed online banking service, inactive QuickBooks account, internet issue, outdated financial-institution information, unsupported QuickBooks version, or a company-file problem. Intuit lists these among the possible causes of OL and OLSU Bank Feed errors.
Open the company file, go to Banking → Bank Feeds → Bank Feeds Center, select the affected account, and choose Download Transactions. If the connection continues to fail, check the bank website, connection method, credentials, and any displayed error code before reconnecting the account.
Your financial institution may have changed its connection service or may require a new connection for security or technical reasons. Intuit currently documents banks that require reconnection and provides bank-specific connection selections in Bank Feed setup.
Yes. Web Connect allows you to download a .QBO file from your bank and import it into QuickBooks Desktop. The current process uses Banking → Bank Feeds → Import Web Connect Files. QuickBooks Desktop does not natively use QIF or QFX files as Web Connect files.
Not immediately. First check the bank website, alerts, connection method, credentials, account status, and error message. If you do disconnect Bank Feeds, review pending downloaded transactions and create a company-file backup first. Intuit recommends matching or deleting pending transactions before deactivating Bank Feeds.
If the same bank connection works in a test company but fails in your normal company file, the problem may be specific to the original company file or its bank-account configuration. Intuit uses a test-company download as part of its troubleshooting process to help distinguish bank or connection problems from company-file issues.
An unexpected Bank Feed error can have several causes, including bank-server problems, connection issues, account configuration, incompatible bank files, or Intuit Account permissions. For example, Intuit documents error 7500 as potentially related to an Intuit Account permission issue and says the primary admin credentials may be required for the Bank Feed download.
