QuickBooks Online Deposit Recorded to the Wrong Bank Account? Here's the Fix

Published September 28, 2026 · LedgerMedic

When you build a deposit from Undeposited Funds in QuickBooks Online, there's a dropdown at the top of the Bank Deposit screen that picks which bank account the money lands in. If that dropdown was left on the wrong account, whether by habit, by a saved default, or by simply clicking too fast, the deposit is now sitting in the wrong ledger. Both bank accounts will fail to reconcile, and because the payment has already been "used" by that deposit, it won't show back up in Undeposited Funds the way an unmatched payment normally would, which is what makes this one more confusing to untangle than most.

Why this is a different problem from a duplicate deposit

A duplicate deposit records the same money twice in the same account. This is the opposite kind of mistake: the money is recorded once, correctly in amount and date, just in the wrong account's register. The correct bank account is missing a deposit it actually received, and the wrong account shows a deposit it never received. Reconciling either account in isolation will fail, and it's easy to mistake this for a reconciliation problem rather than a routing problem, since nothing looks "duplicated" anywhere.

The fix: move the deposit, don't rebuild it

The instinct is to delete the wrong deposit and re-enter it from scratch in the correct account. Don't. Deleting it sends every itemized payment inside it back into Undeposited Funds, which then has to be regrouped into a brand-new deposit by hand, itemized payment by itemized payment, in exactly the combination it was in before. There's a much shorter path.

1. Find the deposit in the wrong account's register. Since it's not in Undeposited Funds anymore, look in the bank register of whichever account it mistakenly posted to, it'll be the deposit that has no matching line on that account's actual bank statement.
2. If a bank feed already matched or accepted a transaction against it, open the Banking tab for the wrong account and undo that match first. Editing the deposit underneath an already-matched feed transaction leaves a feed entry pointing at nothing.
3. Open the deposit and change the "Deposit to" account at the top of the screen from the wrong account to the correct one. Every itemized payment inside the deposit moves with it, you don't need to touch the line items at all.
4. Save the deposit. It disappears from the wrong account's register and appears in the correct one, still built from the same original Undeposited Funds payments, in the same grouping.
5. If either account had already been reconciled for the period covering this deposit, you'll need to undo that reconciliation before the edit, then redo it afterward. Skipping this step is the most common reason this fix gets re-broken a month later.
6. Re-run reconciliation on both accounts for the affected period. The wrong account should now tie out without the deposit; the correct one should tie out with it included.
7. Check whether a bank rule caused it. If a saved bank rule auto-selects a default deposit account for a certain payment type or customer, and that default is wrong for this transaction, fix the rule so the same misroute doesn't happen again next month.

A note if the accounts share a bank or use similar names

This mistake happens disproportionately often when two accounts look alike in the dropdown, an operating account and a trust or escrow account at the same bank, or two accounts named almost identically for different locations. If that's the setup causing the error, renaming the accounts in QuickBooks to be visually distinct (adding the last four digits of the account number, for instance) prevents the same misclick from repeating.

This is closely related to, but distinct from, a duplicate deposit, and from Undeposited Funds not matching the bank deposit. All three break reconciliation the same way, a QuickBooks number that won't tie to a bank statement, so it's worth ruling out each one specifically rather than assuming which you're looking at.