Undeposited Funds is a QuickBooks Online holding account where customer payments sit between the moment you receive them and the moment they hit the bank. It's not a bug, not a workaround, not a balance to be afraid of. As covered across the accounting glossary, it's a deliberate design feature that lets a single bank-statement deposit match multiple customer payments. The trouble is that when the workflow is broken, payments get stuck in Undeposited Funds and the books drift out of reality.
Every QBO file has an Undeposited Funds account. By default, when you "Receive Payment" against a customer invoice, QBO posts the payment to Undeposited Funds rather than directly to the bank. The cash sits there until you go to "+ New → Bank Deposit" and group payments into a single bank-deposit transaction.
It's the same workflow a paper-era bookkeeper used: receive checks throughout the day, hold them in a desk drawer (the "deposit box"), then take them all to the bank as a single deposit at end of day. Undeposited Funds is the digital deposit box.
The reason for the holding account: bank statements show a single deposit when you take three customer checks to the bank, but the books need to record three customer payments individually. Without Undeposited Funds, the bank statement deposit ($5,000) wouldn't match anything in QBO. The books would have three separate $1,000-$2,000-$2,000 entries that the bank reconciliation can't tie back.
Undeposited Funds collapses the three payments into one Bank Deposit entry that matches the $5,000 line on the bank statement. AR is reduced correctly per customer; reconciliation works cleanly.
In a clean book, Undeposited Funds is near $0 at month-end. Anything sitting there means a payment was received but the corresponding bank deposit was never recorded. The balance is real cash that the books think is uncategorized, and at month-end, that cash should have been deposited and recorded.
A balance of $200-$1,000 transient mid-month is normal. A balance of $5,000+ at month-end means the deposit step was skipped on multiple payments and needs cleanup. Material persistent UF balances are a sign of broken workflow that compounds over time.
Undeposited Funds is a QuickBooks Online holding account for customer payments received but not yet deposited as a batch to the bank. It's a deliberate design feature that lets multiple customer payments match a single bank statement deposit. Clean books have near-$0 in this account at month-end.
Three customer payments arrive on March 15: $1,500, $2,000, $1,500. You take all three checks to the bank that afternoon and deposit them as a $5,000 batch.
In QBO:
Bank statement shows: $5,000 deposit on March 15. QBO bank account shows: $5,000 deposit on March 15. Reconciliation matches one-to-one. Customer AR reduces by $1,500/$2,000/$1,500 individually. Undeposited Funds returns to $0.
Three steps make the workflow work.
When a customer pays an open invoice, the path is "+ New → Receive Payment." Pick the customer, select the invoices being paid, enter the payment amount and method (check, ACH, credit card). For the deposit-to account, select Undeposited Funds.
QBO debits Undeposited Funds and credits Accounts Receivable for the customer. The invoice is marked paid. The payment now sits in Undeposited Funds waiting for the deposit step.
When you actually take the payments to the bank (or the e-check batch hits), the path is "+ New → Bank Deposit." Pick the bank account being deposited to. The system shows every payment currently in Undeposited Funds. Select the payments included in this deposit.
The total at the bottom of the form should match the actual deposit amount on the bank statement. Save. QBO debits the bank account and credits Undeposited Funds for the deposit total. UF is back to whatever balance was there before this deposit.
When the bank reconciliation runs, the bank statement shows one $5,000 deposit. QBO shows one Bank Deposit transaction for $5,000. Match. Behind that single Bank Deposit are three customer payments, but those don't appear on the bank statement and don't need to. The monthly reconciliation just sees the deposit total.
This is the entire reason Undeposited Funds exists. Without the holding account, three customer payments would each appear as separate bank transactions and never match the single bank-statement deposit. Reconciliation would be a mess.
Day-of workflow:
Bank statement (next day): $5,000 deposit on March 15. Books match.
Three workflow errors produce most stuck UF balances.
The most common error. The bookkeeper records a Receive Payment (correctly to Undeposited Funds) but never does the corresponding Bank Deposit. The payment sits in UF forever. The bank account is short by the payment amount because the deposit was never recorded, except the bank statement shows the deposit happened.
Reconciliation reveals it: the bank statement has a $1,500 deposit that doesn't match anything in QBO, and Undeposited Funds carries a $1,500 balance that shouldn't exist.
The opposite error. Some bookkeepers, frustrated with the two-step UF workflow, configure Receive Payment to post directly to the bank account rather than to Undeposited Funds. That works fine when each customer payment maps one-to-one to a bank deposit (no batching).
It breaks when the bank statement shows a batch deposit. Now QBO has three individual customer payment entries and the bank statement has one $5,000 deposit. The reconciliation can't match them. Two errors compound: payments correctly recorded but bank statement won't match.
When QBO bank feed pulls in transactions, it sometimes posts customer payments to Undeposited Funds without prompting for batching. This creates orphan UF entries that have to be matched to subsequent Bank Deposit entries manually.
Cleanup is to identify the orphaned UF entries and either match them to existing deposits or post correcting Bank Deposits.
A few specific patterns:
Each is fixable but requires identifying the workflow gap and closing it.
When UF has a real balance at month-end, the cleanup process.
The path is "Reports → Custom Report → Transaction Detail by Account → Undeposited Funds." This shows every entry in UF, with date, customer, and amount.
For each entry, the question is: was this payment actually deposited at the bank? If yes, the cleanup is to create a matching Bank Deposit. If no, the customer paid but the cash never made it to the bank. That's a different problem (lost check, bounced payment, accounting fiction).
For payments that actually deposited, create the matching Bank Deposit. "+ New → Bank Deposit." Select the stuck UF entries that match a real bank-statement deposit. Save. UF clears, bank account gets the deposit, and the books match the bank statement.
If the stuck payments are scattered across multiple actual deposits, you'll need to do this multiple times: one Bank Deposit per actual bank-statement deposit, with the right UF entries selected each time.
If a Receive Payment was created for a customer who didn't actually pay (clerical error, duplicate entry), the right fix is to delete the Receive Payment. That reverses the AR-to-UF posting and returns the customer's invoice to open status.
Be careful here: deleting a Receive Payment in a closed period requires reopening the period, which can cascade to other reports. Most bookkeepers prefer a correcting journal entry (debit Undeposited Funds, credit AR for the customer) when the original entry is in a closed period.
The decision rule:
For systemic UF issues, fix the workflow before cleaning up balances. Otherwise you spend hours cleaning UF only to have new stuck entries appear next month.
Most UF problems surface during bank reconciliation.
The classic symptom. The bank statement shows a $5,000 deposit. QBO shows three Receive Payment entries of $1,500/$2,000/$1,500, but no Bank Deposit. The reconciliation can't match.
The fix is to create the Bank Deposit retroactively, dated to match the bank-statement deposit, with the three Receive Payments selected. After save, the reconciliation matches the single $5,000 line.
Bank reconciliation is the first place UF problems become visible because bank rec compares the bank statement to QBO transactions. Stuck UF balances mean QBO is missing the deposit transaction. The reconciliation has unmatched lines on the bank-statement side.
A bookkeeper who skips reconciliation can carry UF problems for months without anyone noticing. A bookkeeper who reconciles monthly catches them in the first month they appear.
Two approaches:
Most experienced bookkeepers fix in-rec for small numbers of UF issues and batch-fix when there's significant cleanup needed.
If you start a reconciliation and find UF-related mismatches, the workflow is:
QBO's bank rec feature handles this gracefully. Adding new transactions while a rec is in progress is supported.
Three patterns produce most UF cleanup work.
The single most common error. Receive Payment is recorded; Bank Deposit is forgotten. UF balance grows; bank account is understated. Eventually the bookkeeper notices during reconciliation, creates a catch-up Bank Deposit, and books are corrected.
Prevention: build "Bank Deposit" into the regular workflow as a same-day or next-day task after any Receive Payment. The discipline cost is small; the cleanup cost compounds.
Some QBO files have UF set up as if it's a sub-account of the operating cash bank account. That's wrong. UF should be a separate "Other Current Assets" account, distinct from any actual bank account. Mixing them obscures the workflow and breaks reconciliation.
If you inherit a file with this configuration, the cleanup is to recategorize UF as a separate account, then fix the historical postings. This is a non-trivial cleanup but pays back at every subsequent monthly close.
When a UF entry is wrong, the temptation is to edit it directly: change the amount, change the customer, change the date. This works if no downstream Bank Deposit has been created. If a Bank Deposit has been created against the original entry, editing breaks the deposit linkage and creates new mismatches.
The safer pattern: don't edit; reverse and re-post. Delete the original Receive Payment (or post a correcting JE), then create a new correct entry. The audit trail is cleaner and the deposit linkage stays intact for unaffected entries.
Deleting any transaction that's been included in a reconciled deposit will throw off the reconciliation. If you delete a $1,500 Receive Payment that was part of a $5,000 reconciled deposit, the deposit is now $1,500 short, but the bank statement still shows $5,000. The next reconciliation flags the discrepancy.
The fix is to reverse-and-recreate within an open period, or to post correcting journal entries that hit the same accounts without disturbing the deposit history. See the default expense bucket for the parallel cleanup pattern on the expense side. Don't bulldoze through with deletes. Work around them.
Growthy is bookkeeping software, not a CPA firm. This content is educational, not professional advice. Full disclaimer.
Related: Accounting & Bookkeeping Glossary, Uncategorized Expense: What It Means & How to Fix It, Bank Reconciliation: What It Is, Why It Matters, How to Do It
Free during alpha. Read-only access. You review every sync.
CPA firm partner who got tired of watching bookkeepers click categorize 500 times a day. Built Growthy to fix it.
View all articles →Growthy is dedicated to helping businesses of all sizes make informed decisions. We adhere to strict editorial guidelines to ensure that our content meets and maintains our high standards.
Uncategorized Expense is QuickBooks Online's catchall for transactions imported but never assigned to a real category. A clean book has $0 in this account. Here's how to recategorize what's there and prevent new ones from landing.
The trial balance lists every GL account with its debit or credit balance, proving total debits equal total credits. Here's how to read it, and the troubleshooting framework for when it doesn't balance.
The income statement (P&L) reports revenue, expenses, and net income for a period. Here's how to read each section, what it reveals about the business, and how to set up class- and location-based custom P&L views in QBO.