n-How to Enter a Bounced (NSF) Check in QuickBooks
Remove the bounced payment from its deposit, then void or unapply the original payment so the invoice it was covering goes back to unpaid. Add an NSF fee charge if you're passing your bank's fee back to the customer, and record your own bank's fee as an expense. QuickBooks Payments has a guided flow for this if that's how the check was processed; a manually entered check has to be unwound by hand.
The full walkthrough
1. Find the original deposit. The bounced check was almost certainly grouped into a bank deposit with other payments. Open that deposit.
2. Remove the bounced payment from the deposit. If the deposit hasn't been reconciled yet, edit it and remove the line for the bounced check. If it's already reconciled, this gets more involved; you may need to work with your bookkeeper to adjust the affected period cleanly.
3. Reopen the invoice. The payment that bounced was likely applied to an invoice, which is now showing as paid when it isn't. Open the original Receive Payment transaction and void or delete it so the invoice goes back to an open, unpaid status.
4. Add an NSF fee if you're charging the customer for it. Create a charge or add a line to the reopened invoice using a service item mapped to an income or fee account (something like "Returned Check Fee"), and bill it alongside the original amount.
5. Record your own bank's fee. Most banks charge you a fee too when a deposited check bounces. Enter that as an expense, categorized to a bank fees account, separate from whatever you're charging the customer.
6. If the check was processed through QuickBooks Payments, check the original transaction for a built-in "resolve" or bounced-payment option first; QuickBooks can automate steps 2 through 4 in that specific case.
Why this usually gets caught later than it should
A bounced check rarely shows up the day it happens. It surfaces weeks later, often during the next bank reconciliation, when the deposit that includes it doesn't match the statement anymore. By then, the invoice has been sitting marked "paid" the whole time, your accounts receivable looks healthier than it actually is, and whoever handles collections never knew to follow up.
That delay is the real cost, not the mechanics of unwinding the transaction. A business that finds out about a bounced check the day the bank reports it can follow up with the customer immediately. A business that finds out during next month's reconciliation has already let a month of collections time slip by on an invoice that was never actually paid.
The bank already knows the check bounced the moment it happens; QuickBooks just doesn't find out until someone checks the feed or runs a reconciliation. Closing that gap is a matter of connecting the two, not changing how the actual bookkeeping gets done.
What we've built on top of QuickBooks bounced check handling
Same-day alerts on returned deposits
The moment a bank feed shows a returned-item or NSF code, whoever handles collections gets notified and the matching invoice gets flagged, instead of waiting for the next reconciliation to surface it.
Automatic re-billing for the fee
The NSF fee, and your bank's own charge, gets added back to the customer's account and invoiced automatically the moment the return is detected, instead of someone remembering to do it after the fact.
How do bounced checks usually surface in your business?
That's a couple of the shapes this takes. If it's a specific bank, a specific type of customer, or a specific delay that's the real issue, tell us and we'll tell you if it can be caught sooner.
Finding out about bounced checks weeks after they happen?
Tell us how you currently find out a check has bounced, and we'll tell you whether that can happen the same day instead. And if bounced checks aren't actually your biggest cash-flow blind spot, that's fine too; we automate whatever's manual in the business, any tool, any process.
Let's talk