To reconcile customer refunds, start from the refund register and trace each refund to the money that left. Card refunds usually shrink a processor payout instead of showing as their own debit. Check and ACH refunds appear as separate bank lines. Each refund needs approval evidence, and each should be traced to the customer who was owed it.
Card refunds netted from processor payouts
A card refund is money sent back to a customer's card through the processor that took the original payment. Most processors subtract refunds from the next payout, so the bank never shows a refund line. Reconcile them on the payout report: gross sales less refunds less fees should equal the bank deposit.
That means the refund evidence lives in the processor's report, not the bank statement. For each payout, list the refunds the report shows, with the original transaction reference, and check that each one appears in the refund register in the books. A refund in the processor report that is missing from the register was issued outside the normal approval path.
If refunds exceed sales for a period, the payout can be zero or the processor may debit the bank to cover the shortfall. That debit is a refund line in disguise; label it so a reviewer does not mistake it for a fee.
Partial refunds need the same care. A customer who returns one item from a three-item order gets back only part of the sale, so match the refund amount to the returned item's price, not to the order total. Read the fee column on the refund row too, because processors differ on whether the original fee comes back.
Delivery apps and marketplaces follow the same netting pattern, often with the platform deciding the refund rather than the restaurant or seller. The steps for food delivery app payout reconciliation show how platform-issued refunds and adjustments are separated from fees.
Check and ACH customer refunds on the bank statement
Refunds paid by check or bank transfer leave the account as their own debits, so they can be ticked directly. Match each one to the refund register by payee, amount and reference. A refund check is an outstanding check until it clears; an ACH refund should clear within a few business days.
Refunds by transfer are sometimes sent in a batch with vendor payments, in which case the bank shows one debit for the whole batch. Use the batch detail file to split it, just as incoming batches are split in ACH batch deposit reconciliation.
Returned refunds need follow-up. An ACH refund sent to a closed account comes back as a credit, and a refund check that is never cashed sits on the outstanding list. Either way the customer has not been paid, and the liability is still open.
What approval evidence should each customer refund carry?
Every customer refund should carry three things: proof the customer was owed money, such as the original sale and the return or credit note; an approval from someone other than the person who issued the refund; and a record of where the money was sent. A refund missing any of these is an exception.
The test below is a refund tie-out checklist. Values in the example column are made up for illustration.
| Check | Card refund (example) | Check refund (example) | ACH refund (example) |
|---|---|---|---|
| Original sale found | Order 5531, $89.00 | Invoice 2207, $640.00 | Invoice 2214, $1,200.00 |
| Reason documented | Return received | Overpayment credit | Cancelled order |
| Approved by a second person | Store manager | Controller | Controller |
| Paid to the original method or payer | Same card, last four match | Customer's billing address | Account on file before the request |
| Traced to bank or payout | Netted in payout of the 14th | Check 4412 cleared on the 22nd | Debit on the 9th |
| Amount agrees | Yes | Yes | Yes |
Sample at least a few refunds each month, and all refunds above a set amount.
How do you find customer refunds that never reached a customer?
Look for refunds paid somewhere other than the original payment method, refunds with no matching sale, refunds approved and issued by the same person, and refund checks cashed by someone other than the payee. These are the patterns of refund fraud, where an employee routes a refund to their own card or account.
Run four searches over the refund register and processor reports:
- Refunds to a card number or account that never made a purchase.
- Several refunds to the same card or account across different customers.
- Refunds issued just after a till closed or outside opening hours.
- Refunds with no matching return in the inventory records.
Uncashed refund checks are the innocent version of the same problem. The customer never got the money, and the business still owes it. Age them with other outstanding checks and follow up. Refund fraud also belongs in the business's wider fraud risk assessment, so that refund rights, approval limits and review frequency match the risk. When the review covers months of statements, PreciseBankFlow can extract each debit and flag possible duplicates, such as the same refund amount paid twice to one payee.