A bounced check or a returned ACH payment looks like a small event. In practice it touches the payment, the invoices it paid, the customer's balance, the accounting system and at least one person who needs to make a phone call. When those steps are manual, some of them get missed, and the books quietly drift.

Here is the sequence we build so a return is handled the same way every time.

1. Record the return against the original payment

The return should be linked to the payment it reverses, not entered as a new negative payment floating on the account. That link is what lets every later step happen automatically, and it keeps the history readable a year from now.

2. Use the bank's return date, not today's date

This is the step most often gotten wrong. The reversal belongs on the date the bank returned the funds. If it is booked on the day someone noticed, the accounting period can be wrong, deposits stop reconciling, and the bank statement no longer matches the books.

Ask for the return date at the moment someone marks the payment as returned, and carry it through to the accounting system.

3. Reopen exactly the invoices it paid

The invoices the payment covered should go back to open, with their original due dates, so aging and collections reflect reality. Partial applications need the same care: only the amount that bounced should reopen.

4. Mirror the reversal in QuickBooks

The accounting system needs the same reversal, on the same date, against the same deposit. Done by hand, this is where a return gets recorded in one system and forgotten in the other.

5. Tell the right people and protect the next payment

  • Notify the account owner or collections team with the customer, amount and reason code.
  • Flag the customer so the next payment is reviewed, or switch them off automatic payment.
  • Add any returned-item fee your terms allow, as its own line, not buried in the balance.

Why it is worth automating

Returns are rare enough that nobody remembers the full procedure, and important enough that a missed step shows up at month end as an unexplained difference. Turning the whole sequence into one button, with the bank's date as the only input, is one of the highest-value automations we build.