A credit memo is easy to issue. A customer calls about a damaged case, the rep wants to keep the account happy, and a few minutes later the balance is lower. Often that is exactly right: the customer did not get what they paid for, and a fast credit is good service.
The trouble starts when nobody looks at credits as a whole. Each one is small and reasonable. Together they can add up to real margin, and the causes behind them, a careless picker, a rough route, a supplier with a quality problem, never get fixed.
What a credit memo does in the books
A credit memo reduces what the customer owes. Behind that, a few things happen:
- Receivables go down by the amount of the credit, either against a specific invoice or as a balance on the account.
- Revenue goes down, usually through a sales returns and allowances account, so you can see credits separately from gross sales.
- If goods come back and can be resold, their cost goes back into inventory.
- If goods are thrown away, or never come back, their cost stays an expense, often recorded as spoilage or shrink.
- A price correction moves no stock at all; it only changes revenue and receivables.
So a credit for a damaged case costs you twice: the revenue you gave back and the product you cannot sell again. That is why the reason matters.
Reason codes
Every credit memo should carry a reason code. Keep the list short enough that people use it correctly. A starting list, with the question each one should raise:
| Reason | Usually points to | Question to ask |
|---|---|---|
| Damaged in transit | Loading or delivery | Which route, which driver, how was it loaded? |
| Wrong item shipped | Picking | Who picked it, and was the item scanned? |
| Short shipped | Stock or picking | Was the short known before the truck left, and was the customer told? |
| Quality or temperature | Supplier or cold chain | Which lot and supplier? Can we claim it back? |
| Short-dated or expired | Rotation | Was stock picked in expiry order, and was it too close to its date to ship? |
| Pricing error | Pricing or order entry | Was the wrong price set up, or keyed on the order? |
| Customer changed mind | Customer | Is this a pattern for this account? |
| Goodwill | A deliberate decision | Who decided, and why? |
Avoid a catch-all "other". If people keep needing one, a reason is missing from the list.
Ask for evidence at the time
The best moment to understand a credit is when it happens. A photo of the damaged case, the lot number from the label, and the proof of delivery record settle most questions in minutes. A week later, nobody remembers.
Decide, case by case, whether the goods come back. A truck pickup costs a stop. Credit only, with the customer disposing of the product, is often cheaper for low-value items, but you lose the chance to inspect them and to claim them back from the supplier.
Approval limits
Reps need room to fix problems on the spot. Larger credits deserve a second look. For example, a business might let reps issue credits up to $250 on their own, send credits above that to a manager, and send credits above $1,000 to the owner. Set your own limits based on your order sizes.
The point of approval is not distrust. It is a short conversation when the amount is large enough to matter, and that conversation often surfaces context: an account that is unhappy for other reasons, or a problem with a whole delivery rather than one case.
What to look for
Patterns, not single credits. Group credits by reason and then look across a few angles:
- By customer. Compare each customer with their own history and with similar accounts. A customer whose credits keep climbing either has a real problem with your service or has learned that asking works.
- By route and driver. Damage clustered on one route points to loading or handling.
- By picker. Wrong-item credits clustered on one shift or picker point to training or labeling.
- By item and supplier. Quality credits clustered on one item point to a supplier conversation, and a supplier credit to recover the cost.
- By rep. Goodwill and pricing credits clustered on one rep are worth a conversation about pricing and authority.
A review rhythm
- Monthly: total credits by reason, customer, route and rep, against last month.
- Quarterly: the customers with the most credits by value. These are the account conversations worth having.
- Yearly: the trend. If credits are rising, something changed in operations, and it is worth finding.
Credits are part of what it costs to serve a customer. Per-customer profitability shows how to include them.
Keep the receivables clean
Post a credit when it is issued and apply it to the invoice it relates to. An unapplied credit leaves the invoice looking unpaid on the aging and invites a collection call to a customer who is waiting on you. And keep credits apart from bad-debt write-offs. A credit is a correction; a write-off is a loss on a customer who did not pay. AR aging 101 covers the difference.
How APFoodz handles it
In APFoodz, every return and credit memo carries a reason and can require approval, and you decide who approves what (see permissions and approvals).