Bank Feed Broken After a Bank Merger: Fix It in QuickBooks

When your bank or credit union merges, it converts to the acquiring institution's core system, and the listing QuickBooks connected to stops existing. The feed throws an error (162 and 525 are the classic merger codes) or the institution vanishes from the search list. The fix: disconnect the dead connection, search for the new institution name, and link it to the same existing account in your chart of accounts rather than letting QuickBooks create a new one. Whatever months the new feed won't backfill, you fill by converting statement PDFs to .qbo files.

Last updated July 2026.

Why a merger breaks the feed in the first place

QuickBooks doesn't connect to "your bank" in the abstract. It maintains a connection to a specific institution listing, tied to a specific online banking platform and login endpoint. A merger is a core-system conversion: new URL, new credentials, often new account numbers, and a new (or absent) entry in Intuit's list of connectable institutions. From QuickBooks' point of view, the bank you were connected to no longer exists.

Sometimes the acquiring bank's listing works on day one. Sometimes it sits in limbo for weeks while Intuit and the aggregator rebuild the connection. Small banks and credit unions on niche cores get the worst of it. Our breakdown of what each QuickBooks bank feed error code means will tell you whether this is a merger problem or something else.

Mergers are not rare, and each one is a conversion

This is not a once-in-a-career edge case. Credit unions are consolidating fast, and every deal means a core conversion for the surviving members.

Source: NCUA, Q1 2026 credit union system performance data.

Roughly 160 federally insured credit unions disappeared in twelve months, and they didn't evaporate. Their members woke up on a new core with a new banking portal. Banks consolidate on the same curve. CU feeds are the ones most likely to stay broken, so members should start with our guide to getting a credit union statement into QuickBooks.

What breaks versus what to do

"Reconnecting Bank Feed to already established accounts"

Disconnect first, then reconnect. In QuickBooks Online, open Bank transactions, find the dead account tile, choose Edit account info, and check Disconnect this account on save. Then add the new institution and, at the account-matching step, pick your existing register from the dropdown. Skip the disconnect and QuickBooks will happily build you a second account.

The disconnect deletes nothing. Your register, reconciliations, and matched transactions stay put. It only severs the link to a bank endpoint that stopped answering. In QuickBooks Desktop the equivalent is deactivating bank feeds on the account (Lists, Chart of Accounts, right-click, Edit Account, Bank Settings, deactivate all online services). Clear For Review first, because Desktop won't deactivate an account with downloaded transactions still waiting.

"Bank Changed URL, I updated but now have two accounts for each account"

The classic failure. You reconnected without disconnecting, or clicked through the account-matching screen too fast, and now there's a Checking and a Checking (1). The transactions are real, but they're in the wrong register, and your reconciled history lives in the old one.

You want the history in the original account. Undo anything you accepted into the duplicate, exclude the rest, disconnect the duplicate from the feed, then connect the feed to the original register. Merging is the other route, but QuickBooks blocks merges on accounts actively connected to online banking, so the connection comes off first either way. Work through how to clean up duplicate bank transactions in QuickBooks before you categorize anything new.

"QB is only downloading my transactions for the past 3 months. How do I import my transactions for the past year?"

Feeds keep you current, they don't backfill. On connect, QuickBooks pulls whatever history the bank hands over, commonly about 90 days. Some institutions offer more, plenty offer less, and after that initial pull the feed only brings in new activity. Older transactions have to arrive another way.

After a merger this bites twice as hard, because the new institution's feed tends to start from the conversion date. Whatever happened at the old bank isn't coming down the pipe, no matter how often you hit Update. Details in how far back QuickBooks can import bank transactions.

So the gap months become a manual import job. Both editions accept a Web Connect file. QuickBooks Desktop's Web Connect import reads only .qbo, and it's the cleanest path there. QuickBooks Online will also take a .qbo upload, and its file-upload path caps out at 350KB and 1,000 lines per file, which is fine if you split a long catch-up by month or by quarter.

"I cant get more than 90 days of transactions to load from my bank account"

