OL 249 QuickBooks Error Fix and Statement Import
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-249 is a QuickBooks Desktop Bank Feeds error that stops a Direct Connect download before your transactions arrive. Intuit files it with OL-221, OL-231 and OL-232 and gives one set of fixes for the group, while Quicken, which uses the same code, calls it usually temporary. Give it one business day, then work the steps below. If the month has to close today, import the PDF statement as a Web Connect file and leave the connection for later.
Most pages ranking for this code copy the same generic list for every OL number. The useful part is knowing which of Intuit's steps actually applies to OL-249, which ones can make things worse, and what to do about the transactions while you wait.
What does error OL-249 mean in QuickBooks?
It means QuickBooks Desktop could not finish an online banking session with your bank. Intuit's help article "Fix OL and OLSU Bank Feeds errors in QuickBooks Desktop" lists it in the group "OL-221, OL-231, OL-232, or OL-249" and treats them as connection problems between the company file and the bank, not as a problem with any single transaction. It affects Pro, Premier and Enterprise on accounts set up for Direct Connect.
Quicken's support article on OL-248 and OL-249 says these errors "usually indicate a temporary problem" and suggests trying "the next business day", after checking that you can sign in on the bank's website and that the computer's date and time are correct. Those two checks cost nothing and are worth doing in QuickBooks too.
| What you see | Likely meaning | First move |
|---|---|---|
| OL-249 once, after the bank had maintenance | A temporary problem on the bank side | Wait one business day and run Send/Receive again |
| OL-249 every day for a week | A connection or company file problem | Run the test company check, then refresh the connection |
| OL-249 on QuickBooks Desktop 2023 or older | An unsupported release | Import statements as IIF, then plan an upgrade |
| OL-249 in Quicken | Quicken's version of the same code | Follow Quicken's steps, not QuickBooks' |
Check these two things before anything else
Sign in to the bank's website in a browser. If the bank asks you to accept new terms, confirm a security prompt or reset a password, do it there first, because QuickBooks cannot show you that screen. Then check the date, time and time zone on the computer that runs QuickBooks. A clock that is far off can break the secure session, and it is the cheapest cause to rule out.
If you are on QuickBooks Desktop 2023 or older, stop here. Intuit discontinued the 2023 releases on May 31, 2026, including bank feeds and Web Connect, so no amount of troubleshooting brings the connection back. The discontinued QuickBooks Desktop page explains what still works on those versions.
How do I fix error OL-249 in QuickBooks Desktop?
Back up the company file, then work Intuit's steps in order and stop as soon as a download succeeds. Start with a test company file to learn whether the bank or your file is the problem, refresh the bank connection, and only then try the heavier fixes. Each step below says what it tells you.
1. Download in a test company file
Create a blank company, add one bank account, and set up Bank Feeds for it with the same credentials. If the download fails there too, the problem is on the bank side or with the credentials, and the fix is a call to the bank. If it works, your own company file is the problem and the next steps apply.
2. Refresh the connection
Intuit's instructions are to deactivate online services on any inactive accounts that still have them, then set the connection up again. Hidden inactive accounts are easy to miss, so open the Chart of Accounts with Include inactive checked. When you set the connection up again, Intuit's article says to hold Ctrl during setup.
3. Create and merge accounts
This step works around damage in the account record. You create a new account, deactivate online services on the old one, and merge the old one into the new. Merging cannot be undone, so make sure the backup from the start is good and that the account is reconciled up to the last statement before you try it.
4. Turn online banking off and on for every account
If several accounts are connected, turn online banking off for all of them and back on one at a time. The account that brings the error back is the one to work on with the bank.
5. Call the bank
If the test company fails, ask for someone who supports QuickBooks Direct Connect. Ask whether the account is enrolled for Direct Connect, whether the enrollment changed recently, and whether a separate Direct Connect PIN is required. Many banks use a PIN that is different from the online banking password.
How do I get the month into QuickBooks while OL-249 is open?
Import the bank statement as a file. A Web Connect .qbo file does not use the Direct Connect session at all, so the error does not block it. QuickBooks Desktop has no PDF statement import, so the PDF statement has to become a .qbo file first, or an IIF file on releases where Web Connect is gone.
- Download the monthly statement PDF from the bank's website.
- Convert it with a PDF to QBO converter and check the rows against the opening and closing balance.
- In QuickBooks Desktop, go to File, Utilities, Import, Web Connect Files, and choose the existing bank account when asked.
- Accept the transactions in the Bank Feeds Center and reconcile to the statement's ending balance.
Intuit's own troubleshooting list has a step called "Check if the file from your bank works with QuickBooks" and notes that QuickBooks only opens downloaded transactions in a .qbo file. That is the same route. Files built by hand or by cheap converters often fail on import with error OL-222, usually because the bank ID or the format is off. The Web Connect files from PDF page explains what a file needs so Desktop accepts it.
What to watch for when the connection comes back
A converted file carries its own transaction IDs, not the bank's, so QuickBooks will not recognize the same lines when Direct Connect starts working again. Import from the file only the dates the connection missed, and when the feed returns, delete any overlap in the Bank Feeds Center before you accept it. Reconciling each month against the statement's ending balance catches anything that slips through. Firms that reconcile dozens of accounts each month often run separate bank reconciliation software to match statements to the ledger, but for a single month the QuickBooks reconcile screen is enough.
If the error keeps coming back for weeks, treat the statement import as the routine rather than the emergency. Plenty of Desktop firms run on monthly Web Connect files for accounts whose Direct Connect is unreliable, and the bank feed not working page walks through that setup.
How OL-249 compares with nearby errors
| Code | What Intuit or the bank says | Where to go |
|---|---|---|
| OL-221, OL-231, OL-232, OL-249 | One group in Intuit's article, connection problems | The steps above |
| OL-301 | The bank sent an error message, grouped with OL-393 | Test company, then the bank |
| OL-332 | The bank refused the sign-in details | Password or Direct Connect PIN |
| OL-206 | An online payment did not send | Ask the bank before resending |
| OL-222 | A .qbo file QuickBooks could not read | Use a correctly built Web Connect file |
What it costs to wait versus import
Waiting is free if the error clears tomorrow. If it does not, the cost is the close. A busy business checking 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 hunt for 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. For an accounting firm with several clients on the same unreliable bank, the PDF statements to QuickBooks Desktop page covers batch imports for Pro, Premier and Enterprise.
Frequently asked questions
What causes QuickBooks error OL-249?
A Direct Connect session between QuickBooks Desktop and the bank that did not complete. Intuit groups it with OL-221, OL-231 and OL-232 and points to the bank connection or the company file. Common triggers are bank maintenance, a pending prompt on the bank's website, a wrong computer clock, damage in the account record, or an unsupported QuickBooks release.
Will error OL-249 go away on its own?
Often, if the cause was on the bank side. Quicken describes OL-248 and OL-249 as usually temporary and suggests trying again the next business day. If it is still there after one business day, run the test company check, because a company file problem will not clear by waiting.
Is OL-249 a QuickBooks or a Quicken error?
Both products use it. In QuickBooks Desktop it appears in Bank Feeds and Intuit's OL and OLSU article covers it. In Quicken it appears during One Step Update and Quicken's own article covers it. If the code has a letter after it, such as OL-249-A, you are almost certainly in Quicken.
Does OL-249 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 Transactions, Bank transactions, Link account, Upload from file accepts a .qbo file if you need to fill a gap.
Can I import transactions into QuickBooks Desktop while the error is open?
Yes, through a Web Connect file. Importing a .qbo file through File, Utilities, Import, Web Connect Files does not use the Direct Connect session, so OL-249 does not block it. Convert the bank's PDF statement to .qbo, import it into the existing account, and reconcile against the statement.
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