n-What Is Payments to Deposit in QuickBooks?
Payments to Deposit is the list QuickBooks shows you of customer payments it's already received but hasn't yet grouped into an actual bank deposit, the same payments sitting in the Undeposited Funds account under a different name. QuickBooks Desktop pops it up as its own window the moment you choose Make Deposits; QuickBooks Online builds the identical list right into the Bank Deposit screen.
How the list actually works
1. Where it shows up. In Desktop, going to Banking > Make Deposits opens a Payments to Deposit window automatically if anything's waiting to be grouped. In QBO, + New > Bank Deposit shows the same list under the heading Select the payments included in this deposit, same information, no separate pop-up.
2. What lands on it. Any payment recorded through Receive Payment or a Sales Receipt without picking a specific bank account directly goes here first, instead of posting straight to a bank account.
3. What doesn't show up. A payment entered with a bank account chosen directly on the Receive Payment screen skips this list entirely, because QuickBooks already knows exactly which bank line it belongs to and has nothing left to group.
4. Selecting what belongs together. Check off the payments that physically arrived together as one real bank deposit, confirm the running total matches your actual deposit slip or bank statement line, and save.
5. Why it sometimes looks empty. If everything so far was entered with a bank account chosen directly, or everything's already been grouped into a saved deposit, there's nothing left waiting, and Desktop skips straight to the Make Deposits screen with nothing to check off.
Where the list stops matching what actually happened
The list itself is simple. The hard part is knowing which lines on it belong together as one real-world deposit, and that information doesn't live in QuickBooks at all, it lives in whatever actually happened at the bank or the register that day. A processor payout that bundles several days of card payments into one lump sum is the clearest case: nothing on the list maps one-to-one to what shows up on the bank statement.
The other common failure is at the point of entry, not the deposit screen. Someone receiving a payment picks a bank account directly instead of letting it land on this list, usually by habit or because the screen defaults differently than they expect, and the payment ends up posted twice or missing from a deposit where it should've been grouped with others.
What we've built on top of QuickBooks deposits
Payments batched to match the real deposit automatically
Processor payout data gets pulled in directly, so the right subset of the Payments to Deposit list gets selected and saved on its own, instead of someone reverse-engineering which lines add up to the bank total.
A payment routed correctly the moment it comes in
Rules decide whether a payment should land on this list or post straight to a bank account, based on how it was actually collected, so the list doesn't fill up with things that never belonged there.
How much guesswork goes into grouping your deposits right now?
Tell us where the mismatch usually comes from, a processor payout, a cash batch, something else, and we'll tell you if the matching can run on its own.
Still eyeballing which payments belong in which deposit?
Tell us what actually lands on your Payments to Deposit list week to week, and we'll tell you honestly whether grouping it can happen automatically. And if deposits aren't the real bottleneck, that's fine too, n-frames automates whatever's manual in a business, any tool, not just this one screen.
Let's talk