QuickBooks® Error OL-222: Bank Feed Connection Failed
Quick Answer:
Error OL-222 occurs when QuickBooks® cannot authenticate with your bank due to expired or incorrect login credentials. Fix it by deactivating the bank account, updating your bank login password, and reauthorizing the connection.
What is QuickBooks® Error OL-222?
QuickBooks® Error OL-222 is an online banking authentication error that prevents QuickBooks® from connecting to your financial institution to download transactions. This error indicates that your bank login credentials are expired, incorrect, or the account authorization has been revoked, blocking QuickBooks® from accessing your bank account data.
Error OL-222: Bank feed connection failed - authentication error
QuickBooks® cannot authenticate with your bank due to credential or authorization issues.
Symptoms:
- Error OL-222 when downloading bank transactions
- Bank feed sync fails repeatedly
- Cannot connect to bank for online banking
- Message about invalid credentials or authorization
- Bank transactions not updating in QuickBooks®
Resolution Steps:
- 1.Deactivate bank account in QuickBooks®
- 2.Update bank login password if changed
- 3.Reauthorize bank account connection
- 4.Test bank feed to verify fix
Workflow map
Re-authenticate the account, in this order
OL-222 is an authentication failure, so the credentials are proved at the bank before anything inside QuickBooks® is changed. Each step leaves behind evidence that the next step can rely on.
- 1
Prove the credentials
Sign in at the bank website itself with the username and password QuickBooks® is using, and reset the password there if it fails.
Evidence: A successful bank-website sign-in, and the exact case-sensitive username written down.
- 2
Deactivate the feed
Banking → Bank Feeds → Bank Feeds Center, then right-click the affected account and deactivate it. This clears the stored credentials, not your transactions.
Evidence: The account no longer appears in Bank Feeds Center; its register and history are untouched.
- 3
Reconnect and remap
Banking → Set Up Bank Feeds for an Account, complete any security questions or one-time codes, and map to the same QuickBooks® account you used before.
Evidence: The bank account is linked to the original chart-of-accounts account, not a newly created one.
- 4
Download to confirm
Right-click the reconnected account and download transactions, then check that nothing arrived twice.
Evidence: Transactions download with no OL-222, and past reconciliations still balance.
First Checks for Error OL-222
Start here
- In QuickBooks®: Banking → Bank Feeds → Bank Feeds Center
- Find the affected account → Right-click → Deactivate
- Confirm deactivation → Yes
- Verify your bank login credentials at your bank's website
- Banking → Set Up Bank Feeds for an Account
- Search for your bank → Follow prompts to reconnect
- Enter current bank username/password → Authorize
- Download transactions to test - error should be resolved
Detailed Solution Steps
- Verify Your Bank Login Credentials.
Before changing settings in QuickBooks®, verify your bank credentials:
- Open your bank's website in a web browser
- Attempt to log in with your username and password
- If login fails, reset your password on the bank website
- If login succeeds, note your exact username (case-sensitive)
- Check for any security questions or 2FA requirements
- Verify your account is active and not locked
Important: If you recently changed your bank password for security reasons, that's likely the cause of Error OL-222. You must update it in QuickBooks®.
- Deactivate the Bank Account Connection.
Remove the old bank connection in QuickBooks®:
- Open QuickBooks® Desktop
- Go to Banking → Bank Feeds → Bank Feeds Center
- Locate the account showing Error OL-222
- Right-click on the account name
- Select "Deactivate Bank Feeds"
- When prompted, click "Yes" to confirm
- QuickBooks® will deactivate the connection
What This Does
Deactivating removes the old authentication credentials and connection settings. This allows you to create a fresh connection with updated credentials without conflicts. - Clear QuickBooks® Banking Cache (Optional but Recommended).
Clear cached bank data to ensure clean reconnection:
- Close QuickBooks® completely
- Press Windows key + R
- Type:
%appdata%and press Enter - Navigate to: Intuit → QuickBooks® → Company Files
- Find folder matching your company file name
- Locate and delete these files (if present):
- ecml files (entitlement cache)
- *.olb files (online banking cache)
- Restart QuickBooks®
Note: Deleting these cache files is safe - they only contain temporary banking connection data, not your transactions or financial data.
- Reconnect Your Bank Account.
Set up fresh bank feed connection with current credentials:
- In QuickBooks®: Banking → Bank Feeds → Set Up Bank Feeds for an Account
- In the search box, type your bank name
- Select your bank from the list → Click "Next"
- Enter your bank login credentials:
- Username (exactly as you log in to bank website)
- Password (current password)
- Complete any security questions or 2FA if prompted
- When connected, select the account(s) to link
- Match each bank account to the correct QuickBooks® account
- Click "Finish" to complete setup
Account Mapping:
Make sure to map to the SAME QuickBooks® account you were using before. This preserves your transaction history and account reconciliation. - Handle Multi-Factor Authentication.
If your bank uses 2FA/MFA, follow these steps:
- During bank setup, QuickBooks® will prompt for authentication code
- Check your phone/email for code from your bank
- Enter the code in QuickBooks® within the time limit (usually 5-10 minutes)
- Some banks require you to mark QuickBooks® as "trusted device"
- If code expires, restart the connection process
2FA Challenges
Some banks have strict 2FA that expires quickly or doesn't work well with QuickBooks®. If you continue having issues, contact your bank to ensure QuickBooks® is whitelisted for data access. - Test the Bank Feed Connection.
Verify Error OL-222 is resolved:
- Go to Banking → Bank Feeds → Bank Feeds Center
- Locate your reconnected account
- Right-click → Download Transactions
- Wait for download to complete
- Verify transactions appear in Bank Feeds Center
- If successful, Error OL-222 is resolved
- You can now add/match transactions normally
Why Does Error OL-222 Occur?
Common Causes
- Changed Bank Password: You changed your bank password on the bank website but didn't update it in QuickBooks®
- Expired Credentials: Bank forced password reset due to security policy (common after 90-180 days)
- Revoked Authorization: You or your bank revoked QuickBooks®' access to your account data
- Account Locked: Bank locked your account due to suspicious activity or too many failed login attempts
- Changed Username: Bank changed your username or account number format
- Bank Security Update: Bank updated security requirements (new 2FA, security questions, etc.)
- Cached Credentials: QuickBooks® using old cached credentials that no longer work
How to Prevent Error OL-222
Best Practices:
- Update bank credentials in QuickBooks® immediately after changing your bank password
- Download bank transactions regularly (daily or weekly) to catch connection issues early
- Maintain consistent bank username - avoid changing it if possible
- Whitelist QuickBooks® in your bank's third-party app permissions
- Keep QuickBooks® updated - bank connection protocols change regularly
Frequently Asked Questions
What causes QuickBooks® Error OL-222?
Error OL-222 occurs when QuickBooks® cannot authenticate with your bank due to expired login credentials, changed bank passwords, account authorization issues, or bank server maintenance blocking the connection.
What is the difference between OL-222 and OL-334?
OL-222 indicates authentication/credential issues (your username/password problem). OL-334 indicates the bank server is temporarily unavailable or under maintenance (bank's problem). OL-222 requires updating credentials, while OL-334 requires waiting for the bank server.
Will deactivating bank feeds delete my transactions?
No, deactivating bank feeds only removes the connection to your bank. Your existing transactions, reconciliations, and account registers remain intact. You're simply removing the sync connection to set it up fresh.
Can I use QuickBooks® without bank feeds?
Yes, QuickBooks® works perfectly without bank feeds. You can manually enter transactions or import them from downloaded bank files (QBO, OFX, CSV). Bank feeds are a convenience feature, not required.
Why does my bank keep requiring 2FA for QuickBooks®?
Some banks require periodic re-authentication for security. This is normal. You may need to re-enter codes every 30-90 days. Check your bank's settings to mark QuickBooks® as a "trusted application" to reduce 2FA prompts.
Related Resources
Need Professional Help?
If you're still experiencing Error OL-222 after following these steps, or need help with bank feed configuration, our QuickBooks® banking specialists are here to help.
Get Expert Support