Clearing a Stuck Undeposited Funds Balance in QuickBooks Desktop

An old balance stuck in QuickBooks Desktop Undeposited Funds throws off the books; this guide shows the safe way to find and clear it.

Undeposited Funds is a holding account, not a bank. Every payment recorded on an invoice or sales receipt lands there first and waits to be grouped into a deposit. An old, stubborn balance means payments never became deposits on the books, and our engineers clear them with proper deposits rather than a journal entry.

The account is a queue, not a balance

The balance is not forgotten cash. It is a list of finished payments waiting for one last step, each one already applied to a customer invoice. That is why a journal entry cannot truly fix it: the entry changes the number, but the payments stay in the queue.

QuickBooks will not empty the account by itself. The Make Deposits workflow is the only path that moves a payment out cleanly, because it links the payment, the invoice, and the bank line.

Prepare the file before you touch the queue

Back up first. Open the File menu, choose Back Up Company, and create a backup you could restore tonight. Then switch to single-user mode so nobody records a payment mid-cleanup. Set a cutoff date and work one bank statement period at a time, oldest first, with those statements beside you.

If you want a routine that stops the pile rebuilding, our write-up on the month-end close and reconciliation cycle shows where this check belongs.

Find the payments still waiting in the queue

1. Open the Banking menu and choose Make Deposits, called Bank Deposit in newer releases. Anything listed in the Payments to Deposit window is money the books received but never banked.
2. For a dated view, right-click Undeposited Funds in the Chart of Accounts and choose QuickReport. Set the range to your cutoff period. Each payment shows with its date, customer, amount, and method.
3. Note the method. Card payments batched through a processor often reach the bank as one lump with fees netted, which matters next.
4. Sort by date, then by customer, so natural batches stand out.

Match each batch to a line on the statement

Pull the bank statement for the same period and find the line where that money arrived. Group the payments that traveled together into one deposit, dated the arrival day. Where a processor netted its fees, add a second line on the deposit form: the fee as a negative amount, coded to your bank charges account. The deposit then equals the bank line exactly.

A payment with no matching bank line is a different problem. Deposit nothing in that case. Void or delete the payment instead, so the invoice reflects what actually happened.

Record the deposit so it clears at reconciliation

1. In the Payments to Deposit window, tick every payment that formed that bank batch.
2. Set the deposit date to the day the money hit the bank, not the day of the cleanup.
3. Check the Deposit To account at the top of the form; old cleanups often land in the wrong bank.
4. Save the deposit. If the next statement line holds another batch, tick that group and repeat.
5. Run the Undeposited Funds QuickReport again at the end of the period.

The signs of success are concrete. The deposit appears in the bank register for the exact statement amount and date. The account balance drops by the same total, and the queue in Payments to Deposit visibly shortens after each save. At reconciliation, the line matches with nothing left over.

What about payments recorded twice?

One pattern is the same payment entered twice, with both copies waiting in the queue. Keep the copy that belongs to a bank batch and delete the stray. Deleting an undeposited payment is low risk, because no bank line depends on it. The invoice reopens, which is correct if the customer paid once.

The other pattern is a deposit typed straight into the checking register while the payment still waits in the queue. The bank has one line; the books have two. Remove whichever side has not been reconciled. If the raw register entry is unreconciled, delete it and build the deposit from the queued payment. If it already cleared a statement, deleting it breaks that reconciliation, so remove the queued payment and decide how the reopened invoice should settle.

One caution covers both. Deleting or voiding a payment in a period already filed on changes that year's reported income, while recording its deposit does not. Be generous with old deposits and deliberate about old deletions.

A journal entry zeroes the number, not the problem

The temptation is to debit the bank and credit Undeposited Funds until the balance reads zero. It changes the number and nothing else. The payments stay in the queue, which is driven by payment links rather than by the balance. The customer ledger still shows unbanked money, cash-basis reports drift, and the next reconciliation meets a line matching nothing on the statement. You would simply be scheduling a second cleanup.

When does the problem run deeper than the queue?

Sometimes the residue is not payments at all. Opening balances, old adjustments, and journal entries parked in the account never appear in Payments to Deposit, so no deposit can clear them. That leftover must be identified line by line and moved to where it belongs, which is analysis work rather than batching work.

Years of loose use across closed periods add an accounting side no software step resolves. And if deposits post but the balance refuses to move, or the register misbehaves afterward, run Verify from the File, Utilities menu. A file that fails Verify needs repair before its books can be trusted; our QuickBooks Verify and Rebuild repair service covers exactly that. Fix the file, then finish the queue.