OL 205 QuickBooks Error and When to Import a QBO File
Convert a PDF bank statement to a QuickBooks file
Drop in a PDF statement and get a QBO (Web Connect) or IIF file you can import into QuickBooks Online or Desktop.
OL-205 in QuickBooks Desktop means the bank's server did not answer the Bank Feeds request. Intuit lists it with the codes caused by bank alerts, a bank changing its connection type or an inactive account, and Quicken files the same code under high traffic or a temporary server outage that usually clears within 24 hours. So give it one business day. If it is still there on day two, it is not an outage anymore, and a .qbo file made from the PDF statement gets the month into QuickBooks without the connection.
Most pages about this code print the same ten generic steps they publish for every OL number. The more useful question is how long to wait. A true server hiccup fixes itself overnight, while a changed bank service can sit broken for weeks, and the way to tell them apart is the calendar plus one five-minute test.
What does error OL-205 mean in QuickBooks?
OL-205 is a QuickBooks Desktop Bank Feeds code, Enterprise included, that appears when you update an account or set one up and QuickBooks gets no usable reply from the bank's OFX server. Intuit's help article on fixing OL and OLSU Bank Feeds errors groups it with OL-203 and names the likely causes: a problem at the bank, alerts on your online banking account that need acknowledging, a bank that changed its service to Web Connect or Direct Connect, an inactive account in QuickBooks that still has online banking turned on, outdated bank details in the Financial Institutions Directory, or your own internet connection.
Quicken uses the same OL code family and is blunter about it. Its support article covers OL-202, OL-204, OL-205, OL-206 and OL-207 together and says these errors come from high traffic or a temporary server outage and usually resolve themselves within 24 hours.
| Time since OL-205 first appeared | Most likely cause | What to do |
|---|---|---|
| Under 24 hours | Bank server busy or down, often at month-end or after a bank maintenance window | Try again the next business day. Check your internet connection and that QuickBooks is on its latest release. |
| 24 to 48 hours | A notice on the bank's site, an inactive account, or your company file | Clear bank alerts, turn off online banking on inactive accounts, run the test company check below. |
| More than 48 hours | The bank changed its service, its directory entry is stale, or your QuickBooks release is out of support | Ask the bank to escalate through Intuit's OFX connectivity channel. Import the month from the statement meanwhile. |
How do I fix error OL-205 in QuickBooks Desktop?
Work through these in order. The first four take a few minutes each and are all on your side.
1. Rule out your own connection
Open the bank's website in a browser on the same computer. If it loads slowly or not at all, the problem is local: the internet line, a proxy, or a firewall rule blocking QuickBooks. On a hosted or server install, ask whoever runs it whether the machine itself had a bad night. Offices that host their own QuickBooks server often put an uptime monitor on it for exactly this reason, so a dead connection is spotted before someone spends an hour on a bank error that was never the bank's.
2. Update QuickBooks
Go to Help, Update QuickBooks Desktop, and install the latest release, then restart. Banks change their security requirements from time to time and an old release can fail the handshake. Also check the version under Help, About QuickBooks. The 2023 releases, including Enterprise 23.0, were discontinued on May 31, 2026, and Intuit's policy says they can no longer download transactions at all. If that is you, no fix on this page will bring the feed back, and the QuickBooks Enterprise bank feeds page explains the IIF route for older releases.
3. Sign in to the bank's website and clear alerts
Use the same credentials QuickBooks uses. Accept new terms, answer security prompts, and read any banner about accounting software or a new platform. Banks hold Direct Connect requests while a prompt is pending, and QuickBooks cannot see the prompt.
4. Turn off online banking on inactive accounts
Open the Chart of Accounts and include inactive accounts. Any old or closed account that still shows the online banking icon should have its online services deactivated from Edit Account, Bank Feed Settings. Then go back to the live account and update it again.
5. Run the test company check
Create a new sample company file, set up Bank Feeds for the same account, and try a download. If the test file downloads and your real file does not, the problem is in your company file and a rebuild or support call is next. If the test file fails with OL-205 too, the problem is at the bank or in its directory entry, and your time is better spent getting the bank to escalate.
6. Get the bank to escalate
Call the bank's business online banking or treasury support line, give them the exact code and the date it started, and ask them to open a case through Intuit's OFX connectivity process. Front-line support rarely knows the code, so ask for the team that handles QuickBooks Direct Connect.
If your bank recently merged or moved to a new platform, go straight to step 6 and read the OL-203 guide, which covers the changed-service case in more detail. It is the same fault under a neighboring code.
Is OL-205 a QuickBooks error or a Quicken error?
Both. Intuit and Quicken share the OFX banking standard and the OL code numbering, which is why search results mix the two. The causes overlap, but the fixes differ in the details. Quicken's One Step Update is not QuickBooks Bank Feeds, and a Quicken QFX download is not the file QuickBooks Desktop wants. For QuickBooks, the import format is a Web Connect .qbo file, or IIF on releases where Web Connect has been withdrawn.
Can I still get the transactions into QuickBooks while OL-205 is open?
Yes, and at month-end this is usually the real question. A Web Connect file does not use the broken connection. You import it through File, Utilities, Import, Web Connect Files, pick the existing account, and accept the lines in the Bank Feeds center like any download.
There are two ways to get that file:
- From the bank's website, if it offers a QuickBooks download for your account. This is free and fine for recent activity, but it needs the login and covers only the bank's download window.
- From the PDF statement, converted to .qbo. This works for any month you have a statement for, including statements a client emailed you, and on older releases the same statement can be written as IIF instead. The converter at the top of this page reads the PDF, shows every row for you to check against the balance, and writes the file.
One caution: a converted file carries its own transaction IDs, not the bank's, so QuickBooks will not recognize a transaction that the feed already brought in. Import only the dates the feed missed, or delete the overlap on the review screen before you accept.
What waiting on OL-205 costs
If the code clears overnight, it costs nothing. If it is a changed bank service, it can run for two or three weeks, and every day adds unrecorded transactions. Keying a month of a busy operating account by hand is an hour or more, plus the transposed digits you find at reconciliation. Converting the statement takes a couple of minutes and a balance check. On the Starter plan, $49 a month covers 50 statements, which is less than one afternoon of a bookkeeper's time, and you can convert a first statement without an account to see the result before paying. If several clients bank with the same institution, the bank feed not working page covers closing the whole month from statements.
How OL-205 compares with neighboring codes
| Code | What it usually means | First move |
|---|---|---|
| OL-205 | No usable reply from the bank's server | Wait one business day, then the test company check |
| OL-203 | Connection not completed: bank notice, changed service, inactive account | Clear the bank notice, deactivate stale accounts |
| OL-301 | The bank returned a general error for the request | Test company check, then wait on the bank |
| OL-332 | The bank refused the sign-in details | Password or Direct Connect PIN |
| OL-222 | A .qbo file QuickBooks could not read | Use a correctly built Web Connect file |
Frequently asked questions
How long does QuickBooks error OL-205 last?
A genuine server outage usually clears within 24 hours, which is what Quicken's support article says for this code family. If OL-205 is still there after two business days, treat it as a bank-side service change or a company file problem, run the test company check, and ask the bank to escalate.
Is OL-205 caused by my bank or by QuickBooks?
Usually the bank. The test company check settles it: if a brand-new sample file gets OL-205 on the same account, the fault is at the bank or in its directory entry. If the sample file downloads and your company file does not, the fault is in your file.
Does OL-205 happen in QuickBooks Online?
No. OL codes belong to QuickBooks Desktop Bank Feeds, including Pro, Premier and Enterprise, and to Quicken. QuickBooks Online reports its own numbered connection errors, and its manual upload accepts a .qbo file through Transactions, Bank transactions, Link account, Upload from file.
Can I import a PDF bank statement directly into QuickBooks Desktop?
No. QuickBooks Desktop has no PDF statement import. The statement has to be converted into a Web Connect .qbo file, or an IIF file on releases where Web Connect no longer works, before Desktop can read it. See the Web Connect from PDF page for the details of the file format.
Skip the manual entry
Upload a PDF bank statement and get a QBO or IIF file ready to import into QuickBooks.
Convert a Statement Free