QuickBooks Error OL-393: Causes, Solutions, and Bank Feed Troubleshooting

Data Service Team is sharing practical guidance for QuickBooks Desktop users experiencing QuickBooks Error OL-393, a banking connection error that can interrupt online banking activities and prevent certain financial transactions from processing correctly.

The error can appear when QuickBooks Desktop communicates with a financial institution through Bank Feeds. In some situations, the problem involves bill-payment requests, outdated payee information, an inactive banking account, or a communication issue between QuickBooks and the financial institution.

For business owners and accounting professionals who depend on timely transaction downloads, identifying the actual cause is more useful than repeatedly refreshing the same banking connection. The following guide explains how to investigate the error, protect existing accounting records, and work through practical troubleshooting steps.

QuickBooks Error OL-393 is a banking connection error associated with QuickBooks Desktop Bank Feeds and certain financial institution communication requests.

It can occur when the information maintained in QuickBooks does not match the information expected by the bank. Bill-payment requests involving outdated or unsynchronized payees and references to closed accounts are among the possible causes.

The error may also be associated with:

• Temporary problems with the bank's online banking servers.
• An outdated or interrupted banking connection.
• Inactive accounts that still have online banking enabled.
• Incorrect or outdated payee information.
• Problems with the company file.
• Internet connectivity interruptions.
• Changes to the bank's online banking service.
• Incompatible transaction download formats.
• An outdated QuickBooks Desktop installation.

OL-393 should not automatically be treated as a damaged company-file error. The problem may originate with the financial institution, the banking connection, or a particular account within the company file.

Understanding this distinction helps prevent unnecessary changes to important accounting records.

Bank Feeds help businesses bring financial transactions into QuickBooks Desktop so they can review, match, and categorize activity.

When Error OL-393 interrupts the process, users may experience several difficulties:

Interrupted bank downloads: New transactions may not appear in the expected banking window.

Delayed reconciliation: Accounting teams may have to postpone transaction matching until the connection works again.

Bill-payment complications: An outdated payee or closed account referenced in a payment request may interfere with banking communication.

Repeated connection errors: Refreshing an unchanged banking configuration may produce the same error.

Uncertainty about transaction status: Users may be unsure whether a payment request was transmitted or whether an account connection needs attention.

A failed banking request does not necessarily mean that a payment was completed or that money was transferred. Users should verify payment status directly with their financial institution before attempting to submit the same payment again.

Before changing banking settings, QuickBooks users should protect their accounting information and identify the scope of the problem.

Data Service Team recommends beginning with these checks.

1. Create a company-file backup.

Open QuickBooks Desktop and select File → Back Up Company → Create Local Backup.

Choose a secure location and complete the backup verification process when available. Preserve the original .QBW company file and its backup .QBB separately.

2. Review pending banking transactions.

Open Bank Feeds and check whether downloaded transactions are waiting to be reviewed, matched, or added.

Do not delete pending transactions simply to clear the error. Matching existing activity first helps reduce the risk of duplicate entries.

3. Sign in to the bank independently.

Open the financial institution's official website and sign in using the normal banking credentials.

Check for security alerts, updated account agreements, maintenance notices, or requests requiring acknowledgment.

4. Confirm the affected account.

Determine whether OL-393 appears for one bank account or several accounts connected to the same financial institution.

This information helps distinguish an account-specific issue from a broader bank connection problem.

Estimated initial assessment time: 10–15 minutes.

If the error continues, the next step is to determine whether the bank connection or the QuickBooks company file is responsible.

The following troubleshooting methods address different possible causes. They should be performed carefully, with a fresh backup available before account-level changes.

Estimated time: 5–10 minutes.

A financial institution may temporarily change its online banking service, experience server maintenance, or require customers to acknowledge new account notifications.

Follow these steps:

1. Open the bank's official website.
2. Sign in to the affected banking account.
3. Review notifications and security messages.
4. Check for maintenance announcements.
5. Confirm that the account is active.
6. Review whether the bank has changed its online banking access method.

Pay particular attention to notices about changes between Web Connect and Direct Connect services.

These methods use different connection workflows. A change made by the bank may require the QuickBooks banking configuration to be reviewed.

What if this method fails?

If the bank website works normally but QuickBooks still displays OL-393, continue by checking the company file and testing the banking connection separately.

