OL 392 QuickBooks Error Fix and Backfill from PDF

OL-392 is a QuickBooks Desktop Bank Feeds error: QuickBooks asked your bank for new transactions and the request failed. Intuit lists it in one help article with OL-301, OL-332, OL-334 and OL-393, and the causes are the same for the group: something on the bank's side, the account setup in your company file, your internet connection, or a downloaded file QuickBooks cannot open. If the books have to close before the bank answers, convert the PDF statements to .qbo files, import them through Web Connect and fix the connection afterward.

Most pages ranking for this code are copies of one generic checklist with a phone number at the bottom. This one does three things they skip: it separates the three different errors that share the number 392, it puts the checks in the order that finds the cause fastest, and it deals with the part that actually costs you money, the weeks or months of transactions the broken feed never downloaded.

Which error 392 do you have?

Search results mix three unrelated problems. Check the exact wording on your screen before you follow any fix.

The Quicken wording is worth reading even if you use QuickBooks, because it names the real side effect of every long outage: the bank will only send so much history. When a feed has been down for a while, fixing the error does not bring back the missing months.

What does OL-392 mean in QuickBooks Desktop?

It means the bank's server did not complete the download QuickBooks requested. Intuit's article "Fix OL and OLSU Bank Feeds errors in QuickBooks Desktop" gives the causes for the whole OL-301, OL-332, OL-334, OL-392 and OL-393 group: a problem with the bank (an alert waiting in online banking, a switch from Direct Connect to Web Connect, an inactive account still enabled for online banking), outdated bank details in the financial institution list, the bank's server being down, your internet connection, or a downloaded file that is not .qbo. Intuit also states that QuickBooks only opens downloaded transactions in a .qbo file.

How do I fix QuickBooks error OL-392?

Go in this order and stop when the download works. The first four steps are yours and take minutes. The last one needs the bank and can take days.

1. Sign in to online banking outside QuickBooks

Log in on the bank's website. Accept new terms, answer security prompts and read any message waiting for you. A pending notice blocks the connection until someone clicks through it, and it is the most common cause Intuit lists. While you are there, confirm the account is still active and still enabled for QuickBooks access.

2. Update QuickBooks and check Bank Feeds Classic Mode

Install the latest release from Help, Update QuickBooks Desktop, then restart. Intuit also suggests checking whether the error appears in Bank Feeds Classic Mode. If it only fails in one mode, the connection is fine and the problem is in the bank feed screen itself.

3. Test in a new company file

Create a sample company, add the same bank account and try a download. If the test file connects, your real company file has a damaged account setup and step 4 fixes it. If the test file also fails with OL-392, the problem is at the bank or on your network, and editing your file will not help.

4. Deactivate and rebuild the bank connection

Open the account in the Chart of Accounts, choose Edit, go to Bank Feed Settings and deactivate all online services. Save, close and reopen the company file, then set up the bank feed again. If that fails, Intuit's next step is to rename the old account with an asterisk, set up a fresh account with bank feeds, and merge the two so the history stays in one register.

5. Escalate through the bank

When the test file fails too, call the bank's business or treasury support, not Intuit. Send them your Bank Feeds log and ask them to escalate through Intuit's OFX connectivity channel. This is the slow step. You rarely get a date, which is why the next section matters.

How long does OL-392 take to clear?

A pending bank notice clears the same day. A damaged account setup takes about half an hour to rebuild. A server problem or a connection change at the bank can take one to three weeks, sometimes longer after a merger or a platform migration. During that time nothing downloads, and when the feed comes back the bank usually sends only recent activity, often around 90 days. Anything older than that window never arrives through the feed.

How do I get the missing transactions into QuickBooks?

Use the statements. Every bank issues a monthly statement whether or not the feed works, and a .qbo file built from it goes in through the same Web Connect import QuickBooks already trusts, without touching the broken connection.

1. Download the monthly PDF statements for the gap from online banking. Closed-account and older statements are usually still there.
2. Drop each PDF into the PDF to QBO converter. Check that deposits minus withdrawals equal the change in balance before you download the file.
3. In QuickBooks Desktop choose File, Utilities, Import, Web Connect Files, pick the .qbo file and link it to the existing account, not a new one.
4. Match or add the transactions in Bank Feeds, then reconcile that month to the statement's ending balance before you import the next one.

On QuickBooks Desktop 2023 or older, where Intuit has withdrawn bank feed services, download IIF instead and import it through the IIF import for QuickBooks Desktop. A full catch-up across many months is covered on the bank feed not working page.

When the feed starts working again, look at the first download before you accept it. If it overlaps the months you already imported from statements, the transaction IDs differ, so QuickBooks may not recognize them as the same items. Match or exclude the overlap so nothing posts twice.

What waiting costs a business or a bookkeeper

Typing transactions from a statement takes one to two minutes a line once you include checking. A business checking account with 200 lines a month is three to six hours of entry per month of gap, and a single transposed figure breaks the reconciliation. A firm with ten clients at the same bank loses that per client. Converting a statement takes a couple of minutes, and once the months are in, matching them in reconciliation software or the QuickBooks Reconcile window closes the period.

Starter is $49 a month for 50 statements, Plus $149 for 200 and Pro $499 for unlimited, with yearly billing at half the monthly rate. You can convert one statement before creating an account and check every row against the balance first. If you are seeing other codes in the same family, the OL-301 guide and the OL-332 guide cover the sign-in and account mismatch cases.

Frequently asked questions

What causes error OL-392 in QuickBooks?

The bank's server did not complete the Bank Feeds request. The usual reasons are a notice waiting in online banking, a bank that switched your account to a different connection type, outdated bank details, a bank outage, a firewall or internet problem, or a damaged account setup in the company file.

Is OL-392 the same as QuickBooks error 392?

No. OL-392 is a bank connection error inside Bank Feeds. Error 392 without the OL prefix is reported when the QuickBooks program crashes or will not open, and it is fixed by repairing or reinstalling QuickBooks, not by contacting your bank.

Will I lose transactions because of OL-392?

You lose them from the feed if the outage runs longer than the history your bank sends on reconnect, often around 90 days. The transactions are still on your monthly statements, and you can import those months as .qbo files converted from the PDFs.

Can I use Web Connect while Direct Connect shows OL-392?

Yes. Web Connect is a file import, so it works when the live connection does not. Download a .qbo file from the bank if it offers one, or convert the PDF statement, then import it through File, Utilities, Import, Web Connect Files.