QuickBooks Desktop Bank Feed Broken? What to Use Instead

When a QuickBooks Desktop bank feed breaks, you can still get transactions in without typing them. Fix the connection with Intuit’s steps for OL and OLSU errors,¹ import a Web Connect (.qbo) file from your bank’s website,² or convert PDF statements into IIF or .qbo files with a statement converter. None of these requires moving to QuickBooks Online.

Bank feeds in Desktop are failing across the board. Banks are discontinuing Web Connect file downloads. Intuit is sunsetting older Desktop versions. Users who relied on automatic transaction import now face manual data entry or migration pressure. Tools that convert PDF bank statements into Desktop import files remove the typing without leaving the platform.

This guide explains why bank feeds stopped working, compares the tools that restore automatic import, and walks through the setup process. For background on Desktop’s advantages, see our QuickBooks Desktop hub.

Table of Contents

• What to Use When the Bank Feed Breaks
• Why QuickBooks Desktop Bank Feeds Stopped Working
  • Banks Discontinuing Web Connect
  • Intuit Version Sunsetting
  • The Migration Push
• When the Client Banks at a Credit Union
• Your Import Options Without Bank Feeds
• Tools That Convert Statements for Desktop
• How to Import Bank Statements to QuickBooks Desktop
• Common Import Problems and Solutions
• Should You Migrate to QuickBooks Online Instead?
• FAQs

What to Use When the Bank Feed Breaks

There are four ways to keep a QuickBooks Desktop bank account current when the bank connection stops working. Which one fits depends on what the bank still gives you: a working connection, a Web Connect download, or only PDF statements. The table compares them.

Which one to try first:

1. If Desktop shows an OL or OLSU error code, work through Intuit’s fix for that code first.¹
2. If the fix fails, look in your bank’s website for a QuickBooks or Web Connect download and import that file.
3. If the bank offers only PDF statements, or you are catching up on past months, run the statements through a converter and import the IIF or .qbo file it produces.

Conto is one such converter, built for bookkeeping firms. You upload the client’s statements and check images; Conto does not log in to the bank. It checks the extracted transactions against the balances printed on the statement and exports IIF, .qbo or Excel files for Desktop. The bank statement converter comparison covers DocuClipper, MoneyThumb and the others.

Why QuickBooks Desktop Bank Feeds Stopped Working

Bank feeds in QuickBooks Desktop are failing because banks are discontinuing Web Connect file support, Intuit is sunsetting older Desktop versions, and the company is actively pushing users toward QuickBooks Online’s direct bank connections.

The failures manifest in several ways. Connection errors with codes like OL-301, OL-393, or OLSU-1013 appear when attempting to download transactions. Some users see “Bank feeds are no longer supported for your version” messages. Others find that their bank simply stopped offering the download option.¹

Banks Discontinuing Web Connect

Major banks have stopped providing QuickBooks-compatible download files. Bank of America is a notable example. As one QuickBooks Community user reported: “BofA does NOT provide QB Webconnect files (QBO files)” despite QuickBooks indicating the connection should work.⁴

The bank previously offered QBO file downloads but discontinued the feature. Users contacting both Intuit and Bank of America get bounced between support teams, each claiming the issue belongs to the other party.

Wells Fargo still supports Web Connect downloads through their business banking portal, but availability varies by account type.² Chase, Capital One, and regional banks have mixed support. The trend is toward discontinuation as banks focus on direct API connections that work with cloud software but not Desktop.

Intuit Version Sunsetting

Intuit used to follow a strict three-year sunset policy. Desktop 2023 lost bank feed support in May 2026.³ On a discontinued version the software continues functioning for local bookkeeping, but online services including bank feeds stop working.

Desktop 2024 was due to follow in May 2027, but Intuit dropped the three-year lifecycle and says the 2024 release has no sunset deadline.⁵ Users on 2023 or earlier, or without an active subscription, still face complete loss of automatic import.

QuickBooks Desktop Enterprise operates under different terms with no announced end date, making it a more stable choice for firms committed to the Desktop platform.

The Migration Push

Intuit stopped selling QuickBooks Desktop Pro and Premier to new customers in September 2024. Existing users can keep renewing Desktop 2024, but the message is clear: Intuit wants users on QuickBooks Online.⁶

QBO generates recurring subscription revenue. Cloud infrastructure is easier for Intuit to maintain. Bank API integrations work directly with QBO’s architecture.

This business strategy explains the declining investment in Desktop bank connectivity. Intuit has little incentive to negotiate new Web Connect agreements with banks when QBO already connects to banks directly.

When the Client Banks at a Credit Union

Credit union accounts lose the bank feed more often than accounts at large banks. Logan Graf, a CPA who writes about practice operations, put it in two posts on X: “He just landed a new bookkeeping client. Make sure every bank account the client uses is with a local credit union.” Then: “No extra user access, bank feed breaks every month.”⁷

