A refund was requested but failed: what should finance track?

A support agent can approve a refund before the processor has completed it. Track approval, request, current processor status, and the final outcome separately. Use the original payment reference and the refund reference so finance can connect the customer promise with the balance movement.

A failed payment attempt, a canceled authorization, and a failed refund are different events. Check the original charge before deciding that money still needs to be returned. The customer may be looking at an authorization that will disappear rather than a settled charge awaiting a credit.

Include the approved amount, currency, reason, date, responsible person, and next action. For each unresolved refund, record whether funds have left the processor balance, returned to it, or have not yet moved. Link any customer-facing reference without storing unnecessary card or banking data.

Stripe documents pending and failed outcomes, including refunds delayed by insufficient available balance and amounts returned after failure. Use the exact status and balance transactions for the relevant payment method. Do not infer completion solely from the date the request was created.

Suppose the company approved a hypothetical $250 refund, but the processor later returns that amount after a failed attempt. Cash coming back does not automatically cancel the promise to the customer. Have the accountant determine the appropriate remaining liability or adjustment based on the sale and refund terms.

Reconcile the original refund entry with any reversal before posting another payment. A second attempt can create a duplicate outflow if the first is still capable of completing. Check for an active dispute as well, since a separate customer reimbursement can overlap with a chargeback.

Give support the verified status and a realistic next action. Where the processor provides a trace reference, retain it with the case. Avoid promising a bank-arrival date that the provider has not confirmed, and do not ask customers to send full payment credentials through an ordinary email thread.

At month-end, reconcile the open register to processor balances and the ledger. Review aging cases individually, assign a resolution owner, and preserve evidence of the final outcome. A refund is ready to leave the exception list when the obligation and payment trail are both explained.