Problem Overview
This error occurs when QuickBooks temporarily loses connection to your bank's servers. This is typically a temporary network issue that resolves automatically, but can also indicate problems with your internet connection or bank server maintenance.
Common Symptoms
- Bank feed updates fail
- Intermittent connection drops
- Slow bank data retrieval
- Connection timeouts
- Temporary service unavailability
Connection Components
- Internet connectivity
- Bank server availability
- Network routing
- DNS resolution
- Firewall and security settings
Quick Resolution
- Wait and retry connection
- Check internet connectivity
- Restart router/modem
- Verify bank server status
- Clear network cache
Step-by-Step Solution
Most Error 350 occurrences are temporary and resolve automatically within minutes.
- Wait 5-10 minutes before taking any action
- Check if the error resolves on its own
- Try refreshing the bank feed connection
- If still failing, proceed to network troubleshooting
- Many bank connections experience brief interruptions during maintenance
- Peak usage times may cause temporary server overload
Note: Error 350 is designed to be temporary. QuickBooks will automatically retry the connection. If the error persists for more than 30 minutes, then proceed with additional troubleshooting steps.
Verify your local internet connection is stable and functioning properly.
- Test your internet connection by visiting other websites
- Check if other internet-dependent applications are working
- Run a speed test at speedtest.net
- Look for consistent download/upload speeds
- Check for packet loss by pinging google.com
- Verify WiFi signal strength if using wireless connection
// To test internet connection in Command Prompt:
ping google.com -t
// Look for consistent response times
// No "Request timed out" messages
// Low packet loss (less than 1%)
Power cycle your modem and router to refresh network connections.
- Shut down QuickBooks and save your work
- Turn off your computer
- Unplug your modem and router from power
- Wait 30 seconds for complete power drainage
- Plug in the modem first and wait for all lights to stabilize
- Then plug in the router and wait for full startup
- Restart your computer and test the connection
Success Tip: Power cycling network equipment clears temporary glitches, resets connection tables, and often resolves intermittent connectivity issues that cause Error 350.
Verify if your bank is experiencing server issues or maintenance.
- Visit your bank's website directly
- Check if online banking is accessible
- Look for maintenance announcements or status pages
- Check Intuit's bank status page for known issues
- Contact your bank's customer service if unsure
- Search online for "[Your Bank Name] server status"
Important: Banks frequently perform maintenance during off-peak hours (evenings, weekends, early mornings). If the connection fails during these times, it's likely scheduled maintenance that will resolve automatically.
Clear temporary network files and reset the bank connection in QuickBooks.
- In QuickBooks, go to Banking > Bank Feeds
- Select Update Accounts to force a refresh
- If that fails, go to Banking > Bank Feeds Center
- Select your bank and click Disconnect
- Wait a few minutes, then reconnect the account
- Clear DNS cache by opening Command Prompt as Admin and typing:
ipconfig /flushdns
Note: Sometimes QuickBooks caches old connection data that can cause conflicts. Disconnecting and reconnecting the bank account forces a fresh connection attempt with current network conditions.
Connection Management Guide
Network Optimization
Stable connections, wired vs wireless, bandwidth management, and router configuration for reliable bank feeds.
Server Awareness
Bank maintenance schedules, peak usage times, server status monitoring, and alternative connection methods.
Connection Management
Automatic retry settings, manual refresh procedures, connection reset methods, and cache management.
Timing Strategies
Optimal update times, maintenance avoidance, peak hour management, and scheduled update planning.
Frequently Asked Questions
How long should I wait before taking action on Error 350?
For Error 350, wait 15-30 minutes before extensive troubleshooting. Most temporary connection issues resolve within this timeframe. QuickBooks automatically retries connections every few minutes. If the error persists beyond 30 minutes, then proceed with network troubleshooting. However, if you're in the middle of time-sensitive work, you can begin basic checks (internet connectivity, bank website access) immediately while waiting for automatic resolution.
Can I prevent Error 350 from occurring frequently?
While you can't prevent all occurrences, you can reduce frequency by: 1) Using wired Ethernet instead of WiFi for stability, 2) Scheduling bank updates during off-peak hours (early morning or late evening), 3) Keeping your router firmware updated, 4) Using a business-grade internet connection with better reliability, 5) Avoiding bank updates during known maintenance windows, 6) Regularly restarting network equipment to prevent memory leaks or connection table issues.
Is Error 350 different from other bank connection errors?
Yes, Error 350 is specifically designed for temporary, self-resolving connection issues. Unlike credential errors (103) or security blocks (108), Error 350 indicates the connection was working but temporarily dropped. QuickBooks will automatically retry these connections. Other errors typically require user intervention. Error 350 is the most common and usually least concerning bank connection error.
Should I be concerned about data loss with Error 350?
No, Error 350 does not cause data loss. The error occurs during the connection attempt to retrieve new transactions, not during data processing. Your existing QuickBooks data remains safe. When the connection is restored, QuickBooks will retrieve any transactions that occurred during the outage. The bank maintains complete transaction records, so no data is permanently lost due to temporary connection drops.