If you manage business or personal bookkeeping using QuickBooks Online, Quicken, Mint, YNAB, or any financial dashboard powered by Plaid, seeing your Bank of America feeds abruptly fail with Error 350, Error 102, or "Bank Connection Needs Attention" brings payroll and reconciliation to a grinding halt.
Transactions stop syncing, account balances fall out of date, and clicking "Update" simply throws you back into an endless credential loop.
Your banking data has not been lost, and your accounts have not been unlinked. This error is almost always caused by an expired OAuth security token mandated by Bank of America's Open Banking API protocol.
Why Do QuickBooks and Plaid Throw Error 350 with Bank of America?
QuickBooks Error 350 indicates that Bank of America's Open Banking API has revoked the third-party authorization token because it expired, exceeded its cryptographic refresh window, or was blocked by a multi-factor SafePass challenge.
| Error Code | Primary Aggregator | Root Technical Cause |
|---|---|---|
| Error 350 | QuickBooks Online / Intuit | OAuth 2.0 token expired; requires interactive re-consent handshake |
| Error 102 | QuickBooks Online / Desktop | Bank of America core banking maintenance blackout during batch sync |
| Plaid ITEM_LOGIN_REQUIRED | Venmo, Robinhood, YNAB | SafePass two-factor challenge triggered by new aggregator IP address |
| Error 103 | Quicken / QuickBooks | Invalid credentials entered or account locked due to too many sync attempts |
In compliance with financial data privacy standards, Bank of America no longer allows third-party financial apps to store your raw Online ID and password (screen-scraping). Instead, it uses direct Financial Data Exchange (FDX) APIs. These direct connections automatically expire every 90 to 180 days, requiring business owners to re-authenticate.
4 Steps to Resolve Error 350 & Restore Transaction Feeds
1. Perform an Interactive OAuth Re-Authorization in QuickBooks
Do not click the basic "Update" button, which simply retries the dead token. You must force a full re-authorization handshake:
- Log into QuickBooks Online on a desktop web browser.
- In the left navigation menu, go to Transactions (or Bookkeeping) > Bank transactions.
- Select your Bank of America account tile displaying the error alert.
- Click the link that says Sign in to Bank of America (or Update credentials / Reconnect).
- A secure Bank of America pop-up window will open directly to
secure.bankofamerica.com. - Enter your Online ID and Password.
- Complete the SafePass Two-Factor Authentication prompt via text or app.
- On the consent authorization screen, ensure the checkboxes for all your relevant checking, savings, and credit card accounts are checked.
- Click Authorize & Connect. QuickBooks will refresh and begin downloading all queued transactions.
2. Verify Connected Apps Inside Bank of America Security Center
If the re-authentication pop-up closes with an error or fails to link:
- Open a new browser tab and log into Bank of America Online Banking.
- Go to Profile & Settings > Security Center.
- Scroll down to the section titled Third-Party Connected Apps (or Data Sharing Permissions).
- Locate Intuit / QuickBooks or Plaid on the list.
- If the connection shows as Inactive, Expired, or Blocked, click Manage Access and toggle permissions to Allow.
- If the connection is corrupted, click Remove Access, then return to QuickBooks and establish a fresh connection from scratch.
💡 Related Bank of America Solution: Encountering related issues? Check our verified fix for Bank of America Zelle Error 'Your Mobile Number or Email Can't Be Used': Complete Fix.
3. Handle Duplicate Transaction Overlaps During Sync
After resolving Error 350, QuickBooks will attempt to backfill missing days:
- Check the date of the last reconciled transaction before Error 350 occurred.
- If QuickBooks pulls in transactions that you already manually entered while the feed was broken, do not delete them. Go to the For Review tab, select the duplicates, and click Exclude to keep your ledger balanced.
4. Bypass Intuit Server Maintenance Delays (Error 102)
If you are seeing Error 102 instead of Error 350:
- Error 102 is an indicator of overnight maintenance between Bank of America's data export servers and Intuit's ingestion pipelines.
- It typically occurs between 12:00 AM and 4:00 AM ET.
- Do not disconnect your account during Error 102. Wait until business hours (after 9:00 AM ET) and click Update once; the connection normally self-heals without re-entering passwords.
Frequently Asked Questions (FAQ)
Will disconnecting and reconnecting Bank of America delete my historical bookkeeping? No. Re-authorizing or reconnecting the bank feed does not delete transactions that have already been categorized, approved, and added to your QuickBooks register. It only refreshes the data pipeline for new, unreviewed transactions.
Why does Bank of America disconnect from QuickBooks every few months? Under modern Open Banking security protocols, Bank of America mandates that third-party data sharing consents expire periodically to protect account holders from zombie connections continuing to access financial records after third-party software is abandoned.
Can secondary users or bookkeepers re-authorize the connection? Only the primary account owner or an authorized user with administrative digital banking credentials can authorize the SafePass verification handshake with Bank of America.