How do I keep my money records accurate when my bank merges?

Keep your money records accurate during a bank merger by saving the old records, confirming the migration instructions, and checking each replacement account against its predecessor. Count each real balance once, and verify transaction history separately from balances. Follow the bank's confirmed instructions and your budgeting app's documented process before changing connections. Do not delete an old listing merely because a replacement appears or the combined total looks too high.

A bank merger requires a record of what changed

A bank-driven migration can leave you comparing different names, account identifiers, and update dates. An unfamiliar listing is not necessarily new money, and a familiar listing is not necessarily current. Establish what each listing represents before deciding which balances belong in your total.

Keep three questions separate:

Two equal balances do not prove duplication. You could genuinely have the same amount in two separate accounts. Conversely, an old snapshot and its replacement's current balance can differ while still representing the same money at different times.

Use the bank's official website, secure messages, or a known telephone number to confirm instructions. A merger notice should not become a reason to enter banking credentials through an unverified message.

Build a bridge between old and replacement accounts

Create the transition record before changing connections. A short checklist gives you a way to distinguish a bank migration issue from an app display issue without experimenting with deletion.

1. Save statements and dated account records. Download available bank statements, transaction records, and merger notices before the transition. Record each account's identifier, balance, and effective date. Save final statements when available, and check how long older documents remain accessible rather than assuming continued access.
2. Confirm the bank's migration instructions. Establish the transition date, which login and institution name to use afterward, whether account identifiers change, and what the bank says about third-party account access. If instructions do not address your budgeting app, ask the app's support team how to proceed before disconnecting anything.
3. Match old accounts to replacements. Make a table with account type, owner, old masked identifier, new masked identifier, and the bank's explanation of the relationship. Mark each listing as continuing, replaced, or genuinely separate only after confirmation. Do not rely on the account nickname alone.
4. Record comparable balance snapshots. Note the effective date of each bank balance and the app's last update time. Compare the same balance basis, such as posted balances with posted balances, and identify pending items separately. A balance from before the migration cannot be compared directly with one after several purchases without accounting for that activity.
5. Change access only through the confirmed route. Follow the bank's sharing instructions and the app's documented connection process. Before any removal, check its effects on transactions, edits, and historical reports. Keep working connections intact while support resolves an unclear migration route.
6. Reconcile the replacement balance. Start with the documented old closing balance, add subsequent deposits, and subtract subsequent withdrawals and charges through the replacement balance's date. Investigate any unexplained difference instead of creating an adjustment just to force agreement.
7. Check transaction coverage across the boundary. Compare individual entries from before the transition through the first complete period afterward. Identify missing entries and overlapping imports by account, amount, merchant, and bank dates. An opening-balance entry representing existing money is not new earnings.

This is bank reconciliation across a migration, not just a check that syncing succeeds. Keep the mapping and supporting documents together until both the balances and the transaction history agree.

Duplicate listings can turn $11,600 into $21,600

Suppose the bank confirms that your old checking and savings accounts are replaced during a migration. At the close of June 14, checking holds $3,200 and savings holds $6,800, totaling $10,000. The replacement accounts begin with those same amounts; the bank confirms that the old listings do not represent additional deposits.

Between that cutoff and the close of June 16, checking receives $1,800 of pay and pays $120 for groceries and $80 for a utility bill. Savings has no activity. Assume there are no other transactions, interest, fees, or pending items in this example.

Your app temporarily displays both sets of listings:

The replacement checking balance reconciles as $3,200 + $1,800 − $120 − $80 = $4,800. Adding savings gives $4,800 + $6,800 = $11,600. The same result follows from the original combined balance: $10,000 plus $1,800 of income minus $200 of spending equals $11,600.

Counting every displayed listing produces $21,600, overstating your deposit balances by $10,000. The difference is the old checking and savings snapshots counted a second time, not money created by the merger. The zeroes in the final column mean those snapshots contribute nothing additional to the current total; they are not instructions to rewrite the historical bank balances.

The transaction check remains separate. If the app shows the $1,800 deposit and $80 utility payment but omits the $120 grocery purchase, its recorded spending for this interval is only $80 rather than $200—even if its current checking balance correctly shows $4,800. A correct balance does not establish complete transaction coverage.

Verify continuity before retiring an old listing

Resolve the balance problem without casually sacrificing the history. Before removing an old listing, determine whether it holds transactions that the replacement listing does not contain. Also identify any overlapping period so the same purchase does not enter spending totals twice.

Check whether your app has a documented way to retain useful history without counting a stale balance. If the documentation does not answer that question, ask support. Until the issue is resolved, use your separately reconciled total rather than treating an inflated app total as available money or an increase in net worth.

Keep a coverage note for each account: the last verified old-account date, the first verified replacement-account date, and any gaps or overlaps. Check the first statement covering the transition against both sets of records. For incomplete earlier periods, use the separate process for missing older transactions rather than assuming another connection will retrieve them.

Ordinary connection expiry and ordinary account closure are different problems. Use expired-connection troubleshooting when access has expired, and closed-account record checks when an account has actually closed. Neither replaces confirmation of how the bank mapped your accounts during its migration.

Common mistakes

• Adding every displayed balance together. Confirm which listings represent separate money and which represent old and replacement records of the same money.
• Changing connections before reading the migration instructions. Establish the bank's intended access route and the app's process before disconnecting a working feed.
• Deleting the old listing to fix the total. Check what history it contains and what removal does before taking an irreversible step.
• Comparing different dates without the intervening activity. Deposits and purchases can explain a balance difference that initially looks like a migration error.
• Treating a replacement opening balance as income. Existing money remains existing money when its account name or identifier changes.
• Checking only balances. Missing purchases and duplicate imports can distort spending even when the current account balance is right.

Common questions

Should I connect the new bank before disconnecting the old one? Do not assume a universal order. Confirm the bank's migration instructions and ask the budgeting app how its connection process handles the change. If both listings appear temporarily, use your account mapping and dated reconciliation to avoid counting the money twice.

Does the bank's new name mean I have a new account? Not necessarily. A name alone does not tell you whether an account continues unchanged, has been replaced, or is genuinely separate. Match identifiers and ownership details to the bank's migration records before changing how the account contributes to your totals.

Why are the old and replacement balances different? First compare their effective dates. The old listing may show a pre-migration snapshot while the replacement includes later deposits and payments. Reconcile that activity before treating the difference as an error; if it remains unexplained, ask the bank to confirm the transition balances.

Can I remove the old account once the new balance looks right? A matching balance is only one check. Confirm transaction coverage, overlapping imports, and the consequences of removal first. Keep the supporting statements and ask support about retaining useful history when the app's documentation does not explain the options.

What should I send support if the records still disagree? Provide the institution names, masked account identifiers, transition date, balance effective dates, last successful updates, and specific missing or repeated transactions. Explain the relationship the bank confirmed between the accounts. Do not send passwords, sign-in codes, or full account numbers in an ordinary support message.

How Zypper handles this

In Zypper, open Settings › Connections to check each institution's status, accounts, and last update time; connected accounts sync automatically every day, and you can refresh one connection or all connections, as described in Checking connection status and refreshing. The Include in the budget setting controls budget participation, but an excluded account still counts toward net worth, so it does not remove a duplicate balance from that total. Removing a single account deletes that account and its data, while removing a connection stops syncing for every account it provides; review Editing and removing accounts before either action. You can get started with Zypper to connect accounts and review their connection status.