An ACH payment was returned: repair the payment record before retrying

Download the bank or payment provider's return notice and identify the original transaction, direction, amount and settlement reference. A return of a customer collection has a different effect from the return of a supplier payment. Keep the original payment and the return visible as linked events; deleting the first entry can hide the days when the bank balance was different.

Nacha distinguishes a return, where a payment is sent back, from a reversal used to correct certain sender errors. That distinction helps route the issue to the right bank process. Ask the provider to explain the actual return code and any action required. An abbreviated message such as failed does not supply enough evidence to decide whether the payment can be sent again.

For a returned customer collection, inspect how the original receipt was applied. If it closed an invoice, the accounting correction may need to reopen that invoice while preserving the earlier payment history. Check whether the provider has already created the correction automatically. A second manual reversal can leave the customer owing twice the intended amount.

For a returned supplier payment, confirm whether the unpaid bill has reopened in the payables system and whether the returned cash has reached the bank. Keep a payment-in-transit or recovery item where appropriate until the movement is evidenced. Record bank charges separately from the invoice amount. A fee deducted from the return does not reduce the supplier's contractual entitlement by itself.

Review the customer or vendor statement after the changes. The person handling the relationship should be able to see what remains due without interpreting raw bank entries. Attach the return reference to the transaction so the next reconciliation reviewer can follow the sequence.

Assign the next step according to the problem: account information may need correction, funds may be unavailable, authorization may be disputed or the account may be closed. Verify changed payment details through an established channel. Treat the bank's explanation as the starting evidence and involve the customer or supplier where their action is required.

Nacha's rules guidance restricts reinitiating unauthorized debits. Do not treat every return as permission for an automatic retry. Ask the originating bank or provider which rule applies to this transaction and what authorization or correction it requires. Consumer and business transactions can have different handling; the accounting team should not select a return process based solely on the size of the payment.

Name one person who can release the replacement or retry. Record the approval against the unresolved payment so a collections employee and a treasury employee do not each launch a new attempt independently.

Follow the new attempt through submission, acceptance and actual settlement. Match its reference to the original obligation, then reconcile the returned amount and associated charges. If the provider displays success before bank settlement, keep that status distinction in the working record. A screen showing submitted should not support a promise that the supplier has received the money.

Keep an exception log with the return reason, responsible person, expected next event and evidence of final resolution. Review repeat failures by cause. Repeated incorrect bank details call for an onboarding correction; repeated authorization disputes call for a collection-process review. Use that finding to change the relevant process rather than merely clearing the same reconciliation item each month.