What it means
Identify the original receipt by recording its bank or processor transaction ID, date, amount, currency, payer, customer account, invoices allocated and user who posted it. Inspect the source movement rather than relying only on a ledger label.
A payment chargeback or returned cheque may involve fees, dispute rights and timing, while a simple misallocation may leave the cash in the bank but require moving it to the correct account, so do not treat them as the same cash event. Confirm the reason and authority by checking whether the original receipt was duplicated, assigned to the wrong invoice, later failed, or needs a legitimate customer refund.
A customer email claiming money is due back does not itself prove a refund is authorised, especially if it supplies new bank details. Follow independent identity and payment controls, because an accounting correction does not authorise sending money to anyone.
Make the correction traceable. Use the appropriate reversal or unapplication function under policy, keeping the original receipt, linked correction, approval and supporting evidence, and avoid deleting the first posting or backdating a new one to make a prior report look clean.
If cash did arrive but was applied to another customer, unapply and reapply it under the system's controls rather than assuming a true receipt reversal is needed. Notify credit or collections teams before they contact either customer, and reconcile bank and ledger totals after the change.
Review downstream effects, since an invoice may reopen, an order may have been released from credit hold, or a statement may already have been sent. Check whether a customer was told its balance was clear or a supplier payment was made based on the false cash position.
For a failed payment, update the customer accurately and offer an approved route to settle. For a duplicate posting, the actual bank cash never doubled, so cash forecasts and reconciliations need correction.
Separate refunds and chargebacks: a refund is an outbound payment that requires its own authorisation and destination verification, while a chargeback is a processor or payer action that may be disputed under its rules. Reversing a receipt entry can be part of either workflow, but does not complete it.
Track fees, recovery attempts and unresolved amounts with owners, and apply the relevant accounting policy for the period and disclosure. For owners, the reversal protects the truth of cash and receivables reports, correcting mistakes without hiding them and preventing the next customer or credit decision from relying on a false payment status.
In practice
Real-world examples.
Example
Finance reverses a duplicate ledger receipt when the bank statement shows only one transfer.
Example
A transfer posted to the wrong subsidiary's customer account is unapplied and correctly reapplied after payer verification.
Example
A processor chargeback reopens an invoice, while the dispute team separately reviews evidence and fees.
Formula
Calculation
Corrected net receipt = Original recorded receipts - Reversed entries that never settled
Worked example. An invented $5,000 payment was entered twice, while the bank shows one $5,000 credit.
- Reverse the duplicate $5,000 entry; corrected cash receipts tied to the bank equal $5,000, not $10,000.
- Keep the original valid payment allocated to the right invoice and retain the reversal trail.
A customer refund or processor chargeback requires separate evidence and accounting treatment.Case study
Seen in the real world.
This illustrative and entirely fictional example follows Olive Equipment, an invented machinery seller. Two customers had similar account names. A clerk applied a $20,000 transfer to the wrong account, clearing one invoice and leaving the payer's invoice overdue. Collections drafted a demand to the customer who had actually paid. Finance checked the bank reference and remittance from the payer through an established contact, unapplied the wrong invoice allocation and applied the settled receipt to the proper invoice.
It reviewed the first customer's balance and halted the incorrect statement before dispatch. A second person approved the correction under the ledger policy. The team kept both postings and evidence rather than deleting the mistaken record. The owner received a reliable receivables report and avoided a needless customer dispute. The correction also exposed a master-data issue: two account names needed clearer legal-entity identifiers.
Watch out
Common mistakes.
- Deleting the original receipt instead of creating an auditable correction.
- Reversing a settled receipt merely because its invoice allocation was wrong, or treating either correction as permission to refund.
- Failing to update invoices, credit holds or customer communications after changing the ledger.
Questions
People also ask.
Does reversing a receipt mean the customer gets money back?
No. It corrects a recorded receipt; a refund is a separate approved outbound payment.
What if the bank cash is still there?
Determine the correct payer and invoice, then reallocate with a traceable record rather than treating it as lost cash.
Who should approve a reversal?
Follow the company's accounting control based on amount, cause and period, with an independent reviewer where required.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%