Glossary

QuickBooks Bank Deposit

A QuickBooks bank deposit is the transaction that combines payments waiting in Undeposited Funds into a single record matching the one lump sum your bank actually received.

Also called: bank deposit form, recording a deposit, deposit transaction, make deposits

Start a free trial View Pricing

Definition

Almost every form in QuickBooks records something happening with a customer. The Bank Deposit form does not. It records an act of combining: taking payments you have already recorded and grouping them into the one transaction your bank statement will show.

Intuit puts the reason plainly. When you deposit multiple customer payments at the bank, they are combined into one total, and without the deposit feature "your records won't match the bank" because each payment would sit in QuickBooks separately. The deposit is the transaction that closes that gap.

So a bank deposit moves nothing into your books that was not already there. Both sides of it are accounts you already hold: money leaves the holding account where the payments were waiting, and arrives in the bank account. Revenue was recognized earlier, when the sale was recorded. The deposit is a transfer with a grouping function attached, which is exactly why it is the form that a payment processor workflow leans on hardest.

Key points

+Combines several already-recorded payments into one transaction that matches one bank line.
+Payments must be sitting in Undeposited Funds to appear in the deposit picker.
+Recognizes no revenue: the income was booked when the sale was recorded.
+Each deposit is its own record, one per real-world deposit, not one per day or per month.
+The form accepts extra lines that were never payments, including negative ones for fees.
+Unchecking a payment on a saved deposit returns it to Undeposited Funds rather than deleting it.

What the form is actually doing

Two things, and only the second one is unique to this form.

The first is a transfer. The deposit total leaves whichever account the payments were parked in and lands in the bank account you selected. No income account is touched, because the revenue was already recognized on the sales receipt or the invoice that created each payment. A deposit that appears to create income is a sign that payments were not selected from the holding account, and that the revenue is now on the books twice.

The second is the grouping, and it is the whole point. Intuit's own instruction is that "each bank deposit creates a separate record in QuickBooks" and to "make deposits one at a time for each of your deposit slips." The deposit is meant to correspond to a real event at the bank. One record per real deposit, matched one to one against a bank line, is what makes reconciliation mechanical instead of investigative.

The most common way this goes wrong is not an error at all. It is omission. Payments get recorded and deposits never do, so the holding account grows, and the bank feed shows lump sums with nothing in QuickBooks to match them against. The fix is always to record the deposits that actually happened and tick the payments each one contained.

The extra lines are the feature that makes it work

Underneath the list of waiting payments, the deposit form has a second section for lines that were never payments at all. This is the part most guides skip, and it is what lets a deposit represent something more complicated than a stack of checks.

Intuit documents the fee case directly. When a bank charges a service fee against a deposit, the guidance is not to edit the original transactions. You add the fee while in the deposit window by selecting Bank Charges and Fees as the account and entering the amount as a negative number. The deposit total drops to what the bank actually credited, and the fee lands in an expense account, without a single customer payment being altered.

That pattern generalizes. Any line that belongs to this deposit but not to a customer payment goes in the same section: a rebate, an owner contribution, interest, a refunded vendor overpayment. Positive lines increase the total, negative lines reduce it.

This is precisely the mechanism a payment processor deposit needs. A processor does not hand you the gross value of your sales. It hands you the sales, minus its fees, minus any refunds that settled in the same batch, as one net number. A deposit with the payments ticked and the fees entered as negative lines expresses exactly that, and lands on a total that equals the bank line.

Editing, removing, and the balance that will not clear

Deposits are editable after the fact, which matters because they are usually the first thing to be wrong when a reconciliation does not tie.

To remove a payment from a deposit, you open the deposit, uncheck that payment, and save. Intuit is clear about where the payment goes: it returns to Undeposited Funds, available to be deposited elsewhere. It is not deleted, and the underlying sale is untouched. That is the correct tool when a payment was included in the wrong batch, which is far more common than a payment being genuinely wrong.

A stubborn holding-account balance is almost always one of three things. Payments recorded with no deposit ever created against them. A deposit entered manually, by typing the amount into the deposit form instead of selecting the waiting payments, which leaves the originals sitting in the holding account forever while the bank line matches something new. Or a deposit whose selected payments do not add up to the bank line because a fee was never entered as a negative.

The second of those deserves a warning of its own, because it produces books that look reconciled. The bank feed matches the manually typed deposit, the bank account reconciles cleanly, and the error is invisible anywhere except the holding account, which quietly climbs by the amount of every payment that was never swept.

Why Stripe payouts land on this form

A Stripe payout is a batch deposit with the volume turned up. Two days of charges, minus processing fees, minus any refunds that settled in the window, arrive in your bank account as one number. Every sale inside it has to be on your books individually for revenue and sales tax to be right. The bank only ever sees the net.

That is the same shape as a bag of checks, at a frequency no one would choose to handle by hand. It is also why the deposit form suits it so well: the payments section carries the individual charges, the extra-lines section carries the fee, and the total lands on the payout amount that your bank feed will show.

