QuickBooks Error OL-392 -- Bank Feed Connection Failure

Error OL-392 blocks QuickBooks Desktop from connecting to your bank for transaction downloads; our engineers walk through restoring the link step by step.

When QuickBooks Desktop tries to pull down transactions from your financial institution and the handshake fails, the software surfaces Error OL-392. The result is that your bank feeds stop updating, leaving matched and categorized transactions stranded on the bank side. Resolving the error involves identifying which layer of the connection broke — the stored credentials, the financial institution directory entry, the QuickBooks company file, or the underlying network transport — and clearing that specific blockage.

What the Error Message Says

The full message reads:

QuickBooks was not able to complete your request. Please contact your financial institution. (OL-392)

In some builds the text is preceded by the institution name and the last four digits of the affected account number.

What the Code Means

OL-392 is a general-purpose bank communication error. It tells you that QuickBooks sent a request to the financial institution's OFX server and either received no valid response or received a response it could not parse. The code itself does not indicate which component failed — it is a catch-all for a broken round-trip.

What Triggers It

Our engineers see OL-392 most often in these scenarios, listed from most to least common:

1. Expired or changed bank credentials. The user ID or password stored in QuickBooks no longer matches what the bank requires, frequently because the bank forced a password reset or added multi-factor authentication on their own portal.
2. Bank server-side changes. The financial institution migrated its OFX endpoint, changed its connection protocol, or switched from Direct Connect to Express Web Connect without updating the FIDIR (Financial Institution Directory) embedded in QuickBooks.
3. Deactivated or reactivated account link. The bank feed connection was turned off and turned back on, but the internal account mapping in the company file retained stale routing information.
4. Outdated QuickBooks release. An older build of QuickBits Desktop contains a FIDIR that no longer matches the bank's current server configuration.
5. Company file damage in the bank feeds data tables. The .ND and .TLG support files or the underlying transaction list tables have minor corruption that prevents the feed from writing incoming data.
6. Firewall, antivirus, or proxy interference. Security software is blocking QuickBooks from reaching the OFX server over the required ports.

How to Fix It

Scenario 1 — Expired or Changed Bank Credentials

1. Open a browser and sign in to your bank's website directly using the same credentials QuickBooks uses. If the bank forces a password update or a security-question prompt, complete it there first.
2. In QuickBooks, go to Bank Feeds > Bank Feeds Center.
3. Select the affected account and click Update Now.
4. When prompted, re-enter the user ID and password.
5. If the bank requires a one-time passcode, QuickBooks should display a challenge prompt — enter the code sent by the bank.

Scenario 2 — Outdated QuickBooks Release or Stale FIDIR

1. Close QuickBooks and all company files.
2. Run Help > Update QuickBooks Desktop, then click Update Now and select Reset Update.
3. Check Get the latest updates and click Update Now.
4. When the update finishes, restart QuickBooks and attempt the bank feed download again.

Scenario 3 — Deactivated or Reactivated Account Link

1. Go to Lists > Chart of Accounts.
2. Right-click the affected account and choose Edit Account.
3. On the Bank Feed Settings tab, click Deactivate All Online Services.
4. Save and close the account.
5. Reopen the account, return to the Bank Feed Settings tab, and click Set Up Bank Feeds.
6. Walk through the wizard, selecting your financial institution and entering current credentials.

Scenario 4 — Firewall or Antivirus Interference

1. Temporarily disable third-party antivirus or firewall software.
2. Attempt the bank feed update.
3. If it succeeds, add QuickBooks (and its background processes — QBW32.exe, QBDBMgrN.exe, and QBUpdate.exe) to the exclusion list in your security software.
4. Re-enable the firewall or antivirus and confirm the download still works.

Scenario 5 — Company File Damage

1. Run File > Utilities > Verify Data.
2. If Verify reports damage, run File > Utilities > Rebuild Data.
3. Attempt the bank feed download again.

How to Prevent It Recurring

Keep QuickBooks Desktop on the latest release so the embedded FIDIR stays current — updates often include refreshed financial institution directory entries. When your bank notifies you of a portal migration or password-policy change, update the stored credentials in QuickBooks immediately rather than waiting for the next scheduled download. Avoid deactivating and reactivating bank feeds unless the connection is actively failing, since each cycle can leave residual mapping data in the company file. Finally, run Verify Data on a monthly schedule so minor file corruption is caught before it interferes with the bank communication tables.