QuickBooks Error OL-332

Let’s Dive in to see…

How to Fix QuickBooks
Error= OL-332

Schedule a call to fix QuickBooks Errors
QuickBooks Online

QuickBooks Desktop Bank Feeds Error · OL Series

How to Fix QuickBooks Error OL-332

QuickBooks displays: "OL-332: Cannot verify your financial institution information" or a message indicating an invalid customer ID or PIN when downloading bank transactions.

Error OL-332 appears during bank feed downloads and means QuickBooks found an invalid customer ID or PIN for the bank account. At QuickFix Bookkeeping, the diagnostic test is the test company file method: create a new QB company file, add the same bank account, and attempt the download. If it works in the test file — the issue is with your company file's bank feed setup, not the credentials or bank server. If it also fails — the bank's server has the problem.

The QuickFix Bookkeeping Distinction — The Test Company File Diagnostic

OL-332 can come from two different sources. The test company file tells you immediately which one you're dealing with.

Test file works → Company file issue

The bank feed setup in your main company file is corrupted. Fix: copy-and-merge the affected bank account (add asterisk to name, deactivate online services, create new account, merge back). This rebuilds the bank feed setup cleanly.

Test file also fails → Bank server issue

The problem is at the bank's server — it's returning OL-332 for all connections, not just your company file. Contact the bank with your bank feeds log file. Also check for pending alerts on the bank's website requiring acknowledgment.

Running the test company file — step by step: QB → File → New Company → Express Start (or Start Setup) → complete minimal setup → Banking → Bank Feeds → Set Up Bank Feeds for Account → add your bank → enter the same credentials → attempt to download. If transactions download in the test file without OL-332 → your main company file's bank feed setup needs the copy-and-merge fix. If OL-332 also appears in the test file → take your bank feeds log to the bank's support team and contact Intuit if the bank's server issue persists.

What Causes QuickBooks Error OL-332?

Incorrect Customer ID or PIN in QB

