Returns & Credit Notes: Three Records, One Event
A customer returning goods triggers three separate events — the money, the stock and the story — and only one of them is a credit note. The credit note here carries an amount and no lines, which decides how you have to work.
Returns are where tidy sales records go to die. The customer brings back three of the ten cartons, wants a credit rather than a refund, two of the three are resaleable and one is crushed. Somebody issues a credit note for the whole lot, somebody else puts three cartons back on the shelf, and by month end the stock count, the customer statement and the margin on that sale disagree with each other — each of them defensibly.
The confusion is almost never carelessness. It is that a return is three different events wearing one name, and most businesses have a process for only one of them.
The three events, separated
What one return actually consists of
The money — what the customer no longer owes
A credit note against the customer, optionally linked to the invoice it relates to, with an amount, a reason, a number from the same numbering service that issues your other documents, and an issued and applied date.
The stock — what physically came back, and in what condition
Not part of the credit note. Goods returning to saleable stock are a stock adjustment; goods returning damaged are either written off or held separately. This is a deliberate hand-entry, and the most commonly skipped of the three.
The story — why it came back
The reason field on the credit note. Trivial to fill and the only one of the three with any strategic value, because a reason recorded consistently across a year tells you whether you have a quality problem, a picking problem or a sales-expectation problem.
Read the middle row twice. A credit note reduces what the customer owes and moves nothing in your warehouse. If your process ends when the credit note is issued, your stock is overstated by every return you have ever taken — quietly, cumulatively, and in a way no report will flag, because nothing knows the goods came back.
The flat-amount constraint, and what follows from it
A credit note here holds a single amount. It does not hold lines. There is no per-item breakdown, no quantity, no link from the credit down to the specific invoice line being reversed.
That is a real constraint and it is worth understanding rather than resenting, because it changes the correct habit. A credit note is a financial instrument in this system, not a reversal of a document. So the arithmetic has to be done before you write it, and it has to be written down somewhere the auditor can find.
Ten cartons out, three back, two saleable
The line that catches people is the last one. The credit was for three cartons because that is what the customer sent back and what was commercially agreed; the stock went up by two because that is what you can sell again. Those two numbers are supposed to differ, and the difference is your return loss — which is a figure worth knowing and which nobody ever calculates, because the two records are made by different people on different screens.
The counter behaves differently from the invoice desk
Worth knowing if you sell both ways: a point-of-sale return is line-level. It records the items and the quantity coming back, so the till side of the business has the item detail that the invoice side does not.
This asymmetry is not a design statement, it is just where the two features arrived from. But it has a practical consequence: a walk-in return and an account-customer return produce differently shaped records, and any attempt to report on "returns" across both will be comparing a line-level record with a money-level one. Report on them separately until you have a reason not to.
What is and is not built
What AWRA OpsHub does today
- Credit notes against a customer, optionally linked to the invoice they relate to, tenant-scoped like everything else.
- Document numbering from the same service that numbers your other documents, so credit notes are sequential and traceable.
- A status, an issued date and an applied date, so an agreed-but-not-yet-applied credit is distinguishable from a settled one.
- A reason field — the highest-value and least-used part of the record.
- Created-by and updated-by tracking, so who granted the credit is on the record rather than in somebody's memory.
- Point-of-sale returns with item and quantity detail, for counter trade.
What it does not do
- No credit note line items. The credit is an amount, not a reversal of specific invoice lines, so partial-line credits are arithmetic you do before writing it.
- A credit note does not touch stock. Goods returning to the shelf are a separate stock adjustment that somebody has to remember.
- No return authorisation step. There is no RMA number, no approval gate before goods come back, and no record of a return that was requested and refused.
- No automatic restocking-fee or partial-credit calculation.
- No return-reason analytics — the reasons are recorded and nothing aggregates them, so that analysis is an export.
- No link between a returned unit and the batch or serial it came from, unless you record it in the reason or the adjustment note.
The absence of a return authorisation step is the one to build a habit around rather than wait for. Goods that arrive back at your premises with nobody expecting them are how returns go unrecorded entirely — the storekeeper puts them somewhere, the credit is never raised, and the customer chases it three weeks later with a stronger claim than they started with.
A process that survives contact with a busy week
Six rules for returns
- Nothing comes back without somebody knowing it is coming. A phone call and a note is a sufficient authorisation process. No system feature required, and it eliminates the worst failure mode.
- The credit note and the stock adjustment are raised by the same person, in the same sitting. Split them across two people and one of them will be skipped — reliably, and always the stock one.
- Count the condition, not the quantity. Three back is not three saleable. The gap between the credit and the restock is your return loss and it is worth a column.
- Use the reason field with a short controlled vocabulary. Six reasons, agreed once, typed the same way every time. "Damaged in transit", "wrong item picked", "over-ordered", "quality complaint", "duplicate delivery", "customer changed mind" will cover almost everything and turn a year of credit notes into an actual diagnosis.
- Link the credit note to the invoice whenever the invoice is known. It is optional in the data and it is what makes the customer statement readable a year later.
- Reconcile returns monthly against stock adjustments. Two short lists, side by side. Every credit note for physical goods should have an adjustment behind it, and the ones that do not are your overstatement.
The number this gives you that most businesses do not have
Return loss as a percentage of sales, by reason. It falls out of the reason field and the credit-versus-restock gap, and it is one of the few figures that points directly at a fixable cause — because "damaged in transit" is a packaging or carrier conversation, "wrong item picked" is a warehouse layout conversation, and "customer changed mind" is a sales-expectation conversation. One number, three completely different remedies.
Our take
Treat a return as three records and make all three in one sitting: the credit note for the money, a stock adjustment for what is genuinely resaleable, and a reason from a fixed short list. The credit note carries an amount and no lines, so the apportionment is arithmetic you do first — and critically, it moves no stock at all, which is the single most common way inventory quietly drifts upward. Add a phone-call authorisation habit before goods travel, reconcile credit notes against adjustments monthly, and the return loss figure you get for free is worth more than the tidiness.
Credit notes that reconcile to your stock
Numbered, tenant-scoped credit notes with reasons, invoice links and full attribution — and a plain statement that they carry an amount rather than lines, and that returning stock is a deliberate second step.
See plans & pricingFrequently asked questions
Does issuing a credit note put the goods back into stock?
No. A credit note reduces what the customer owes and creates no stock movement whatsoever. Goods coming back onto the shelf are a separate stock adjustment that somebody has to raise deliberately. If your process stops at the credit note, your inventory is overstated by every return you have ever accepted, and nothing will flag it because nothing knows the goods returned.
Can we credit part of an invoice line?
Yes commercially, but the credit note holds a single amount rather than lines, so you calculate the apportionment before writing it and record the workings in the reason field. There is no per-item breakdown and no link from the credit down to a specific invoice line. Link the credit note to the invoice — that is supported and optional — so the customer statement reads correctly later.
Why should the credit and the restock be different quantities?
Because they measure different things. The credit is what was commercially agreed with the customer; the restock is what you can actually sell again. Three cartons returned with one crushed is a three-carton credit and a two-carton restock. The gap is your return loss, and it is a genuinely useful figure that almost nobody calculates because the two records are made on different screens.
Is there a return authorisation or RMA process?
No. There is no RMA number, no approval gate before goods travel back, and no record of a return that was requested and declined. Substitute a habit: nothing comes back unless somebody here knows it is coming and has noted it. That costs a phone call and removes the worst failure mode, which is goods arriving unannounced, being shelved by a storekeeper, and the credit never being raised at all.
Do counter returns work the same way as invoice credit notes?
No, and it is worth knowing. Point-of-sale returns record items and quantities, so the till side has line-level detail the invoice side does not. That means reporting on returns across both channels compares a line-level record with a money-level one. Keep the two reports separate until you have a specific reason to combine them.
What is the highest-value habit here?
A short controlled vocabulary in the reason field — six reasons, agreed once, typed identically every time. Nothing aggregates them automatically, so it is an export rather than a dashboard, but a year of consistently-worded reasons converts a pile of credit notes into a diagnosis: transit damage is a packaging conversation, wrong-item-picked is a warehouse layout conversation, and changed-mind is a sales conversation.