The “no extra user access” part is the hard one. Most credit unions give an outside bookkeeper no read-only login, so you work from the client’s own login or from the statements the client sends you. Three habits keep a credit union client workable:

1. Ask for a read-only login at the start. Call the credit union with the client and ask what options exist. Some will issue a second login or send statements to you on request, even when they do not advertise it. If the answer is no, price the engagement for the extra hour of statement chasing each month.
2. Put statement delivery in the engagement letter. The client sends or uploads PDF statements within five business days of month-end. If the statement is late, the reconciliation is late, and the client knows why.
3. Reconcile to the PDF statement, not the feed. Treat the statement as the record. Reconcile the register to the statement balance every month, so a feed that stopped without an error shows up within 30 days instead of at year-end.

When the credit union gives you only PDFs, use the statement converter path above.

Your Import Options Without Bank Feeds

QuickBooks Desktop supports three transaction import paths: IIF files (most powerful, handles all transaction types), Web Connect files (when banks still offer them), and CSV/Excel import (limited but simple) - with IIF being the preferred format for bulk imports from external tools.

IIF (Intuit Interchange Format)

IIF files are Desktop’s native batch import format. They handle:

• Checks, deposits, and transfers
• Invoices and credit memos
• Bills and bill payments
• Journal entries with splits
• Classes and job assignments

The format is tab-delimited text with strict header requirements. A single formatting error can cause silent import failures. Most accountants use tools that generate IIF files automatically rather than building them by hand.

Web Connect (QBO, QFX, OFX)

When banks offer them, Web Connect files import through Banking → Bank Feeds → Import Web Connect File. The transactions appear in the bank feed queue for matching and categorization.

Current availability is spotty. Many banks show the option in their interface but return errors when attempting download. Test your specific bank before relying on this method. If your bank only provides PDFs, a PDF to QBO converter can generate Web Connect files from those statements.

CSV and Excel

Native Excel import (File → Utilities → Import → Excel Files) works for basic transactions and list updates. The field mapping is limited and cannot handle split transactions or complex data types effectively.

Third-party importers like Transaction Pro provide better Excel-to-Desktop capabilities than native import.

For more on Desktop import capabilities, see our QuickBooks Desktop hub.

Tools That Convert Statements for Desktop

A statement converter reads the PDF and writes an IIF or .qbo file. DocuClipper, MoneyThumb, ProperConvert and Conto all do this. They differ in which files they write and how they charge. Our bank statement converter comparison sets them side by side, with each vendor’s pricing model and a link to its pricing page.

Transaction Pro and SaasAnt are importers, not converters. They take data you already have in Excel or CSV and import it to Desktop with more field mapping than the built-in import, including splits and classes.⁸ You still need a converter, or your own typing, to get the data off the PDF.

Conto also reads check images. A bank statement shows a check’s number and amount, and the check image shows the payee. Conto reads the payee from each check image and matches the check to its cleared line on the statement, so the payee is on the transaction before you export.

How to Import Bank Statements to QuickBooks Desktop

To import bank statements into QuickBooks Desktop, download statements as PDF from your bank, upload to a converter tool to generate IIF or Web Connect files, then import via File → Utilities → Import → IIF Files or Banking → Bank Feeds → Import Web Connect File.

Step 1: Download PDF statements from your bank

Log into your bank’s online portal and download statements in PDF format. Most banks retain 12-24 months of statements. Download all statements for the period you need to import.

Step 2: Upload to your converter tool

Open DocuClipper, MoneyThumb, Conto, or your chosen tool. Upload the PDF files. Most tools accept batch uploads for multiple statements.

Step 3: Review extracted transactions

The tool displays extracted transactions for review. Check for:

• Missing or incorrect dates
• Truncated payee names
• Split transactions that may need attention
• Any flagged low-confidence extractions

Step 4: Assign account codes (if applicable)

Some tools allow category or account assignment before export. Match transactions to your Desktop chart of accounts at this stage to minimize post-import work.

Step 5: Download the import file

Export in your preferred format:

• IIF files for maximum transaction type support
• Web Connect (QBO) files if your workflow uses bank feed matching
• CSV for simpler transactions or when IIF gives errors

Step 6: Import into QuickBooks Desktop

For IIF files:

1. Ensure QuickBooks is in single-user mode
2. Go to File → Utilities → Import → IIF Files
3. Select your file and click Open
4. Review the import log for errors

For Web Connect files:

1. Go to Banking → Bank Feeds → Import Web Connect File
2. Select your downloaded file
3. Map to the appropriate bank account
4. Review transactions in the bank feed center

Step 7: Reconcile and verify

After import, reconcile the bank account normally. Verify transaction totals match the statement. Address any duplicate or missing transactions.

