QuickBooks Error OL-393 -- Bank Server Rejected Online Banking Request

QuickBooks OL-393 means your bank's server rejected an online banking request; our engineers walk through identifying the trigger and restoring the connection.

QuickBooks Error OL-393 appears when your financial institution's server refuses an online banking request from QuickBooks Desktop. The error can surface during direct connect downloads, payment transmissions, or when setting up a new online banking connection. Our engineers have resolved this error across every supported QuickBooks Desktop version, and in nearly every case the root cause is identifiable through a structured troubleshooting sequence.

What the Error Message Says

The full message displayed by QuickBooks is:

QuickBooks was not able to complete your request. Contact your financial institution. (OL-393)

In some installations the message includes additional context:

Your financial institution has rejected your request. (OL-393)

The wording may vary slightly depending on your QuickBooks Desktop release year, but the error code OL-393 is consistent.

What the Code Means

Error OL-393 is a server-side rejection code. Unlike errors in the OL-2xx range, which typically point to local connectivity or configuration problems, OL-393 indicates that QuickBooks successfully reached the financial institution's server, authenticated the session, and submitted a request — but the server returned a decline or refusal. The rejection is not a timeout or a network failure; it is an affirmative response from the bank telling QuickBooks the request cannot be processed.

What Triggers It

Our engineers see OL-393 most frequently under these scenarios:

1. Account number or routing number mismatch. The account credentials stored in QuickBooks do not exactly match what the bank has on file for direct connect access.
2. Customer ID or password changed at the bank's website. The bank-side login was updated but QuickBooks is still sending the previous credentials.
3. Account closed or online banking service revoked. The bank disabled direct connect access for the account, often due to inactivity or a product change.
4. Server-side maintenance or outage. The financial institution's direct connect servers are temporarily unavailable or returning errors to all requests.
5. QuickBooks brand or FIDirectory entry is outdated. The routing or institution identification number stored in QuickBooks no longer matches the bank's current configuration.

How to Fix It

Scenario 1 — Customer ID or password changed at the bank (most common)

1. Open a browser and log in to your bank's website using your current credentials. Confirm you can access the account successfully.
2. In QuickBooks, go to Lists > Chart of Accounts.
3. Right-click the affected account and select Edit Account.
4. In the Bank Feed Settings tab, click Deactivate All Online Services.
5. Save and close the account.
6. Reopen the account, go to the Bank Feeds tab, check Enable Account, and follow the on-screen prompts to re-enter your current customer ID and password.
7. Complete the connection wizard and attempt a download.

Scenario 2 — Account number or routing number mismatch

1. Log in to your bank's website and locate the full account number and routing number as displayed there.
2. In QuickBooks, go to Lists > Chart of Accounts.
3. Right-click the affected account and select Edit Account.
4. Compare the account number and routing number shown under Bank Feed Settings against what the bank displays.
5. If any digits differ, deactivate the online services for that account (as in Scenario 1, step 4), then reactivate and re-enter the correct numbers during the setup wizard.

Scenario 3 — Server-side maintenance or outage

1. Check your bank's support page or status dashboard for announced direct connect outages.
2. If an outage is confirmed, wait and retry the download after the bank resolves the issue — typically within several hours.
3. If no outage is posted, wait at least one hour and retry. Transient server errors can produce OL-393 without a public announcement.

Scenario 4 — Outdated FIDirectory or brand file

1. Close QuickBooks Desktop.
2. Download the latest QuickBooks Tools Hub and run the QuickBooks Program Issues tool, which updates the FIDirectory component.
3. Reopen QuickBooks and attempt the download again.
4. If the error persists, deactivate and reactivate the account connection as described in Scenario 1 to force QuickBooks to read the updated institution data.

How to Prevent It Recurring

• Whenever you change your bank website password, immediately update the credentials in QuickBooks before the next scheduled download.
• Review your account settings in QuickBooks after any bank merger, account conversion, or product tier change, as these events frequently alter routing numbers or direct connect enrollment.
• Keep QuickBooks Desktop updated to the latest release, since Intuit periodically pushes FIDirectory updates that reflect bank-side configuration changes.
• If you manage multiple accounts at the same institution, deactivate and reactivate all of them together after a credential change to prevent mismatched connection states.