Estimated time: 15–25 minutes.

A test company file helps determine whether the problem is associated with the existing QuickBooks company file or the financial institution's connection.

Before proceeding, keep the original company file and backup unchanged.

Follow these steps:

1. Open QuickBooks Desktop.
2. Select File.
3. Choose New Company.
4. Select Express Start or the available company setup option.
5. Create a temporary test company.
6. Set up Bank Feeds for the affected financial institution, where permitted.
7. Attempt to download transactions.

Review the result carefully.

If the same OL-393 error appears in the test company, the issue may involve the bank's connection, its server, or the banking service configuration.

If the test company downloads transactions successfully, the original company file or its banking account configuration may require additional investigation.

A test company is a diagnostic environment. It should not replace the original business file or be used as the permanent accounting record.

What if the error appears in both companies?

Check the bank's connection service and ask the financial institution whether there are known changes or restrictions affecting QuickBooks Desktop banking requests.

Estimated time: 10–20 minutes.

Web Connect allows eligible banking transactions to be downloaded from a financial institution and imported into QuickBooks Desktop.

The downloaded transaction file generally uses the .QBO extension.

To test this method:

1. Sign in to the bank's official website.
2. Open the transaction download section.
3. Select the appropriate bank account and date range.
4. Choose the QuickBooks-compatible Web Connect download option, if available.
5. Save the .QBO file in a known location.
6. Open QuickBooks Desktop.
7. Import the downloaded file using the available Bank Feeds or Web Connect workflow.
8. Review the imported transactions before adding or matching them.

The .QBO extension matters because QuickBooks Desktop does not treat every bank download format as a compatible Web Connect file.

Do not rename an unrelated file extension to .QBO and assume that it will become compatible.

What if the QBO file cannot be imported?

Check whether the financial institution offers a QuickBooks-compatible download. If the file is rejected despite being downloaded in the correct format, investigate its contents and the bank's current export configuration.

Estimated time: 10–20 minutes.

An inactive account in QuickBooks Desktop may still retain online banking settings.

This can create confusion when QuickBooks attempts to communicate with the financial institution.

To review inactive accounts:

1. Open the company file.
2. Select Company → Chart of Accounts.
3. Enable Include Inactive, if available.
4. Look for inactive accounts displaying the lightning-bolt banking indicator.
5. Identify whether an inactive account still has online banking enabled.

If an inactive account should no longer connect to the bank, review its settings.

Right-click the relevant account and choose Edit Account.

Open Bank Feed Settings, select Deactivate All Online Services, and confirm the change when appropriate.

Save the account and close the window.

Afterward, close and reopen the company file and check whether the banking indicator has disappeared.

Do not deactivate an active business account simply because it appears in the list. Confirm its actual accounting purpose first.

What if the account cannot be edited?

Stop before making structural changes to the chart of accounts. Review the account's transactions and existing banking configuration, and investigate whether the company file has a separate integrity problem.

Estimated time: 10–15 minutes.

If the bank account remains active and its website works normally, refreshing the connection may help resolve an outdated banking session.

Before proceeding, make sure pending downloaded transactions have been reviewed and that a verified backup exists.

Open the Chart of Accounts and locate the affected bank account.

Review its online banking settings and follow the available account-connection workflow to refresh or re-establish the connection.

Some QuickBooks Desktop Bank Feeds workflows use the Ctrl key while selecting particular connection or setup buttons to refresh the connection process. Follow the applicable Intuit instructions for the exact screen and button involved; this is not a general shortcut to press throughout the application.

If multiple accounts use the same bank, identify whether one account is causing the problem before changing all the connections.

What if refreshing does not work?

Check the bank's current connection method and determine whether its online banking service has changed. If the bank has discontinued the connection method used by the installed QuickBooks release, repeated refresh attempts will not resolve the underlying compatibility issue.

Estimated time: 15–30 minutes.

Payee synchronization is particularly relevant when the error occurs during bill-payment activities.

A payment request may reference a payee that is outdated, duplicated, or no longer recognized by the financial institution.

Review the following:

• Confirm that the intended payee still exists.
• Check for duplicate vendor or payee records.
• Review the payment details.
• Confirm that the destination bank account is active.
• Check whether a payment request references a closed account.
• Verify payment status directly with the bank before resubmitting anything.

Do not delete or recreate payment records simply because the error appears.

