OL 209 QuickBooks Error Fix and Statement Import

OL-209 means QuickBooks Desktop sent a request to your bank and could not read what came back. Either the bank's server never answered properly, or your computer could not save the reply to its temporary folder. That makes it the one common OL code where your own PC is a real suspect, so check free disk space and the temp folder before you spend an hour on the phone with the bank. If the month has to close today, import the PDF statement as a Web Connect file and fix the connection afterward.

Most pages ranking for this code repeat the same generic list they use for every OL number. This guide sorts the fixes by where the fault sits, tells you which result points at the bank and which at your machine, and shows how to keep the books moving while the download is broken.

What does error OL-209 mean in QuickBooks?

It means the Direct Connect download failed after QuickBooks sent the request, at the point where it reads the bank's response. The wording attached to the code, which Quicken publishes for its OL-209-B variant, is "unable to read a response. The response may not have been returned or there may have been inadequate disk space or a disk error when saving the response to a temporary file." QuickBooks Desktop Pro, Premier and Enterprise use the same OFX download path, so the same two halves apply: the bank's side and your disk.

Intuit's help article "Fix OL and OLSU Bank Feeds errors in QuickBooks Desktop" covers the whole family and lists five broad causes: a problem with your bank, your internet connection, the bank accounts in your company file, an incompatible file from the bank, or an unsupported version of QuickBooks. For OL-209 the first and the local disk are the usual culprits.

Is the problem the bank or my computer?

Answer that first, because the fixes do not overlap. Run Send/Receive for a second bank in the same company file. If that bank downloads and the failing one does not, the fault is almost certainly on the failing bank's side. If every bank fails with OL-209, look at your own machine, starting with the disk and the temp folder, then the firewall and security software.

Quicken Community threads on OL-209-B show the bank-side pattern clearly: users of one institution, for example a Citi card or a brokerage, all hit the code in the same week while their other accounts kept working, and it cleared when the institution fixed its server. If your QuickBooks file only has one connected bank, the test company check below gives you the same answer.

How do I fix error OL-209 in QuickBooks Desktop?

Back up the company file, then work through the steps in order and stop as soon as a download succeeds. The first two cost nothing and rule out the local causes that make OL-209 different from its neighbors. The rest follow Intuit's order for the OL family.

1. Free up disk space and clear the temp folder

Check the free space on the drive that holds Windows and the drive that holds the company file. If either is nearly full, clear space before anything else. Then close QuickBooks, open the Windows temporary folder (type %temp% in the Run box) and delete what Windows lets you delete. A full or damaged temp folder is the literal cause the error message names, and it is the cheapest one to fix.

2. Sign in on the bank's website

Log in through a browser. If the bank shows a new agreement, a security prompt or a password change, finish it there, because QuickBooks cannot display that screen and the bank may refuse to answer the download until you do. Intuit puts this check before every other fix.

3. Check the firewall and security software

Intuit asks you to confirm the Windows firewall is not blocking QuickBooks. Antivirus tools that scan or quarantine temporary files can also interrupt the save step, which fits OL-209 closely. If you recently installed or updated security software, add QuickBooks to its exceptions and try again.

4. Download in a test company file

Create a new company with Express Start, set up Bank Feeds for the same account and download. If the test file works, your real company file has a problem with that account record, so go to step 5. If the test file fails with OL-209 too, the problem is the bank or the connection itself, so skip to step 6.

5. Refresh or rebuild the account connection

Turn off online banking on inactive accounts in the file, then refresh the connection on the failing account. If that does not work, Intuit's heavier fix is to create a copy of the account, connect the copy, and merge it with the original. Do this only with a fresh backup, and only after the test company check pointed at your file.

6. Send the bank your Bank Feeds log

When the test company also fails, the fix belongs to the bank. Intuit tells you to contact the bank's support with a copy of the Bank Feeds log and ask them to escalate the case through Intuit's OFX connectivity channel. Ask for the online banking or Direct Connect team, not general support, and write down the case number.

If you are on QuickBooks Desktop 2023 or older, none of this will help. Intuit discontinued the 2023 releases on May 31, 2026, including bank feeds and Web Connect. The discontinued QuickBooks Desktop page explains what still imports on those versions, and the answer is IIF.

OL-209 compared with the other OL errors

The OL codes look alike in the error box, but they point at different stages of the download. Knowing which one you have saves you from fixes that cannot work.

Keep the books moving while the error is open

A bank escalation can take days, and month-end does not wait. The download path that OL-209 blocks is Direct Connect. Web Connect is a separate route: you import a .qbo file through File, Utilities, Import, Web Connect Files, and QuickBooks never talks to the bank's server. Intuit's own article notes that QuickBooks only opens downloaded transactions in a .qbo file, which is exactly what a converted statement gives you.

So convert the bank's PDF statement to a .qbo file, import it into the existing account, and reconcile against the statement's ending balance. Upload the statement in our PDF bank statement to QuickBooks Desktop converter, check that the rows match the balance, and download the file. On Desktop 2023 or older, download IIF instead and import it through File, Utilities, Import, IIF Files.

Two cautions. First, import only the dates the connection missed. A converted file carries its own transaction IDs, not the bank's, so if the connection comes back and downloads the same days, QuickBooks will not recognize them as duplicates and you will have to match or delete them by hand. Second, keep each bank in its own account. If you also want an independent check that every statement line made it into the ledger, dedicated reconciliation software can match bank lines against the books once the month is in.

What does waiting cost?

Nothing, if the error clears tomorrow. If it does not, the cost is the close. A busy operating account can run to a hundred or more lines a month, and typing them from the statement takes an hour or more, plus the typos you then chase at reconciliation. A converted statement takes a few minutes. Our plans start at $49 a month for 50 documents, and you can convert one statement without an account to see the result first. Firms with several clients on the same failing bank can use the bank feed not working page to plan a catch-up across all of them.

Frequently asked questions

What causes QuickBooks error OL-209?

QuickBooks could not read the bank's response to a download request. Either the bank's server did not return a usable reply, or the computer could not save the reply to its temporary folder because of low disk space, a disk error or security software. Unsupported QuickBooks releases and problems with the account record in the company file can trigger it too.

How do I fix OL-209 in QuickBooks Desktop?

Free up disk space and clear the Windows temp folder, sign in on the bank's website to clear any prompt, and check the firewall. Then download in a test company file. If the test file works, refresh or rebuild the account connection. If it fails, send the bank your Bank Feeds log and ask them to escalate it.

Is OL-209 a QuickBooks or a Quicken error?

Both products use it. QuickBooks Desktop shows OL-209 in Bank Feeds, and Intuit's OL and OLSU article covers it. Quicken shows OL-209-B during One Step Update and documents its own steps. If there is a letter after the number, you are almost certainly in Quicken.

Does OL-209 happen in QuickBooks Online?

No. OL codes belong to QuickBooks Desktop and Quicken. QuickBooks Online has its own connection errors, and its manual upload under Bank transactions, Link account, Upload from file accepts a .qbo file if you need to fill a gap.

Can I import transactions while OL-209 is still open?

Yes. A Web Connect import through File, Utilities, Import, Web Connect Files does not use the Direct Connect download that OL-209 blocks. Convert the bank's PDF statement to .qbo, import it into the existing account, and reconcile to the statement. Import only the dates the connection missed.