You open QuickBooks® Desktop, go to download your latest bank transactions, and instead of a smooth sync you get QuickBooks® Error OL-222. The bank feed stops working, transactions aren't downloading, and your books are falling behind. This error is one of the most common online banking issues in QuickBooks® Desktop, and it's almost always fixable without losing any data.
Please try again later. If the problem persists, contact your financial institution.
Error OL-222 means the connection between QuickBooks® and your bank has been disrupted. It doesn't mean there's anything wrong with your bank account itself or your QuickBooks® data — it's purely a connectivity issue between the two systems.
What Causes QuickBooks® Error OL-222?
Bank feeds in QuickBooks® Desktop work through a technology called OFX (Open Financial Exchange). QuickBooks® sends a request to your bank's OFX server, and the bank sends back your recent transactions. Error OL-222 appears when this communication breaks down.
- Your bank changed their connection platform — Banks periodically migrate to new data sharing systems. When this happens, existing QuickBooks® connections break because the old connection path no longer works. This is the most common cause and typically affects many users at the same bank simultaneously.
- Password or credentials changed — If you recently changed your online banking password, set up multi-factor authentication, or accepted new terms and conditions at your bank's website, the credentials stored in QuickBooks® are now outdated.
- Bank server maintenance — Your bank's OFX server may be temporarily down for maintenance or experiencing technical issues. This is usually resolved within a few hours to a day.
- Expired connection token — The authentication token that links QuickBooks® to your bank has a limited lifespan. When it expires, QuickBooks® can no longer authenticate with the bank.
- SSL/TLS certificate issues — QuickBooks® uses encrypted connections to communicate with banks. If your computer's SSL certificates are outdated or the bank upgraded their security requirements, the secure connection fails.
- QuickBooks® software is outdated — Banks update their systems regularly, and older versions of QuickBooks® may not support the latest connection methods. This is especially common if you haven't updated QuickBooks® in several months.
5-Step Fix for QuickBooks® Error OL-222
⚠️ Before starting: Log into your bank's website directly (not through QuickBooks®) and confirm your account is active, your password works, and there are no pending security prompts or terms to accept. Sometimes the fix is as simple as completing a verification step on your bank's website.
1 Update QuickBooks® to the Latest Version
Banks frequently update their connection systems, and Intuit releases QuickBooks® patches to maintain compatibility. An outdated QuickBooks® version is often the simplest explanation for a suddenly broken bank feed.
- Open QuickBooks® Desktop
- Go to Help → Update QuickBooks Desktop
- Click the "Update Now" tab
- Check "Reset Update" and click "Get Updates"
- Wait for the update to download and install
- Restart QuickBooks® and try downloading bank transactions again
2 Deactivate and Reactivate Bank Feed
This is the most effective fix for Error OL-222. It destroys the old connection and creates a completely fresh one.
- Go to Banking → Bank Feeds → Bank Feeds Center
- Select the affected bank account
- Click "Deactivate All Online Services" for that account
- Confirm the deactivation
- Wait at least 24 hours — this is important because the bank's system needs time to fully disconnect the old session
- After 24 hours, go back to Banking → Bank Feeds → Set Up Bank Feed for Account
- Search for your bank and reconnect using your current login credentials
- Follow the prompts to link the bank feed to the correct QuickBooks® account
The 24-hour wait is critical. Many users try to reconnect immediately and get the same error because the bank's system hasn't fully cleared the old connection yet.
3 Switch Connection Method (Direct Connect vs Express Web Connect)
QuickBooks® offers multiple ways to connect to banks. If your current method is failing, switching to an alternative often resolves OL-222:
- When reactivating (Step 2), look for the connection method options
- If you were using Direct Connect, try Express Web Connect instead (or vice versa)
- Direct Connect communicates directly with the bank's OFX server — it's more reliable but requires the bank to support it and sometimes has a monthly fee
- Express Web Connect goes through Intuit's intermediary servers — it's free and works with more banks but can be slower
4 Reset the Online Banking Connection
If deactivating and reactivating didn't work, a deeper reset may be needed:
- Close QuickBooks® completely
- Log into your bank's website directly in your browser
- Look for a section like "Connected Apps," "Third-Party Access," or "Account Aggregation" in your bank's settings
- Revoke or disconnect the QuickBooks® / Intuit connection from the bank's side
- Log out of the bank website
- Open QuickBooks® and set up the bank feed from scratch as if connecting for the first time
Disconnecting from the bank's side ensures both ends of the connection are fully cleared before you establish a new one.
5 Use Web Connect as a Temporary Workaround
If automated bank feeds aren't cooperating, you can manually import transactions while you wait for the connection issue to resolve:
- Log into your bank's website
- Navigate to your account's transaction history or download section
- Download transactions in .QBO format (QuickBooks Web Connect format) — most banks offer this option
- In QuickBooks®, go to File → Utilities → Import → Web Connect Files
- Select the downloaded .QBO file
- Map it to the correct bank account in QuickBooks®
- Review and accept the imported transactions
This gets your books current while you resolve the automated connection. Once the bank feed is working again, transactions you've already imported won't be duplicated — QuickBooks® checks for this automatically.
Bank Feed Still Not Connecting?
Some bank feed issues involve bank-side configuration changes that require specific troubleshooting. Our independent technicians can diagnose the exact cause remotely.
📞 Call +1-888-550-4779 — Free DiagnosisOL-222 vs OL-301 vs OL-332: Understanding QuickBooks® Banking Errors
QuickBooks® has several OL-series banking errors, each pointing to a slightly different issue. Error OL-222 is a general "cannot connect to bank" error — the broadest category. Error OL-301 typically means the bank requires you to complete an action on their website first (accept new terms, verify identity, update security settings). Error OL-332 means the bank rejected the connection request outright, often because your credentials are wrong or your account is locked.
For all three errors, the fix starts with Steps 1 and 2 above. If you're seeing OL-301, make sure to log into your bank's website directly and complete any pending prompts before trying to reconnect in QuickBooks®.
Keeping Your Bank Feeds Healthy
Maintenance Tips
- Update QuickBooks® monthly — Bank connection patches are included in regular updates.
- Download transactions weekly — Connections that sit idle too long are more likely to break. Regular use keeps them fresh.
- Update bank credentials in QuickBooks® immediately after changing your password — Don't wait until the feed breaks.
- Check your bank's website for maintenance notices — Banks usually announce planned outages in advance.
- Keep one .QBO file download as a backup — If automated feeds break at a critical time (month-end, tax season), you can import manually.
- Monitor Intuit's bank feed status page — Intuit maintains a page listing known bank connection issues across all institutions.
Frequently Asked Questions
QuickBooks Error OL-222 is an online banking error that appears when QuickBooks Desktop cannot connect to your bank's servers to download transactions. The connection between QuickBooks and your bank has been disrupted — your data is safe, and the issue is purely about connectivity between the two systems.
Bank feeds can stop working when your bank changes their data sharing platform, your password was recently changed, your bank is doing server maintenance, or the connection token between QuickBooks and your bank has expired. Multi-factor authentication changes at your bank can also break existing connections.
No. Error OL-222 only affects the download connection. All transactions already in QuickBooks are safe. Once you fix the connection, QuickBooks will download any transactions that occurred during the disconnection period. No data is lost.
Go to Banking → Bank Feeds → Deactivate Bank Feeds for the affected account. Wait 24 hours, then go back and set up the bank feed again with your current login credentials. The 24-hour wait is important to let the bank fully clear the old connection.
QuickBooks Online uses a different banking connection system. While QBO can have its own bank feed issues, the specific OL-222 error code is exclusive to QuickBooks Desktop. QBO users see different error messages for similar problems.
Not all banks support direct QuickBooks connectivity. Check if your bank offers Web Connect (.QBO file) downloads from their online banking portal. You can manually import these into QuickBooks through File → Utilities → Import → Web Connect Files. Some smaller banks and credit unions may not support any QuickBooks connectivity.
Need Help with QuickBooks® Banking Issues?
Our independent technicians resolve bank feed errors remotely. Free diagnosis on every call.
📞 Call +1-888-550-4779 — Free Diagnosis⚠️ Disclaimer: InstantDesk Support is an independent, third-party technical support provider. We are not affiliated with Intuit Inc., QuickBooks®, or any financial institution. For free official support, visit quickbooks.intuit.com. For bank-specific issues, contact your bank directly.