Credit Memos, Refunds, and Overpayments: Getting the Bookkeeping Right

Three different things people call "a refund"

Eventually every business has to reduce a charge it already made — a customer was overbilled, a product came back, a service didn't go as planned, or someone paid twice. Owners tend to lump all of this under "refund," but on the books there are really three distinct events, and confusing them is how revenue gets overstated and accounts receivable stops tying out. This guide separates them: the credit memo, the cash refund, and the overpayment. (General education, not accounting advice.)

The credit memo: reducing what they owe

A credit memo (or credit note) is a document that reduces a customer's balance without any cash changing hands. It's the opposite of an invoice: an invoice says "you owe us more," a credit memo says "you owe us less." You reach for it when you've already invoiced — or already booked the revenue — and something needs to come back down:

• You billed the wrong amount and need to correct it.
• A customer returned goods or rejected part of an order.
• You're granting a goodwill discount after the fact.

The key idea is what a credit memo does to your numbers: it reduces revenue and reduces accounts receivable for an open invoice (they simply owe less), or it creates an available credit on the customer's account if the invoice was already paid — store credit they can apply to a future invoice. Either way, you're not moving cash; you're adjusting what's owed. Issuing a proper credit memo instead of just deleting or editing the original invoice matters: it leaves a clean trail showing the sale happened and was later reduced, which is exactly what audit-readiness depends on. Quietly editing history is the thing that makes books impossible to trust.

The cash refund: money actually leaves

A cash refund is what most people picture — you send money back to the customer. The defining difference from a credit memo is simple: cash actually leaves your bank account. You use a refund when the customer has already paid and wants their money back rather than a credit to use later.

On the books, a refund does two things at once: it reverses the revenue (the sale is being undone) and it records the cash going out. If the original payment came through a card processor, remember the mechanics rarely net to zero — many processors keep their fee on the original charge even when you refund the customer, so a fully refunded $100 sale can leave you slightly out of pocket. Tracking that processor cost as a fee, not as lost revenue, keeps your expense categories clean.

The overpayment: they paid too much

An overpayment is the mirror image — the customer sends more than they owe, or pays an invoice twice. It's tempting to treat the extra as a happy little revenue bump. It isn't. An overpayment isn't income; it's a liability — money you're holding that doesn't belong to you yet, much like deferred revenue. Booking it as revenue inflates your profit & loss statement with money you may have to give right back.

The right move is to record the full amount received, apply what covers the invoice, and park the remainder as a credit on the customer's account (a liability you owe them). From there it resolves one of two ways: they apply it to their next invoice, or you refund the difference. Either path is clean; treating it as a windfall is the one that comes back to bite you.

Why this matters for your reports

Handled correctly, these three events keep your numbers honest. Handled sloppily, each one quietly distorts something:

• Skip the credit memo and just delete the invoice → you erase a real sale from history and break your audit trail.
• Book a refund as a new expense instead of reversed revenue → your revenue is overstated and your margins look better than reality.
• Book an overpayment as income → you overstate profit and may owe tax on money you have to return.
• Leave any of them unapplied → your AR aging report shows phantom balances and you chase customers who are actually square.

There's also a sales-tax angle: if the original sale had tax on the invoice, reducing or refunding the charge usually means the tax has to come down too. Letting your software handle that adjustment keeps your sales-tax compliance from drifting.

Keep the trail clean

The through-line is the same one that runs through all good bookkeeping: never rewrite history — adjust it with a documented entry. A credit memo, a recorded refund, and a tracked overpayment each leave a visible, defensible trail, which is exactly what your month-end close and any future review depend on. Hosting Books issues credit memos, applies them or refunds them, and holds customer overpayments as account credits — so revenue, AR, and sales tax all stay tied to the ledger no matter how a charge unwinds.

This article is general information, not accounting or tax advice. The right treatment depends on your facts and local sales-tax rules — confirm with a qualified professional.