01Establish the refund case and supported cause
Assign a case ID and identify supplier, buyer, account, purchase order, invoice, original payment and operational event. State whether the cause is duplicate payment, overpayment, canceled order, return, shortage, damage, price correction, rebate, deposit return or another approved settlement. Preserve the request, supplier response and supporting documents. Calculate the requested amount by line or component instead of using an unexplained net. Confirm who can approve the refund, negotiate a deduction and close the related claim. Do not treat a promised refund as inventory acceptance, return completion or waiver of a remaining quality dispute. If several causes are combined in one payment, maintain allocation to each source. Search for an existing recovery case so a credit note, refund request and payment-recall process do not pursue the same money independently.
02Validate approval and payment instructions
Record supplier-approved amount, currency, method, payee entity, expected date, remittance reference and the document establishing the obligation. Validate sensitive changes through trusted contact details and separation of duties. A refund normally returns value to the buyer, but any request to route it to a different company, employee, card, wallet or bank account requires enhanced authorized review. Never send credentials or unnecessary full bank details in a shared case. Keep a supplier credit note, debit note, correspondence and cash payment distinct. The UN/CEFACT remittance process links fund-transfer details to invoices, credit notes and debit notes and separates operational reconciliation from checking the amount received at the bank. Use that separation even when the supplier sends only an informal remittance note.
03Track lifecycle states without premature closure
Use explicit states: identified, requested, under review, approved, credit issued, payment instructed, supplier says sent, bank pending, received, posted, applied, short or disputed, and closed. Store state time, actor and evidence. Do not move directly from supplier says sent to received. Set follow-up dates based on the agreed method and actual banking context rather than publishing a universal transfer time. When the supplier changes amount or date, preserve the prior commitment and reason. Distinguish a failed, rejected, recalled, returned or reversed payment from a successful refund. If the supplier proposes future offset instead of cash, record that as a different settlement method and identify the later invoice only when applied. Aging should measure time in each state so delayed approval is not confused with bank transit. Define allowed transitions and rejection paths so a user cannot mark applied before booked or reopen closed without an explanation. Attach the evidence type that permits each transition: internal approval, supplier acknowledgement, remittance, bank entry, posting batch and allocation report. Timestamp receipt in the source system and later manual review separately. Preserve resubmission sequence when the first transfer fails. Use reason codes for beneficiary rejection, compliance review, insufficient sender information, closed account, currency restriction, limit, duplicate instruction, technical failure and supplier withdrawal only when the actual provider or counterparty supplies that reason. Otherwise record unknown. A dashboard badge should derive from the case log rather than become an editable substitute for it. Notify the owner when a deadline passes, but prevent automated reminders from being recorded as supplier responses.
04Match the verified bank credit
Use bank-controlled evidence to match value date, booking date, amount, currency, payer or originating bank where available, payment reference and account. Search for equal or near-equal credits across the relevant date range without assuming the first matching amount is correct. Consider batched refunds, partial payments, bank fees, currency conversion and a reference truncated by the payment network. Keep supplier evidence and bank evidence separately attributable. Investigate a refund sent in the wrong currency or to the wrong validated buyer account through authorized finance and bank channels. Record funds received only when the account record supports it, and record finality according to the bank process rather than intuition. Protect bank data and do not copy full account information into public or broadly shared documents. Link reversals back to the same case immediately. Build a candidate-match table rather than searching by amount alone. Depending on what the buyer's bank exposes, useful attributes can include statement entry ID, end-to-end reference, transaction reference, remitter name, narrative, channel, value date, booking date, original currency, instructed amount, credited amount and charge code. Normalize punctuation and spacing for search while retaining the untouched statement text. Score a candidate as exact, probable, ambiguous or rejected and record the deciding attributes; never let an opaque score post cash without review. One credit can aggregate several refunds, while one approved refund can arrive through several credits, so support one-to-many and many-to-one allocation with control totals. Look for weekend or holiday booking shifts, intermediary deductions, sender-name abbreviations, parent-company remitters, platform settlement descriptors and reference-length limits. These are investigation paths, not automatic explanations. When two open cases share amount and supplier, use the remittance allocation, initiation evidence and source-document chronology to avoid cross-application. Reconcile bank feed, downloaded statement and general-ledger import identifiers so the same credit is not ingested twice. Quarantine manual entries that imitate a bank feed. For card reversal, wallet return, marketplace release or bank transfer, name the actual settlement channel because its evidence and reversal lifecycle differ. Record pending, booked, available, reversed and returned only as the financial institution reports them.
05Reconcile amount, currency and residual
Bridge the approved supplier-currency refund to cash received, fee or deduction, conversion, ledger amount and remaining balance. Reconcile the related credit note or debit claim by original invoice and line. Separate principal shortfall from buyer-bank fee, intermediary fee, exchange-rate movement, tax adjustment, rounding and an unsupported supplier deduction. Use qualified finance and tax owners for posting date, exchange rate and treatment. Do not net an unrelated payable against the shortfall unless the agreement and approval permit it. For partial refund, keep received and outstanding amounts with the next commitment. For batched cash, allocate the total to individual cases and prove the batch sum. UN/CEFACT remittance guidance supports comparing the advice with outstanding documents and then the advised amount with the bank amount; retain both comparisons. Build the bridge in the transaction currency first: approved principal, supplier deduction, instructed amount, network charges, credited amount and outstanding principal. Then show functional-currency translation using the policy-selected rate and recognized difference. This prevents an exchange gain from concealing a supplier short payment. Where the statement shows only the credited currency, obtain authorized supporting detail before assigning an assumed original amount. For a refund covering deposits from several orders, allocate using the supplier remittance or agreed schedule rather than oldest-first convenience. Record decimals at the currency precision supported by the systems, preserve the source precision for quantity-based settlements and isolate rounding instead of editing principal. Test that the sum of case allocations equals the bank entry and that the sum applied to source obligations equals the authorized recovery. Use a suspense account only through controlled finance policy, with owner and clearance target, not as a permanent home for unidentified money. A residual below an internal review threshold still needs an approved disposition; threshold is not evidence that the counterparties agree.
06Apply the recovery once across accounts
Post the bank receipt through the authorized cash process and apply it to the correct supplier, invoice, overpayment, deposit, claim or credit balance. Check whether a credit note already reduced the open payable or a future invoice has already used the account credit. Prevent the refund from also being recovered through chargeback, payment recall, insurance, carrier claim or duplicate offset. Reconcile the buyer ledger, supplier statement and operational case. If the supplier statement still shows a credit after cash refund, request a corrected allocation rather than assuming the buyer may use both. If cash arrives before the supporting document, hold the unmatched item visibly and obtain the required record. Preserve who approved application and which source balance it closed. Keep tax, expense, inventory and foreign-exchange entries under qualified policy. Assemble a compact evidence packet before final posting: case cover sheet, calculation, approval, counterparty confirmation, remittance, redacted statement excerpt, allocation worksheet, posting batch and residual confirmation. Give every artifact an origin, captured date, preparer and immutable reference. Use checksums or repository versioning where the evidence platform supports them, while following retention rules. Separate preparer, matcher, approver and poster for material cases according to company policy. Record emergency access and retrospective review. Prohibit silent spreadsheet formula replacement by locking calculation cells or exporting the reviewed values with formula lineage. When a case imports data from email, portal, enterprise resource planning, bank feed or marketplace, retain the system record key so reviewers can navigate back to the authoritative entry. Use redaction rather than duplicating unrestricted statements into operational folders. Test access after personnel or role changes. A complete-looking PDF bundle cannot cure a missing bank event; the packet index should mark absent, pending and not-applicable items explicitly.
07Close, escalate and prevent recurrence
Close when the verified cash, approved refund, credit or debit documents, buyer posting and supplier account agree, and every source case is resolved or carries a documented residual owner. Record shortfall, rejected payment or supplier disagreement with evidence and next date. Escalate through contractual, legal, bank or marketplace channels only under authority and actual terms. Measure request-to-approval, approval-to-initiation, initiation-to-bank, unmatched cash, short payment, duplicate recovery and open age. Classify root cause across duplicate payment, order change, returns, supplier credit administration, bank-data error, receiving dispute or reconciliation delay. Correct upstream controls rather than treating refunds as routine cash flow. Sample closed cases back to bank statements and sample relevant bank credits back to cases so unrecorded or misapplied refunds are found in both directions. Maintain an exception calendar by promised initiation date, expected statement window, first chase, renewed commitment and escalation checkpoint. Age the supplier obligation and the unidentified bank item on separate clocks. A case waiting for supporting documentation after cash arrival has a different bottleneck from approved money that never reached the account. Report recovery yield as approved principal received, not gross bank credits found, and exclude unrelated incoming payments. Analyze deduction frequency, reversal frequency, missing remittance, incorrect currency, misdirected account, stale commitment and unallocated receipt separately. For repeat counterparties, review whether refunding or leaving an account credit is creating avoidable cycles, but change the commercial method only through agreement. Archive sanitized reconciliation attributes for pattern testing while keeping raw bank statements restricted. Retest duplicate detection after process changes so a recovered payment cannot re-enter the payable queue under a new document number. Run a post-close lookback after the next supplier statement and after the next bank-feed refresh. Confirm the recovered source does not reappear, the cash entry was not reversed, and no orphan credit remains. Stratify completed cases by recovery route, payment rail, turnaround band, deduction class and root-cause family. Review recurring small losses that stay below individual escalation thresholds but accumulate across a quarter. Track abandoned requests separately from denied requests; silence is not a supplier decision. Feed verified outcomes to treasury forecasting only after preventing a contingent promise from being counted as available liquidity. Dispose of expired working copies through approved records practice while retaining the authoritative audit trail.