Primary cause — the customer ID or PIN (not the same as your website password in some banks' Direct Connect setup) stored in QB doesn't match what the bank's Direct Connect server requires. Some banks use a separate Direct Connect PIN from the website password. Contact your bank to confirm the correct Direct Connect credentials.

Corrupted Bank Feed Setup in Company File

The bank feed configuration for the specific account in the company file has become corrupted — the stored authentication data is invalid even though the credentials themselves are correct. This is confirmed by the test company file method: if a fresh setup works with the same credentials, the existing company file's bank feed setup is the issue. The copy-and-merge fix rebuilds it cleanly.

Bank Has Pending Alerts Requiring Acknowledgment

Some banks block Direct Connect access until you log into their website and acknowledge security alerts, updated terms of service, or new security prompts. QB receives OL-332 until the alert is cleared. Log into your bank's website → check and acknowledge any notifications → retry the bank feed download in QB.

Bank Account Not Enabled for Direct Connect

The specific account in QB is either not enabled for online banking or the bank changed the account to Web Connect only (vs. Direct Connect). QB attempts a Direct Connect authentication, the bank returns OL-332 because Direct Connect isn't authorized for this account. Switch to Web Connect in QB's bank feed settings if the bank uses it.

Inactive Bank Account Still Linked in QB

A closed or dormant bank account is still linked in QB's Chart of Accounts with online banking active. When QB attempts to download transactions for this inactive account, the bank returns OL-332. Deactivate online services for all inactive/closed accounts: Chart of Accounts → find accounts with lightning bolt icons → edit each → Bank Feed Settings → Deactivate All Online Services.

Downloaded Bank File Not Compatible with QB

If using Web Connect (manual .QBO import) rather than Direct Connect, OL-332 can appear if the downloaded .QBO file from your bank doesn't comply with QB's expected format or contains data QB can't parse. Verify the file is in .QBO format (not CSV or OFX) and download it fresh from the bank's website.

How to Fix QuickBooks Error OL-332

Run the test company file first to determine whether the issue is in your company file or at the bank's server — the fix path is completely different for each.

METHOD 1 Test Company File Diagnostic + Check Bank Website Always do this first — identifies the source
1

Create test company file: QB → File → New Company → Express Start → minimal info → Banking → Bank Feeds → Set Up Bank Feeds for Account → add your bank → enter credentials → try downloading. Result determines your fix path (see the distinction box above).

2

Check bank website first: log into your bank → check for notifications (security prompts, terms updates, account alerts). Acknowledge any pending alerts → return to QB and retry. Also verify your bank account is still active for online banking and that the credentials you're using are correct.

METHOD 2 Copy and Merge the Affected Bank Account Test file worked — company file setup is corrupted
1

Lists → Chart of Accounts → right-click the affected account → Edit Account → copy the account name. Add an asterisk (*) to the end of the name (e.g., "Business Checking*"). Click Bank Feed Settings → Deactivate All Online Services → OK → Save & Close. This effectively deactivates the corrupted bank feed setup.

2

Create a new account in Chart of Accounts with the original name (without the asterisk). Close and reopen the company file. Now set up bank feeds fresh for the new account: Banking → Bank Feeds → Set Up Bank Feed for Account → select the new account → enter credentials → connect. Test the download — it should work without OL-332.

3

Once bank feeds work on the new account → merge the asterisked account back in: find the asterisked account in Chart of Accounts → right-click → Edit → remove the asterisk from the name → Save & Close → QB will ask if you want to merge → click Yes. All transaction history consolidates into the clean account.

METHOD 3 Deactivate Inactive Accounts + Check TLS Settings Inactive linked accounts or security settings
1

Deactivate inactive accounts: Chart of Accounts → check "Include inactive" → find any accounts with a lightning bolt icon that are closed/inactive → right-click → Edit Account → Bank Feed Settings → Deactivate All Online Services → Save & Close. Do this for all inactive bank accounts.

2

Check TLS settings: INETCPL.CPL → Advanced → Security → ensure TLS 1.2 is checked. QB uses IE security settings for bank connections. Also: in QB → Edit → Preferences → Checking → Company Preferences → verify Bank Feeds mode is set to Express mode (not Classic) for most modern banks.

METHOD 4 Contact Bank with Bank Feeds Log Test file also failed — bank server is the issue
1

If the test company file also showed OL-332: collect your Bank Feeds log (in QB, go to Help → Send Feedback Online → Include diagnostic files, or find logs at C:\Users\[user]\AppData\Local\Intuit\QuickBooks\log) → contact your bank's technical support → provide the log showing the OL-332 error → ask them to check their Direct Connect server for issues with your account. Also update QB (Help → Update QB Desktop) to ensure the Financial Institutions Directory is current.

Quick Reference

Test ResultSourceFix
Test file downloads OK, main file gets OL-332Company file bank feed corruptedMethod 2 — copy and merge account
Test file also gets OL-332Bank server issueMethod 4 — contact bank with log
Bank website has pending alertUnacknowledged notificationAcknowledge on bank website, retry
Multiple bank accounts showing OL-332Inactive accounts or TLS settingsMethod 3 — deactivate inactive, check TLS

Frequently Asked Questions

What is a Direct Connect PIN and why is it different from my bank website password?
Some banks use a separate authentication system for Direct Connect (the technology QB uses to automatically download transactions) that is distinct from the username and password you use on their website. The Direct Connect PIN is typically a 4–8 digit number or a separate password that the bank provides specifically for use with financial management software like QuickBooks. If your website credentials work but QB shows OL-332, contact your bank and specifically ask: "What credentials do I use for QuickBooks Direct Connect?" — they may need to activate Direct Connect separately for your account and provide you with a specific PIN.
Will the copy-and-merge fix delete any of my transaction history?
No. The copy-and-merge process preserves all transaction history. What happens: the asterisked version of the account (with the deactivated, corrupted bank feed) retains all the transaction history. When you create the new clean account and set up fresh bank feeds, it initially has no transactions. But when you merge the asterisked account back into the new one (by removing the asterisk), QB combines all the transaction history from both accounts into the single merged account. You end up with one account containing all your original transaction history plus new clean bank feed functionality. Always back up your company file before starting this process as a precaution.

Related QuickBooks Errors

Error OL-332 Persisting After Copy-and-Merge?

Let QuickFix Bookkeeping Restore Your Bank Feeds.

Persistent OL-332 after the copy-and-merge fix typically means the bank's Direct Connect credentials need updating, or the bank requires activation of Direct Connect on their end — our ProAdvisors can diagnose which and coordinate with your bank.

Book a Free 30-Minute Consultation

No obligation. Same-day response.