The alternative is worth naming, because plenty of Stripe workflows never touch this form at all. If your holding account is a regular asset clearing account rather than Undeposited Funds, the payout is recorded as a simple transfer for the net amount, and the composition of the payout lives on the individual sales records instead of on the deposit. Both reconcile, and which one you get is decided by your holding account rather than by the payout. The trade-off between them belongs to Undeposited Funds, and is covered there.

How Acodei builds a payout deposit

Acodei writes a QuickBooks Deposit for a payout only when your holding account is Undeposited Funds. On an Undeposited Funds setup, each payout becomes a Deposit that itemizes the underlying activity out of Undeposited Funds and into your bank account. On a regular asset holding account, the same payout is recorded as a single Transfer for the net amount instead, and no deposit is written at all.

The lines are built from the payout's own balance transactions, grouped by type and by mapped product. That is why the deposit reads as a summary of what the payout contained rather than as a single figure: charges, refunds, fees, and any uncommon balance transaction types that appear inside that payout each resolve to their own lines. Uncommon types use the products you set under Balance Transaction Mapping, with one documented fallback: `payment_unreconciled` falls back to your account's default product. If the payout's own balance transaction carries a fee, it is recorded against your mapped Stripe fee product.

Two prerequisites decide whether the deposit can be built at all.

The deposit bank account has to be assigned in Account Mapping, per Stripe account and per currency for multicurrency users. A payout with no assigned deposit account errors with a prompt to assign one rather than guessing.

Everything inside the payout has to already exist in QuickBooks. This is the Undeposited Funds prerequisite in its strictest form: a deposit can only itemize records that are there to be itemized, so a payout with missing underlying transactions is blocked with a mismatch error, and each missing transaction is recorded for retry. Rather than failing the payout outright, the dispatcher can park it while it waits for the other transactions to sync. A payout with no resolvable line items errors with a "No line items" message instead of closing silently.

Not every payout produces a deposit, and the exceptions are deliberate. A negative payout, on a day when refunds and disputes exceeded sales, is money moving from your bank back into Stripe, so it posts as a Transfer from the bank account into the holding account for the absolute amount, in both holding-account modes. A failed or canceled payout is closed out without creating a record, because nothing moved. A top-up, which is you funding your Stripe balance from your bank, is the mirror of a payout and posts as a Transfer from the bank into the holding account. Where a payout's destination is a Stripe Financial Account you have mapped, the transfer destination becomes that mapped QuickBooks account rather than your default deposit account.

On reconciliation, the deposit is the checkpoint. With Undeposited Funds, the method Acodei supports is payout matching: match each payout deposit against the bank feed and reconcile the bank account. Balance-reconciling the Undeposited Funds account itself is not supported, and the reason is structural rather than a gap. Sales sit in Undeposited Funds until a payout sweeps them, and some items are only added at deposit time, so the balance can legitimately diverge from your Stripe balance at any given moment.

Want to see this on your own Stripe data?

Start a free trial

Frequently asked questions

What is a bank deposit in QuickBooks?

It is the transaction that combines payments you have already recorded into the one lump sum your bank received. Intuit describes the purpose as grouping payments so your records match the bank, since a bank that receives several payments together shows them as a single total.

Does a bank deposit record income in QuickBooks?

No. The income was recognized when the sale was recorded, on the invoice or sales receipt that created the payment. A deposit only moves money from the holding account where the payments were waiting into your bank account. A deposit that appears to create revenue usually means the waiting payments were never selected, and that the income is now on the books twice.

Why are my payments not showing up on the Bank Deposit screen?

Because they are not in Undeposited Funds. Only payments sitting in that holding account appear in the deposit picker. A payment recorded straight to a bank account has already been treated as deposited, so there is nothing left for a deposit to sweep.

How do I record a bank fee on a deposit in QuickBooks?

Add it inside the deposit window rather than editing the original payments. Intuit's guidance is to select Bank Charges and Fees as the account and enter the amount as a negative number, which brings the deposit total down to what the bank actually credited and puts the fee in an expense account.

How do I remove a payment from a deposit?

Open the deposit, uncheck that payment, and save. The payment returns to Undeposited Funds and can be included on a different deposit. Nothing about the original sale changes, which makes this the right fix when a payment was simply batched into the wrong deposit.

Should a Stripe payout be entered as a bank deposit?

Only if your holding account is Undeposited Funds. In that setup the payout is a deposit that itemizes the charges, refunds, and fees it contains. If your holding account is a regular asset clearing account, the payout is a single transfer for the net amount instead, and the detail lives on the individual sales records.

What customers say about running Stripe through Acodei

★★★★★

“If you're testing out all the different Stripe/QuickBooks integration apps right now, let me save you some time. This one is the best one by far.”

RyanOwner at Indie Music Academy