Undeposited Funds in QuickBooks: what it's for, and how it gets stuck
The account everyone has a growing balance in and nobody set up on purpose. What Undeposited Funds is actually solving, why it fills up, and how to clear it safely.
Open your balance sheet. There is an account called Undeposited Funds with a balance in it. Nobody remembers creating it, nobody is quite sure what is in it, and the number has been going up for two years.
This is one of the most common conditions in small-business bookkeeping, and it is entirely fixable once you know what the account is actually for.
What it solves
Undeposited Funds exists to handle one specific mismatch: you receive payments individually, and you bank them together.
Three customers pay you £400, £750 and £1,100. You take all three cheques to the bank on Friday. Your bank statement shows one deposit of £2,250. Your books show three payments.
Nothing matches. There is no £2,250 receipt in your records and no £400 line on the bank statement.
Undeposited Funds is the holding area that closes the gap. Each payment is received into it, then the bank deposit is recorded as a single entry grouping all three. Your books now show one £2,250 deposit — matching the bank exactly — while each invoice remains correctly marked as paid.
It is not an error account. It is a batching mechanism, and for a business handling cheques or cash it is genuinely the right tool.
Why it fills up
The balance grows because payments go in and nothing comes out. Money is received into Undeposited Funds and the corresponding bank deposit is never recorded, so entries accumulate indefinitely.
The dominant modern cause is the collision between this workflow and bank feeds.
Here is the pattern, and almost every stuck balance is a version of it:
- A customer pays by card or transfer. The money lands in the bank.
- The bank feed imports the deposit. Someone categorises it — often straight to income.
- Separately, someone marks the invoice as paid in QuickBooks. The default payment account is Undeposited Funds.
You now have two records of one payment. The bank-feed copy is reconciled and accounted for. The Undeposited Funds copy is stranded, with nothing to clear it against, forever.
Repeat weekly for two years and the balance is enormous. It also means your income is likely overstated, because the same money has been recognised twice — once through the feed categorisation and once through the invoice payment. This is the same underlying failure as ordinary duplicate transactions, with an extra account involved to disguise it.
Other causes, less common:
- Deposits recorded directly to the bank account, bypassing the grouping step, while receipts still route through Undeposited Funds.
- A deposit recorded for a different amount than the sum of the receipts it was meant to clear, leaving a remainder.
- Processor settlements where the deposit is net of fees while the receipts are gross — the difference sticks.
How to clear it, safely
Do not journal the balance away. Every entry in Undeposited Funds corresponds to an invoice you have already marked as paid. Wiping the balance leaves those invoices settled with no money behind them, which either understates revenue or invents an expense depending on how you post the adjustment. You will have replaced a visible problem with an invisible one.
Work it properly:
1 · List what’s in there. Run a report on the account showing individual transactions, not just the balance. Each line is a payment received but never deposited. Note the dates — they tell you when the pattern started, which usually identifies what changed.
2 · Sort the entries into two groups.
- Genuinely undeposited — real money that was received and banked, where the deposit step was simply never recorded. Rare in an electronic business, common where cheques are involved.
- Duplicates — payments already accounted for through the bank feed. This is almost always the large majority.
The test: find the payment on the bank statement. Has it been categorised from the feed already? If yes, the Undeposited Funds entry is the duplicate.
3 · For genuine ones, record the deposit. Use the bank deposit function, select the receipts that made up that deposit, and match the total to the bank statement line. The entries clear.
4 · For duplicates, fix the source. Remove the incorrect record — usually the bank-feed line if it was categorised straight to income, since the invoice payment carries the customer link and settles the invoice properly. Then reconcile that period again.
5 · Do this in date order, oldest first. Later entries often depend on earlier corrections, and working backwards means redoing work.
If the balance covers several years and hundreds of entries, this is a bookkeeper’s job, not an evening’s job. Do it anyway — the alternative is that every reconciliation and every set of accounts from here on rests on a number nobody can explain.
Should you use it at all?
If you receive cheques or cash: yes. This is exactly the problem it was designed for.
If you receive only electronic payments, individually: probably not. Each payment arrives separately and appears separately in the feed. Routing it through a holding account adds a step with nothing to reconcile against, and creates the duplicate risk above for no benefit. Change the default deposit account on your payment methods so receipts go straight to the bank account.
If you receive processor settlements: yes, but not necessarily this account. When one deposit covers forty sales net of fees, you genuinely need a holding mechanism — but a dedicated clearing account per processor is usually cleaner, because it lets you see each processor’s undeposited position separately and makes the fee difference explicit rather than mixed in with everything else. That structure is worth setting up early: see setting up QuickBooks for a service business.
What the growing balance is actually telling you
A rising Undeposited Funds balance is a symptom, and the disease is worth naming.
It means two systems are independently recording the same money and nobody is reconciling them against each other. The bank feed says money arrived. The invoicing side says a customer paid. Both are true, both are recorded, and nothing connects them — so one of the two records goes nowhere and quietly accumulates.
That is the same failure that produces reconciliation discrepancies, duplicate expenses and unallocated supplier payments. Undeposited Funds is simply the version where the orphaned record has a dedicated account to pile up in, which at least makes it visible. Most orphaned records do not get that courtesy.
The link between a payment and the invoice it settles is not something the accounting system can reliably infer afterwards from an amount, a date and a bank description string. It is information that exists at the moment the payment is made and is thrown away before it reaches the ledger. Every reconciliation problem downstream is an attempt to reconstruct it.
Where Fynex fits
Fynex keeps the link. A payment carries the invoice it settles, the fee deducted from it, and the settlement it arrived in — created when the money moves, not inferred a month later from a bank feed.
That removes the condition that fills Undeposited Funds in the first place: there is one record of the payment rather than two, so nothing is orphaned and nothing accumulates. Processor settlements break down into the individual sales they contain, with fees booked as fees, so the gross-versus-net difference never becomes a residue in a holding account.
The account can stay in your chart of accounts doing the job it was designed for — batching cheques. It just stops being the place where two years of unexplained money goes to sit.