Express Web Connect+ in QuickBooks: Why Your Bank Reconnects

Express Web Connect+ (EWC+) is Intuit's newer, token-based bank feed connection. Instead of storing your online banking password and logging in on your behalf (what plain Express Web Connect does), QuickBooks sends you to your bank's own site, you authorize the connection there, and the bank hands back a security token. That token, not your password, pulls the transactions. When an institution is moved onto EWC+, existing feeds usually have to be re-authorized, which is why a working connection suddenly shows an 'action needed' banner and stops importing.

Last updated July 2026.

The four ways QuickBooks gets bank data

Most bank feed problems make sense once you know which of these four routes your account is on. Intuit's financial data documentation lists Direct Connect, aggregation (Express Web Connect) and Web Connect as separate connectivity types. The token-based EWC+ flow sits on the aggregation side.

Why is Intuit moving banks to Express Web Connect+?

Because the old model is fragile and banks want it gone. Screen-scraped Express Web Connect requires a third party to hold your live banking password, and every MFA change or login redesign can snap the feed. A token lets the bank see exactly which accounts you shared and with what app, and lets you revoke access without changing your password.

That is the security story, and it is a real one. The practical story is less tidy. Migrations happen institution by institution, on the bank's schedule. When your bank's turn comes, the old connection is retired and a new one is stood up, and anything that depended on the old plumbing (the account link, the last download date, sometimes the institution's entry in the search list) gets rebuilt.

"Why does QuickBooks keep asking me to reconnect my bank?"

Two reasons. Either your institution was migrated to a token-based connection and the old link no longer works, or the token you already granted has aged out. Intuit's guidance on bank error 350 says the connection can expire and that, depending on the bank, you may need to reconnect roughly every 90 business days or as rarely as every 18 months.

So it isn't only a migration thing. Periodic re-authorization is baked into how these connections work. The bank sets the lifetime of the consent it granted, and when that consent lapses QuickBooks can't pull transactions until a human signs in at the bank and approves it again. Error 350 is the one you'll see most ("to sync your accounts again, you'll need to reconnect"). Errors 103 and 324 also cluster around migrations, since account identifiers on the bank side can change when the connection method does. Our guide to QuickBooks bank feed error codes walks through each one.

One more trap: when several QuickBooks companies share one set of online banking credentials, reconnections knock each other over. Intuit's advice is to let one designated person handle the reconnect.

"My bank disappeared from the QuickBooks bank list"

This happens around a core-system change or a connection-method switch. The tile vanishes from search, or the name you always used is now slightly different with a new logo. Your data is fine. It means QuickBooks currently has no live connection profile for that institution.

Search by the bank's full legal name and by its login URL, not just the name on your debit card, since institutions are often listed under a holding company or a post-merger brand. Credit unions are the worst offenders here: see our page on getting a credit union statement into QuickBooks. If the institution genuinely isn't listed, no setting will summon it back. Import from a file until the connection returns.

"I reconnected and now I have duplicate transactions"

Very common after a migration. A new connection often pulls a fresh window of history (typically the last 90 days), and if those transactions already came in under the old connection, you get two of each in the review queue.

Handle it in the For Review tab before you accept anything. Sort by date, find the overlap window, and exclude the duplicates rather than deleting posted transactions from the register. If some already slipped into the books, work through fixing duplicate bank transactions in QuickBooks. The mirror-image failure is just as common: the new connection starts at the switch date and quietly skips a week. Reconcile before you trust a feed, especially right after a reconnect.

"Does QuickBooks Desktop support Express Web Connect+?"

Intuit's public documentation is not clear on this, so treat any confident answer with suspicion. What Intuit does document plainly: Direct Connect and Web Connect are the Desktop routes, aggregation-style connections are described as a QuickBooks Online, Credit Karma and Quicken feature, and Desktop users at some banks are told to "refresh" an Express Web Connect connection when bank feeds are upgraded.

The practical reading: on Desktop, your two dependable routes are Direct Connect (if the bank still offers it, enrolled on the bank's side) and a .qbo Web Connect import. Desktop's Web Connect import will not take a CSV or a QFX. It reads .qbo and nothing else. We compare the two in Direct Connect vs Web Connect.

What to do when the feed is down mid-migration

You can't hurry a migration, but you can stop it holding up your close. The order of operations that works.

• Read the banner, then act on it. If QuickBooks shows an "action needed" or reconnect prompt, run it. You'll be bounced to the bank's site to sign in and approve accounts. Approve every account you need, not just checking.
• Relink, don't re-add. Point each bank account at the existing QuickBooks register. Creating a second register is how people end up with a split ledger and two years of history in the wrong place.
• Check the date range it pulled. Compare the earliest new transaction against your last reconciled date. Gaps and overlaps are both normal after a switch.
• If it's still broken after 24 to 48 hours, stop waiting. Bank-side outages clear on their own. Migrations have no published ETA, and neither does an institution that has fallen off the list.

That last point is where the file route earns its keep. Every bank still issues a statement, and a statement is a complete, final record of the period. Convert the statement PDF into a .qbo Web Connect file and import it, and QuickBooks treats those transactions the way it treats fed ones: they land in For Review, rules fire, matching works. Same import path a downloaded bank file uses, which is why it keeps working when the feed doesn't. Our QBO converter takes PDF and image statements only, and a PDF is the one thing every institution still hands you.

Two details to keep straight. QuickBooks Online's manual "Upload from file" option accepts QBO, QFX and CSV, with limits of 350KB and 1,000 lines per upload, so long statements need splitting. In Desktop, Web Connect means .qbo, full stop. If your institution hands you an OFX file instead, you can turn the statement PDF into an OFX file for whatever software expects that format. For the mechanics, see what a .qbo file actually is.

Is Express Web Connect+ actually better?

For security, yes, and it is where the industry is heading. Your password stops living on someone else's server and you can revoke access from the bank's dashboard. For day-to-day reliability, it depends on how well your bank implemented it. A token connection breaks in fewer ways than a screen scraper, but its failures need a human to log in and click Approve, and they tend to land at month end.

Assume you will re-authorize once or twice a year per institution, assume a migration costs an afternoon of cleanup, and keep the manual import path handy so a broken feed never becomes a late close. For broader triage, start with bank feed not working in QuickBooks.

Frequently asked questions

Is Express Web Connect+ the same as Web Connect?

No, and the names are unhelpfully similar. Express Web Connect+ is an automatic feed that uses a token you approve at your bank. Web Connect is a manual file import: you download a .qbo file and bring it into QuickBooks yourself. One is a live connection, the other is a file. Different things entirely.

How often will I have to re-authorize an Express Web Connect+ bank?

It depends on the institution, and Intuit doesn't publish a single number. Its bank error 350 guidance says a connection can expire and that some banks want a reconnect roughly every 90 business days while others go as long as 18 months. Plan on doing it periodically rather than never.

Will I lose my transaction history when my bank is migrated?

Your posted QuickBooks transactions stay put. What changes is the connection and, sometimes, the date range the new feed pulls. Expect either an overlap (duplicates in For Review) or a gap. Compare the first new transaction to your last reconciled date before you accept anything.

Can I just import the statement while the connection is down?

Yes, and it is usually the fastest way out. Download the statement PDF, convert it to a .qbo Web Connect file, and import it. The transactions arrive in the same review queue the feed uses, so rules and matching behave normally. When the feed returns, watch the overlap window for duplicates.

Does re-authorizing give a third party access to my bank account?

The point of the token model is that it doesn't hand over your password. You approve specific accounts at your bank's own site, the bank issues a revocable token, and you can withdraw that access later from the bank's side. Read-only transaction access is what the feed needs.