Common Import Problems and Solutions

The most common QuickBooks Desktop import errors include “account not found” (fix: pre-create accounts with exact names), “invalid date format” (fix: match MM/DD/YYYY), and “duplicate transaction” warnings (fix: check import date ranges against existing entries).

Account name mismatches

IIF imports require exact account name matches including capitalization, spaces, and punctuation. “Office Supplies” and “Office supplies” are different accounts to the import process.

Solution: Before importing, review the IIF file in a text editor. Compare account names against your Desktop Chart of Accounts (Ctrl + A). Fix mismatches either in the source file or by creating matching accounts in Desktop.

Date format errors

QuickBooks expects dates in MM/DD/YYYY format. International date formats or text dates cause import failures.

Solution: Most converter tools format dates correctly by default. If you’re editing files manually or using Excel, ensure date columns are formatted as MM/DD/YYYY before export.

Duplicate transactions

Importing overlapping date ranges creates duplicate transactions. Desktop doesn’t automatically detect duplicates during import.

Solution: Before importing, check the last imported date in your register. Only import transactions after that date. Some converter tools include duplicate detection, but verification is your responsibility.

“QuickBooks is unable to verify the Financial Institution”

This error appears when importing Web Connect files with unrecognized bank identifiers. AutoEntry and some other tools use default bank IDs that may trigger this warning.

Solution: Accept the default bank ID suggestion. The transactions will import normally even if the bank branding appears incorrect. This is cosmetic and doesn’t affect data accuracy.

Silent import failures

IIF files with formatting errors often fail without clear error messages. Transactions simply don’t appear after import.

Solution: After every import, verify the expected transactions appear in the register. If transactions are missing, check the import log at File → Utilities → Import → IIF Files → View Log. Common causes include missing headers, incorrect delimiters (must be tabs, not commas), and unescaped special characters.

Should You Migrate to QuickBooks Online Instead?

Migrating to QuickBooks Online makes sense if you prioritize native bank feeds and app integrations; staying on Desktop makes sense if you value instant response times, multi-window workflows, advanced reporting, and job costing - and automation tools can close the bank feed gap.

When migration makes sense:

• Remote teams needing anywhere access
• Simple bookkeeping with basic reporting needs
• Heavy reliance on app integrations (payment processors, e-commerce, CRM)
• Mobile-first workflow requirements
• Willingness to adapt to QBO’s single-window interface

When staying on Desktop makes sense:

• High transaction volume where speed matters (500+ transactions daily)
• Complex job costing and project tracking
• Multi-window workflow habits and keyboard shortcuts
• Advanced reporting requirements
• Data sovereignty preferences (local file storage)
• Enterprise users with no sunset pressure

The middle path:

Automation tools restore the key capability that QBO offers over Desktop: getting bank data in without typing. With statement-to-IIF conversion, Desktop users match QBO’s bank feed outcome without sacrificing Desktop’s performance and feature advantages.

For a broader look at Desktop’s advantages, see our QuickBooks Desktop hub.

FAQs

What can I use instead of bank feeds in QuickBooks Desktop when the bank connection breaks?

First try Intuit’s fix for the OL or OLSU error code.¹ If the connection stays broken, download a Web Connect (.qbo) file from your bank’s website² and import it into Desktop. If the bank offers only PDF statements, convert them to an IIF or .qbo file with a statement converter.

Is QuickBooks Desktop losing bank feeds permanently?

Many banks have discontinued Web Connect file downloads, and Intuit has ended bank feed support for Desktop 2023 and earlier. Third-party tools that convert PDF statements to IIF files provide a lasting workaround that doesn’t depend on bank or Intuit support.

What file format is best for importing transactions to Desktop?

IIF (Intuit Interchange Format) is the most powerful option, supporting all transaction types including splits, classes, and job assignments. Web Connect (QBO) files work for basic transactions when available. CSV/Excel imports are simplest but most limited.

How accurate are PDF bank statement converters?

Vendors publish accuracy figures for clean statements. Your clients’ scanned and credit union statements are the real test. Review the extracted transactions, and check that they tie to the statement’s opening and closing balances, before you import.

Can I use automation tools with QuickBooks Desktop Enterprise?

Yes. Enterprise supports the same IIF and Web Connect import methods as Pro and Premier. Enterprise has no announced end-of-life date, making automation investment lower risk for long-term Desktop users.

Will Intuit ever add bank feeds to QuickBooks Desktop?

Intuit has not announced plans to add direct bank feeds to Desktop. The company actively encourages migration to QuickBooks Online, which has native bank feed support. Third-party automation remains the path for Desktop users who want to stay.

Conto extracts data from bank statements and check images for QuickBooks Desktop. Upload your PDFs and get back IIF, QBO, or Excel files ready to import. Request early access and try it with your messiest client documents.