A payment that has already been processed should not be submitted again without confirming its status.

What if the payee information appears correct?

Ask the financial institution whether its bill-payment service has changed its payee requirements or whether a previous payment request remains pending.

Estimated time: 10–20 minutes.

QuickBooks Desktop requires an appropriate network connection for online banking operations.

Windows Firewall settings, security applications, proxy configurations, or an unstable internet connection may interfere with communication.

Check these items:

1. Confirm that Windows has an active internet connection.
2. Open QuickBooks Desktop and test another online function, if available.
3. Review Windows Firewall notifications.
4. Check whether legitimate QuickBooks applications are being blocked.
5. Review network security rules with the person responsible for managing the computer.

Do not disable Windows Firewall permanently or open unnecessary network ports.

If the computer uses a business network, verify whether a recent security policy change affected the application.

What if the connection still fails?

Compare the behavior on another authorized network or computer when practical. If the problem follows the bank account rather than the computer, investigate the financial institution's connection service.

Estimated time: 20–40 minutes for initial checks.

If banking downloads work in a test company but fail in the original company file, the original file's banking configuration or data integrity may need further investigation.

QuickBooks Desktop includes a Verify Data utility that can help identify certain company-file data problems.

Follow these steps:

1. Open the original company file.
2. Select File → Utilities → Verify Data.
3. Allow the verification process to finish.
4. Review the results.
5. If QuickBooks identifies an issue, review the recommended repair procedure.
6. Create another verified backup before performing a rebuild or other repair.

A company-file repair should not be the first response to every OL-393 error. The test-company result and other banking checks should help establish whether file damage is a reasonable possibility.

What if verification identifies a problem?

Preserve the original file and backup. Review the reported issue before attempting a rebuild. If the problem remains unclear, have the file examined before making further structural changes.

QuickBooks Tool Hub is a Windows utility that provides access to selected diagnostic tools for QuickBooks Desktop.

QuickBooks File Doctor is designed to diagnose and address certain company-file and network-related problems.

These tools may be relevant when a company-file or network issue is suspected, but neither is a dedicated bank-server repair utility.

For example, if OL-393 also appears in a new test company, running File Doctor repeatedly is unlikely to resolve a problem originating from the financial institution.

A better approach is to use the test-company results to choose the correct troubleshooting path.

Before running any repair utility, create a verified company-file backup and preserve the original .QBW file.

The financial institution should be involved when the error appears in multiple company files, its online banking website displays warnings, or a transaction request appears to be rejected by its banking service.

Useful information to prepare includes:

• The exact error code: OL-393.
• The name of the affected financial institution.
• The affected account type.
• The date and time the error appeared.
• Whether the error occurs in a test company.
• Whether Web Connect downloads work.
• Any available Bank Feeds error details.

The bank can investigate its connection service, account status, and payment records.

If a payment's status is uncertain, verify it before attempting another transaction.

Data Service Team provides QuickBooks-related accounting technology guidance for businesses experiencing software and banking workflow problems.

Its educational approach emphasizes identifying the actual source of an error before changing company-file settings or repeating banking operations.

For QuickBooks Error OL-393, the most useful starting information includes the affected bank, whether the issue occurs in a test company, and whether manually downloaded .QBO transactions can be imported.

Users can contact Data Service Team at +1-888-718-7888 for a Free Consultation about their QuickBooks Desktop concerns.

This guide was prepared using documented QuickBooks Desktop Bank Feeds troubleshooting workflows, Windows-oriented menu paths, and practical accounting data-protection principles. The recommended procedures distinguish financial institution connection problems from company-file issues. Menu availability and banking features can vary by QuickBooks Desktop release and financial institution.

QuickBooks Error OL-393 can interrupt online banking activities, but the error does not automatically indicate that the company file is damaged.

The most effective approach is to protect the accounting data, check the bank's website, test the connection in a separate company file, review inactive accounts, and investigate payee synchronization when bill payments are involved.

QuickBooks Tool Hub and QuickBooks File Doctor may be useful for certain application or company-file problems, but banking errors require a diagnosis based on the actual connection behavior.

Data Service Team encourages QuickBooks users to verify payment status, preserve pending transactions, and avoid unnecessary changes to their accounting records while investigating the error.

Contact:

Data Service Team
Phone: +1-888-718-7888
Free Consultation