You can't, and that's by design. The way through is the statement itself. Download the PDF statements for every gap month from the old portal (and the new one, for the conversion period), then convert each PDF statement to a .qbo file and import it into the account the feed is now attached to. Those transactions land in For Review exactly like feed data.

This works where a feed can't because the statement is the bank's own record, complete and final, going back as far as your archive does. A QBO converter reads the PDF (or a scan of it) and writes the Web Connect file QuickBooks expects. For a year or more of history, see converting a year of statements for catch-up bookkeeping.

The order of operations that avoids duplicates

Duplicates come from two places: reconnecting into a new account instead of the existing one, and importing a period the feed already covered. Both are avoidable.

1. Log in to the new portal in a browser. Confirm the credentials work and note any new account numbers.
2. Download every statement PDF you still need, from the old portal and the new one. Old portals get shut off with short notice.
3. Clear For Review on the affected account so nothing is half-processed.
4. Disconnect the old feed (QBO) or deactivate bank feeds on the account (Desktop).
5. Connect the new institution by its new name and link it to the existing account in your chart of accounts.
6. Note the earliest date the new feed pulled. That is your gap boundary.
7. Convert and import the gap months as .qbo files, stopping the day before that boundary date. No overlap, no duplicates.
8. Reconcile month by month against the statements you downloaded.

Step 6 is the one bookkeepers skip. Check the oldest transaction the feed actually brought in, not the date you assume. If the feed reached back to April 12 and your import file runs through April 30, you just made eighteen days of doubles.

"Linked an account in error - how do I remove duplicate transactions?"

If the duplicates sit in For Review, select them and choose Exclude. They move to the Excluded tab, where you can delete them permanently. If you already added or matched them, go to the Categorized tab, select them, and Undo. That returns them to For Review, where you exclude them like the rest. Do this before you reconcile, not after.

Keep a copy of the old bank's history before the portal goes dark

The part nobody warns you about: after conversion, the acquirer eventually kills the legacy portal, and years of statement history go with it. Once it's gone, you're filing a records request.

Pull every statement PDF you can while you still have a login. Beyond the .qbo files you'll import, keep a spreadsheet copy of the old account's history for reconciliation workpapers, since a flat file is easier to pivot and tie out than a stack of PDFs. Archive the raw statements too. An auditor wants the original document, not your export of it.

When the new institution isn't connectable at all

Sometimes the acquirer isn't in QuickBooks' list at all, or its listing stays broken for months. Two honest choices: wait, or work from statements.

Working from statements is not a downgrade. You import bank statements into QuickBooks as .qbo files once a month, right after the statement drops. The data is cleaner than feed data (statements are final, feeds show pending items that later change) and it reconciles to the penny. If you're still hoping the feed returns, our guide to QuickBooks not connecting to your bank covers what to try first.

Frequently asked questions

Will I lose my reconciliation history if I disconnect the bank feed?

No. Disconnecting only removes the link between QuickBooks and the bank's servers. Your register, your categorized transactions, and your completed reconciliations stay exactly as they are. What you lose is the automatic download, which was already broken. Disconnecting is a prerequisite for a clean reconnect, not a destructive act.

Should I create a new QuickBooks account for the merged bank?

Almost never. The bank changed, but it's the same money in the same account with the same reconciled history. Link the new connection to your existing register at the account-matching step. Creating a new account splits your history across two registers and forces a merge later, which QuickBooks blocks while either account is connected to online banking.

Why doesn't the new feed bring in transactions from before the merger?

Because the feed only pulls what the new institution's platform makes available, and that window is typically short (commonly around 90 days, sometimes less). Pre-conversion activity often lives only in the legacy system. Those months have to come from statements, converted to .qbo and imported into the same account.

How do I import the gap months without creating duplicates?

Find the oldest transaction the new feed actually downloaded and treat that date as your boundary. Build your .qbo files to end the day before it. If you do overlap, catch the doubles in For Review and exclude them, or undo them from Categorized first if you already accepted them.

Does QuickBooks Desktop still accept .qbo files after a merger?

Yes. Web Connect import is independent of whether the institution's live feed works, and it reads only .qbo files. You may need to deactivate bank feeds on the account first if the old connection is still attached. Once the file imports, transactions flow into the same account and match against what's already there.