QuickBooks Desktop Banking Error Guide · OL Series
How to Fix QuickBooks Error OL-203
QuickBooks Desktop displays: "Error OL-203" when attempting to set up or update bank feeds (online banking) in QuickBooks Desktop.
Error OL-203 is a bank feeds connection error — QuickBooks could not verify or connect to your financial institution. The OL series errors (OL-202 through OL-393) all relate to bank feeds and share similar causes. At QuickFix Bookkeeping, the first step is always the test company file diagnostic — it definitively tells you whether the problem is at your bank's servers or in your company file, which determines everything that follows.
The QuickFix Bookkeeping Distinction — The Test Company Diagnostic
Before spending time on troubleshooting, run the test company diagnostic first — it takes 5 minutes and tells you exactly which of the two root causes you are dealing with.
Test result: Error also occurs in test company
The problem is at your bank's side — their servers are down, they changed their connection method (Web Connect vs Direct Connect), they require identity verification, or their bank information in QB's Financial Institutions Directory (FiDir) is outdated. Fix: contact the bank, update FiDir, or switch connection method.
Your company file is fine. No file-level troubleshooting needed.
Test result: Works fine in test company
The bank connection is fine — the problem is specific to an account or data in your main company file. An inactive bank account with bank feeds still active, a corrupted bank account record, or pending unmatched transactions are causing the error in the specific company file. Fix: deactivate and reactivate bank feeds for the affected account, or merge/recreate the account.
The bank is fine. All troubleshooting stays within your company file.
Pending bank alerts trigger OL-203 — check these first: Most banks require identity confirmation before they allow a new automated connection, especially after a QB version update or after a period of no activity. Log into your bank's website directly (not through QB) and check the message center or notifications inbox for any alerts requiring acknowledgment before re-attempting the bank feed connection. This takes 2 minutes and resolves OL-203 in a significant number of cases without any further troubleshooting.
What Causes QuickBooks Error OL-203?
Pending Bank Alerts Requiring Acknowledgment
Very common first cause — your bank has a security alert, identity verification request, or terms update in your online banking message center that must be acknowledged before QB can connect. Log into the bank's website directly and clear any alerts before reconnecting in QB.
Bank Changed Service Type (Web Connect vs Direct Connect)
Your bank switched from Direct Connect to Web Connect (or vice versa), or changed the connection method entirely. QB's stored bank feed connection method no longer matches what the bank offers. The account must be deactivated and reconfigured using the new method.
Inactive Bank Account with Active Bank Feeds
A bank account in the Chart of Accounts is marked as Inactive but still has bank feeds (the lightning bolt icon) set up. QB tries to connect and update this account, fails, and throws OL-203. Fix: show inactive accounts, find the account, deactivate its bank feeds, then re-setup only the active accounts.
Outdated Financial Institutions Directory (FiDir)
QB's local FiDir.txt file stores how to connect to each bank. If a bank changed its connection details and QB's FiDir has not been updated, QB sends connection requests to the wrong endpoint. Refreshing the FiDir updates the bank's connection information in QB.
Bank Merger or Name Change
Your bank was acquired by or merged with another institution and changed its name, routing, or online banking platform. QB's stored connection references the old institution name or connection method. The account must be deactivated and re-linked to the new institution's bank feeds entry in QB.
Corrupted Bank Account Record in Company File
The bank account record in the Chart of Accounts has become corrupted or contains data that conflicts with the bank feeds connection. Merging and recreating the account (by adding an asterisk, deactivating feeds, creating a new account, merging) resolves this without deleting any transaction history.
How to Fix QuickBooks Error OL-203
Run the test company diagnostic first (Method 1) — it determines which of the remaining methods you need and prevents wasting time on the wrong type of fix.
METHOD 1
Run the Test Company Diagnostic — Identify Bank vs File Issue
Always do this first — determines everything
Before clearing alerts or deactivating accounts: first check your bank's website for pending alerts (2 minutes), then run the test company diagnostic to determine the root cause definitively.
1
Clear bank alerts first: log into your bank's website directly (not through QB). Go to the message center, notifications, or alerts section. Acknowledge or dismiss any pending alerts, identity verification requests, or terms updates. Then close the bank website and retry the bank feed connection in QB. If OL-203 is resolved — done. If not, continue to step 2.
2
Test company diagnostic: in QB, go to File > New Company > Express Start (or Start Setup, then Skip). Enter minimal info to create a test company. In the test company: set up Bank Feeds for the account that is showing OL-203. Use the same bank and credentials as your real company file.
3
Interpret the result: If OL-203 also appears in the test company → the problem is at the bank (proceed to Methods 2 and 3). If the bank feed works in the test company → the problem is specific to your main company file (proceed to Methods 4 and 5). Delete the test company file after the diagnostic — it is not needed further.
METHOD 2
Update the Financial Institutions Directory (FiDir)
OL-203 also in test company — bank-side issue
The FiDir.txt file in QB's installation contains up-to-date connection information for each bank. If your bank changed its connection details, refreshing the FiDir updates QB's reference for your bank.
1
Close QB. Navigate to C:\ProgramData\Intuit\QuickBooks [Year]\Components\OLB\Branding\Filist. Find fidir.txt > right-click > Rename > change to fidir.old.
2
Alternatively, in QB: Banking > Bank Feeds > Bank Feeds Center. From the Send/Receive dropdown, select Sync all for this bank. This triggers QB to refresh the FiDir data from Intuit's servers automatically — no manual file editing required.
3
Also check TLS settings: Internet Explorer > Tools > Internet Options > Advanced > Security. Ensure Use TLS 1.2 is checked. Uncheck Use TLS 1.0. Click Apply > OK. Reopen QB and retry the bank feed setup.
METHOD 3
Deactivate and Reconnect the Bank Account with New Setup
Bank changed service method / merger
If the bank changed its connection method or was acquired, the existing bank feed connection must be fully deactivated and re-established using the bank's current setup.
1
In QB Chart of Accounts: right-click the affected bank account > Edit Account > Bank Feeds Settings tab > Deactivate All Online Services > OK > Save and Close. This removes the bank feed connection without deleting any transaction data.
2
Close and reopen the company file. Then: Banking > Bank Feeds > Set Up Bank Feed for an Account. Search for the bank by its current name. Select the account > connect. QB will present the available connection options (Web Connect or Direct Connect) based on what the bank currently offers.
3
If you switched from Direct Connect to Web Connect: you will now need to manually log into the bank's website, download a .QBO file for each statement period, and import it into QB via Banking > Bank Feeds > Import Web Connect File. Direct Connect pushed transactions automatically; Web Connect requires manual download.
METHOD 4
Find and Fix Inactive Accounts with Active Bank Feeds
Works in test company — company file issue
A common company-file cause of OL-203 is an inactive bank account that still has bank feeds configured. QB tries to update it, fails, and reports OL-203. The lightning bolt icon on the account confirms bank feeds are active.
1
Open the Chart of Accounts (Ctrl+A). At the bottom, tick the Include inactive checkbox. Scan through the list for any bank or credit card account that shows as inactive (greyed out name with X) but still displays a lightning bolt icon (bank feeds active).
2
Right-click each such account > Edit Account > Bank Feeds Settings tab > Deactivate All Online Services > OK > Save and Close. After deactivating all inactive accounts with active feeds: close and reopen the company file. Retry the bank feed update. The active accounts should now connect without OL-203.
METHOD 5
Merge and Recreate the Affected Account to Fix Corrupted Record
Works in test company — account record corrupted
If the test company works but inactive accounts have been cleaned up and OL-203 persists, the active account record itself is corrupted. The merge-and-recreate method fixes the account record without losing any transaction history.
1
Chart of Accounts > right-click the affected account > Edit Account. Copy the exact account name. Add an asterisk at the end of the name (e.g., "Business Checking*"). Bank Feeds Settings tab > Deactivate All Online Services > OK. Save and Close. Close and reopen the company file.
2
Create a new bank account: Chart of Accounts > New > Bank. Paste the original account name (without asterisk). Set account number and other details to match. Save. QB will ask to merge — click Yes. The new account absorbs all transactions from the old one.
3
Set up bank feeds on the newly recreated account: Banking > Bank Feeds > Set Up Bank Feed for an Account > select the account > follow the setup wizard. Test downloading transactions. OL-203 should be resolved for this account.
Quick Reference — Which Method to Try Based on Your Situation
| Your situation |
Root cause |
Start with |
| OL-203 just started — no obvious changes |
Pending bank alerts |
Method 1 step 1 — check bank alerts first |
| OL-203 in test company too |
Bank server / FiDir / connection method |
Methods 2 + 3 — FiDir + reconnect |
| Works in test company, fails in main file |
Inactive account or corrupted record |
Methods 4 + 5 — inactive accounts / merge |
| Bank recently changed name or was acquired |
Old institution reference in QB |
Method 3 — deactivate and reconnect to new bank |
Frequently Asked Questions
What is the difference between OL-203 and other OL-series errors (OL-202, OL-205, OL-221)?
All OL-series errors (OL-202 through OL-393) share the same general root causes and the same diagnostic approach. They indicate different stages at which the bank feeds connection failed — OL-202 and OL-203 occur during the connection verification phase; OL-205 and OL-209 occur during account setup; OL-221 and OL-231 indicate a file format mismatch. In practice, the troubleshooting steps are identical for OL-203, OL-205, and OL-209 — run the test company diagnostic, clear bank alerts, update FiDir, and deactivate/reconnect the account. The error code number tells you at which step the failure occurred but does not change which fixes to apply.
What is the difference between Web Connect and Direct Connect in QuickBooks?
Direct Connect is a live, automated two-way connection — QB connects to your bank's servers in real time, downloads transactions, and can even initiate payments. It typically costs a monthly fee through your bank. Web Connect is a manual import process — you log into your bank's website, download a .QBO file, and import it into QB. Web Connect is free but requires manual action each time. If your bank discontinued Direct Connect (which many banks did after 2020), you will need to switch to Web Connect. After deactivating Direct Connect, go to your bank's website > download transactions as .QBO > QB: Banking > Bank Feeds > Import Web Connect File.
Will deactivating bank feeds on an account delete my existing transaction data?
No — deactivating bank feeds only disconnects the automated connection to the bank. All previously imported and matched transactions remain in your company file exactly as they were. You will not lose any reconciled transactions, entered data, or historical records. The only thing removed is the automated connection itself. When you reactivate bank feeds by reconnecting, QB will start downloading new transactions from a date you specify — typically the date of the most recent transaction already in QB, to avoid duplicates. Existing data from before reconnection is entirely unaffected.
Related QuickBooks Banking Errors
Bank Feeds Still Failing After All Troubleshooting Steps?
Let QuickFix Bookkeeping Restore Your Bank Feed Connection.
Certified Intuit ProAdvisors — QuickBooks Desktop Specialists
If OL-203 persists after the test company diagnostic and all account-level fixes, the issue usually involves a bank-specific integration that has changed or a corrupted company file section that requires ProAdvisor-level data repair. We restore your bank feeds and ensure reconciliation is accurate throughout.
Book a Free 30-Minute Consultation
No obligation. Same-day response. Bank feeds restored fast.
