Credit notes, refunds and adjustments — the reverse flow nobody designs

Sales processes get designed. Purchase processes get designed. The reverse flow — credit notes, refunds, adjustments, write-offs — usually just happens, handled case by case by whoever is available.

That is a problem, because the reverse flow is where the weakest controls in most businesses live. A credit note reduces revenue and can be raised in seconds. A refund moves real money out. Neither typically carries the scrutiny that raising an invoice or approving a payment does.

Why the reverse flow is under-controlled

Nobody thinks of it as spending. Approving a RM 5,000 purchase requires a process. Issuing a RM 5,000 credit note has the same effect on the result and frequently requires nothing.

It is often urgent. Credits and refunds usually arise from a customer problem, and the pressure is to resolve quickly. Process feels like an obstacle at exactly the moment somebody is annoyed.

It is genuinely varied. Returns, pricing errors, goodwill gestures, short deliveries, damaged goods, disputes. Each has different accounting and each looks like an exception, so nothing gets standardised.

The reason is rarely recorded. A credit note says what it credits and almost never says why. Which means nobody can analyse it, and nobody can tell whether the same problem is recurring.

The single change worth making

Require a reason code on every credit note and refund, from a fixed list.

Not free text — a defined set: return, pricing error, damage, short delivery, goodwill, billing error, cancellation.

That one change turns credits from a set of individual events into data you can analyse, and the analysis is usually uncomfortable in a useful way:

• Pricing errors concentrated on one product suggest a price list problem
• Damage concentrated on one route suggests a packaging or carrier problem
• Goodwill concentrated on one salesperson suggests something about how deals are being closed
• Returns concentrated on one product suggest a listing or quality issue

None of that is visible when credits are processed as individual annoyances. Every one is actionable once the reason is captured.

What automation should enforce

Approval proportionate to the amount. A credit note above a threshold should require the same authority as a payment of that size. Most businesses have this for payments and not for credits, which is an odd asymmetry once noticed.

A link to the original transaction. A credit note should reference the invoice it relates to. Unlinked credits are how revenue gets reduced without anyone being able to reconstruct why, and they make the receivables ledger unreliable.

The reason code, mandatory. Not optional, or it will be blank.

Duplicate prevention. The same return credited twice — once by customer service, once by finance — is a common and preventable error.

Refund matched to the original payment method. Refunding to a different account than the one that paid is both a fraud vector and an operational mess.

The reconciliation that finds problems

Credits issued should reconcile to something real. Two checks:

Do credits for returns match actual returns received? A credit for goods that never came back is a write-off dressed as a return. If the credit process and the goods-in process are not connected, this is invisible.

Do refunds match credits? A refund without a corresponding credit note means money left without the revenue being reduced. A credit without a refund means a customer is owed money that has not been paid — which is a liability and, in some cases, one you cannot quietly keep.

Both reconciliations are mechanical and both are commonly not run.

Marketplace adjustments are the same problem

For businesses selling through marketplaces, the reverse flow arrives as deductions rather than credit notes — returns processed by the platform, adjustments applied to settlements, fees reversed and re-applied.

The structural issue is identical: money moving in the unexpected direction, with a reason that may or may not be recorded, and no natural point of approval because the platform simply applies it.

The response is the same too — categorise every deduction, reconcile it to something real, and treat anything unexplained as a question rather than a cost of doing business. We cover the specifics in disputing a marketplace deduction.

The question to ask this month

Pull every credit note issued in the last twelve months, sort by value, and look at the top twenty.

For each, can you say why it was issued? If more than a few are unexplainable, the reverse flow is not controlled — and given that credits reduce revenue directly, that is worth more attention than most cost controls receive.

On an own store the refund is only part of the cost — the outbound delivery is already spent, the return leg may be yours, and the processing fee frequently does not come back — see returns on your own store and what they cost and what happens to the fee when you refund.

Common questions

Why are credit notes a control weakness?

Because they reduce revenue as directly as a purchase increases cost, yet they rarely carry equivalent approval. They also tend to arise under time pressure from a customer problem, which makes process feel like an obstacle, and the reason for issuing them is usually not recorded, so nobody can tell whether the same underlying problem keeps recurring.

What is the single most useful improvement to credit note handling?

Requiring a reason code from a fixed list on every credit note and refund. It converts credits from individual events into analysable data, which typically reveals concentrations — pricing errors on one product, damage on one delivery route, goodwill from one salesperson — that are invisible when each credit is handled as a one-off.

What should be reconciled around credits and refunds?

Two things: whether credits issued for returns correspond to goods actually received back, since a credit for goods that never returned is a write-off dressed as a return, and whether refunds correspond to credit notes. A refund without a credit note means money left without revenue being reduced, and a credit without a refund means a customer is owed money that has not been paid.

Should credit notes require approval?

Yes, proportionate to the amount, in the same way a payment of equivalent value would. Most businesses have approval thresholds for payments and none for credit notes, which is an asymmetry that becomes obvious once noticed given that both affect the result by the same amount.

Related: handling returns and warranties · disputing a marketplace deduction · controls that survive automation