Hello,

I am opening this discussion to formally report a system-wide regression in QuickBooks Online bank connectivity affecting all major financial institutions.

Until recently, QuickBooks Online allowed linking to multiple accounts at the same bank when those accounts used different login credentials; or example, a personal checking account under one username and a business checking account under another.

As of approximately mid-2025, this functionality has stopped working entirely.
When attempting to connect a second set of credentials (same financial institution, different login), QuickBooks now forces disconnection or refuses to authorize.

This issue is not isolated to a specific bank.

It occurs with:

• Wells Fargo
• CitiBank
• Bank of America
• U.S. Bank
• Barclays
• American Express

Each institution’s technical team has confirmed no policy or API change was made on their end that would restrict customers from using two different credential sets concurrently. It is highly improbable that six or more unrelated financial institutions implemented identical new restrictions on the same date.

Therefore, the logical conclusion is that this change originates from Intuit’s own aggregation or connectivity layer, either within QuickBooks Online, Intuit’s OAuth token management system, or its third-party aggregator (e.g., Plaid/Yodlee).

This is a major regression from previous QuickBooks behavior and directly affects business workflows where owners manage multiple business accounts at the same bank.

KEY POINTS / TECHNICAL EVIDENCE

Previously Functional:

Multiple credentials per institution worked seamlessly prior to spring 2025.

Simultaneous Failure Across Institutions:

The restriction appeared across all major U.S. banks simultaneously — an impossible coincidence if banks were individually responsible.

Bank Confirmations:

Support teams at Wells Fargo, CitiBank, and Bank of America have all confirmed that:

“There is no restriction on our side preventing multiple credential authorizations for third-party applications.”

Impact Scope:

Prevents legitimate dual-account access.

Breaks existing reconciliations and automated feeds.

Causes unexpected disconnects even for long-standing connections.

Inference:

This appears to be an Intuit-side policy or code change treating “institution” rather than “credential” as the uniqueness key for active bank connections.

REQUESTED ACTION:

Please escalate this case to Tier 2 or Engineering for verification of the following:

Was there a policy or code change in the Intuit aggregator or bank-feed service that now enforces “one connection per financial institution per QuickBooks company”?

If so, what is the official reason (security, API consolidation, aggregator migration, etc.)?

Is there a workaround or exemption for legitimate use cases involving separate credentials?

Please provide an official statement or article link confirming whether this is an intentional limitation or a defect.

This is a legitimate and widespread functional regression, not a bank-side policy. It requires a clear and

documented engineering-level response.

IMPACT STATEMENT

Our business relies on maintaining accurate real-time feeds from both personal and business accounts for reconciliations and owner-draw tracking.

The current restriction forces manual imports and undermines a key feature of QuickBooks Online.

We need either:

Restoration of prior functionality, or A documented technical workaround endorsed by Intuit.