OLSU-1011 QuickBooks Desktop Error: Fix the Bank Feed

OLSU-1011 in QuickBooks Desktop means the bank feed setup could not finish talking to your bank, so no transactions downloaded. Intuit's own fix list starts with two quick checks: set default accounts in Edit, Preferences, Checking, and test the connection in a new company file. If the error stays, the fastest way to close the month is to skip the live connection and import the transactions as a .qbo Web Connect file, which Intuit itself suggests as the workaround.

That second part matters more than most error guides admit. OLSU-1011 is often not something you can fix from your side. When a bank changes how its accounts connect, every QuickBooks user at that bank sees the same code at the same time, and the fix arrives when the bank and Intuit sort it out. Your reconciliation deadline does not move while you wait, so this guide covers both jobs: clearing the error when it is local, and getting the transactions in when it is not.

What OLSU-1011 means in QuickBooks Desktop

OL and OLSU codes come from Bank Feeds, the part of QuickBooks Desktop that signs in to your bank and pulls transactions. OLSU errors appear during setup or reconnection. Intuit's help article "Fix OL and OLSU Bank Feeds errors in QuickBooks Desktop" groups the causes into a short list, and it is worth reading carefully because only some of them are yours to fix.

Two quotes from that article are worth holding on to. The first: "QuickBooks only opens downloaded transactions in a .qbo file extension." The second is its recommended test, which is to sign in to your bank's website, download the transactions as a .qbo file and import them. If that import works, your company file is fine and the live connection is the problem.

How do I fix error OLSU-1011 in QuickBooks Desktop?

Work through these in order. Log in as the Admin user and switch to single-user mode before you start, because several of the steps change company preferences.

1. Set default accounts in Preferences

Go to Edit, then Preferences, then Checking. On the My Preferences tab, choose a default account for each of the four options. On the Company Preferences tab, set default accounts for Create Paychecks and Pay Payroll Liabilities. Blank defaults are the most commonly reported local cause of OLSU-1011 in the QuickBooks Community, and this takes two minutes.

2. Test the connection in a new company file

Create a sample company, set up Bank Feeds for the same account and try to download. If the new file connects and your real one does not, the problem is inside your company file. If the new file fails too, the problem is between QuickBooks and the bank, and the remaining steps in your file will not change it.

3. Update the Financial Institutions Directory

QuickBooks keeps a list of banks and their connection details. If your bank changed its setup, an outdated list points QuickBooks at the old one. Update QuickBooks Desktop to the latest release, which refreshes the directory, then try the connection again.

4. Deactivate and reactivate the bank feed

Open the account in the Chart of Accounts, edit it, and on the Bank Feed Settings tab deactivate all online services. Then set the account up again. Intuit's article adds a detail that many people miss: during setup, hold the Ctrl key each time you select a button, except when you are typing information. If you have several connected accounts, turn each one off and back on to find the one that fails.

5. Merge into a fresh account

If one account keeps failing, Intuit describes creating a duplicate account with an asterisk at the end of its name, setting up the feed on that one, then merging the two. It works, but it is the most invasive step on the list. Back up the company file first.

What if the OLSU-1011 error is on the bank's side?

Then none of the steps above will clear it, and you will know because step 2 fails in a brand new company file. This is common. A long QuickBooks Community thread from Desktop Pro Plus 2024 users describes Citi card connections failing with OLSU-1011 from September 3, 2024, while Wells Fargo, American Express and Chase kept downloading normally. Support pointed at the bank; the bank said it knew of no problem. Users waited weeks.

A connection error does not stop you from importing a file. Web Connect imports run through File, Utilities, Import, Web Connect Files, and they never touch the live bank connection. So the practical question becomes where to get a .qbo file for the months you need.

• From the bank's website. Many banks offer a QuickBooks or .qbo download for recent activity. If yours does and the range covers your gap, use it.
• From a CSV. QuickBooks Desktop cannot import a bank CSV at all, so a CSV only helps if you convert it first.
• From the PDF statements. Every bank provides statements as PDFs, usually for years. When the download is missing, too short or CSV only, you can convert the PDF bank statement to a QuickBooks Desktop file and import it through Web Connect the same afternoon.

Can I still import bank transactions while OLSU-1011 is unresolved?

Yes. OLSU-1011 blocks the online Bank Feeds connection, not the Web Connect file import. Download or create a .qbo file for the period, then use File, Utilities, Import, Web Connect Files and choose the existing account when QuickBooks asks. The transactions land in Bank Feeds for review exactly as a download would, and each one carries an ID so a later download of the same period does not duplicate them.

For a credit card account, the file has to be a credit card file. If a statement converter writes a card statement as a checking account, or keeps the statement's signs where purchases are positive, the charges arrive as payments and the card balance is wrong by twice the spending. That is the problem our Citi credit card statement to QuickBooks converter was built around, and the same card-account export applies to every issuer.

How long does it take to fix OLSU-1011?

A local cause, such as blank default accounts or an inactive account with online banking on, usually clears within fifteen minutes using the steps above. A bank-side change can take days or weeks, and QuickBooks Community threads show some lasting more than a month. If the new company file test fails, plan on importing files for the current month rather than waiting for the feed.

What the workaround costs compared with waiting

Waiting feels free, but it is not. A month of activity on an active business card is often 80 to 150 transactions. Keying them by hand commonly takes half an hour or more per 60 lines once you include checking, and the month cannot close until it is done. Across a bookkeeping practice where one bank's feed is down for every client at that bank, the hours add up quickly.

On pricing, the Starter plan here is $49 a month for 50 documents, which is one statement per document. For a firm with a dozen clients at a bank whose feed is down, that is a single month's fee against a couple of days of data entry.

Related QuickBooks Desktop errors on bank imports

OLSU-1011 is a connection error. If the connection is fine and the file itself fails, you will see a different code. OL-222 on a QBO import means QuickBooks cannot parse something inside the file, usually a stray character in a payee name. "QuickBooks is unable to verify the Financial Institution information for this download" means the file is missing the bank identifier Desktop checks first, which is covered in our guide to that message. And if the feed is working but only reaches back a few months, the older history has to come from statements, as described on the bank feed not working page.

Once the transactions are in, the job is reconciliation. Firms that reconcile dozens of bank and card accounts each month sometimes move that step into dedicated account reconciliation software that matches the feed, the processor payouts and the ledger in one place. For a single company file, QuickBooks' own reconcile screen is enough.

Frequently asked questions

Is OLSU-1011 a QuickBooks Online error?

It is reported mostly in QuickBooks Desktop, where OL and OLSU codes come from the Bank Feeds setup. QuickBooks Online uses its own connection messages. The Online equivalent of the workaround is Transactions, Bank transactions, Link account, Upload from file, which accepts a .qbo file too.

Does OLSU-1011 mean my bank login is wrong?

Not usually. A wrong password produces a sign-in failure you can correct at the prompt. OLSU-1011 points to setup and connection problems: preferences, inactive accounts, firewall, an outdated version or a change on the bank's side. Sign in on the bank's website anyway to clear any alerts waiting there.

Will switching to Express mode fix OLSU-1011?

Sometimes. Community experts suggest trying the other Bank Feeds mode, Express or Classic, when the default steps fail, because the modes connect slightly differently. It is quick to test in Edit, Preferences, Checking, Company Preferences, and it changes nothing about your data.

Can I import a PDF statement directly into QuickBooks Desktop?

No. QuickBooks Desktop has no PDF statement import in any edition. The statement has to become a .qbo Web Connect file, or an IIF file on Desktop versions that no longer support Web Connect, before Desktop will read its transactions.