Recording deposits & applying customer payments
Understand how customer payments, retainers, processor payouts, fees, refunds, and invoice payments should flow through your books.
A bank deposit only proves cash arrived. The books still need to show what the cash represents: invoice payment, customer deposit, retainer, payment-processor payout, sales tax collected, refund, chargeback, loan, owner contribution, or transfer. Recording every deposit as sales can overstate revenue and leave customer balances, fees, refunds, and liabilities wrong.
Why deposits are not always revenue
A bank deposit is the end of a cash movement, not the full accounting story. A single deposit may include several customer payments, processor fees, sales tax collected, refunds, tips, chargebacks, or timing differences. A transfer from another account may look like a deposit but is not revenue at all.
The most common mistake is recording the net deposit as one sales line. That can understate gross revenue, hide merchant fees, leave invoices open, miss refunds, or treat money held for later as current revenue.
The right question is not "How much landed in the bank?" It is "What activity created this deposit?"
Match payments to customer activity
If you invoice customers, payments should usually be matched to the right invoice so accounts receivable stays clean. A payment against an invoice is not new revenue if the revenue was already recorded when the invoice was issued.
Customer deposits, retainers, and prepayments may need separate treatment until the work is performed or the sale is earned. Refunds and chargebacks should connect back to the original customer activity when possible. Otherwise, reports can show revenue in one place, refunds somewhere else, and customer balances that never clear.
Clean payment application is what keeps receivables from becoming stale.
Accounts receivable is money customers owe for work already billed. Applying payments correctly keeps that balance from becoming stale or wrong.
Account for processor fees
Payment processors often deposit net cash after fees. For example, a customer may pay $1,000, the processor may keep $30, and only $970 may land in the bank. If the books only record $970 of revenue, both revenue and processing fees may be understated.
Processor payouts can also combine multiple days or batches. They may include refunds, disputes, tips, sales tax, platform fees, and timing differences. The processor report is often the source that explains the deposit.
For businesses with meaningful processor volume, clean processor mapping matters as much as bank reconciliation.
When to ask for review
Ask for review when deposits do not match invoices, customers prepay, retainers are involved, refunds or chargebacks are common, sales tax is collected, tips are included, or processor reports are missing.
Review also matters when payment treatment repeats. A one-time cleanup is annoying; a recurring rule that treats deposits incorrectly can distort revenue, receivables, liabilities, and taxes every month.
If you are not sure, provide the processor report, invoice, customer name, payment date, refund detail, and any explanation of what the deposit includes.
Reconcile customer balances regularly
After payments are recorded, review open invoices and customer balances. If old invoices still show as unpaid even though cash came in, payments may not have been applied correctly. If customer deposits or retainers sit unchanged, the team may need to confirm whether the work has been performed or revenue has been earned.
Payment cleanup gets harder with time. Customer payments are easiest to trace when the invoice, processor payout, deposit, and customer context are still fresh.
If you remember three things
A bank deposit is not always the same thing as revenue.
Customer payments should connect to invoices, retainers, fees, refunds, and sales tax where relevant.
Processor reports are often the key to clean revenue, fee, refund, and receivable records.
This guide is educational and still needs SME review before publication. Revenue recognition, retainers, deferred revenue, sales tax, tips, refunds, chargebacks, processor mapping, and customer balances can be fact-sensitive and should be reviewed by the accounting team before recurring rules are applied.
Use Uplinq notes and document requests to attach invoices, processor reports, refund details, and customer context when a deposit is more than a simple payment.