Returns Management Software: Three Numbers

A sale moves in one direction: goods go out, and money comes in or is recorded as a debt. A return is a reverse movement travelling several paths at the same moment, and each path has a rule.

The real difficulty is that a return refers to an earlier event. It does not stand alone: it is a partial or total reversal of an issued invoice. So the system needs to know which invoice, at what price it was sold, and with what tax it was calculated — because the reversal must mirror what actually happened rather than today's price.

This is where most simple systems fail: they record the return as an independent transaction at today's price, producing a gap between what was collected and what was refunded, and that gap sits in the accounts with no explanation.

When an item is returned, three numbers must move together and at the same moment:

The customer balance — falls by the value of the return. If they paid cash they gain a credit balance or receive a refund; if it was on credit, their debt decreases.

The stock quantity — rises by the returned quantity, provided the item is fit for resale (a condition that must not be assumed automatically — see the section on it).

VAT — is adjusted by the tax on the return. This is the most frequently forgotten, and forgetting it means declaring output tax on a sale that did not complete.

In one system all three happen from a single movement. In separate systems you need three steps in three places, and every forgotten step is a number that drifts.

In Snad a return reverses all three together, because sales, inventory and accounting are apps in one database rather than systems joined by bridges.

The most common mistake: opening the original invoice and editing the quantity, or deleting it.

This is wrong for two reasons. The first is accounting: an issued invoice is a final document, and editing it retroactively breaks the sequence and makes what you gave the customer differ from what is in your system. The second is regulatory: an invoice reported to the e-invoicing system is not corrected by deletion — the correction is a separate document.

The correct document is the credit note: a new document that references the original invoice and reverses part or all of it. The original stays as it is, and the effect stays recorded and explained.

Its practical value shows at audit: the auditor sees an invoice and a credit note with its reason and date, rather than an invoice whose quantity dropped with no trace of when or why.

Two cases where many systems stumble:

A partial return — the customer brings back three units out of ten. The system needs to reverse three tenths of the invoice with tax at the same proportion, and keep the original open for the remainder. A system that works on all-or-nothing logic forces you to cancel the whole invoice and reissue it — a workaround that functions and leaves a mess in the sequence.

A return after payment — the invoice was paid and then the item came back. Here reducing the debt is not enough because the debt is already zero. The correct treatment is to create a credit balance for the customer to be applied against their next invoice, or to refund it in cash with a payment voucher. Choosing between the two is a commercial decision rather than an accounting one — but the system must allow both.

Assuming every return re-enters stock as sellable is both wrong and expensive.

An item may come back broken, opened or expired. Adding it to available stock means you will promise it to another customer and discover at delivery that it is unfit.

The correct treatment separates sellable returns from damaged ones: the first raises available stock, while the second is recorded as damage, leaves inventory and is charged as an expense. This is a genuine accounting distinction: the first restores an asset, the second recognises a loss.

A point of candour about Snad: Snad does not track expiry dates or batch numbers. So if your business depends on those — pharmaceuticals or short-life food, for instance — that tracking stays outside the system or on a specialised tool, and you should know this before relying on it rather than after.

Everything above concerns goods coming back to you. The other side is usually forgotten: goods going back from you to your supplier.

The logic is identical in reverse, and the document here is a debit note to the supplier rather than a credit note:

Three things get missed in this direction specifically:

1. Input tax. The tax deducted at purchase must be adjusted by the value of the return. Anyone returning goods without adjusting their input tax files a return claiming more than they are owed.

2. Average cost. Returning an item at a price differing from its original purchase price distorts the average cost of the remaining stock — so every later sale of it shows the wrong profitability.

3. Following up the supplier. Was the note actually issued? Was it deducted from what is due, or was the invoice paid in full while the note stayed on paper? This is what most often slips, because it falls between two departments: the warehouse sent the goods back and accounts never heard.

In Snad purchase returns issue a debit note to the supplier, and the next purchase order can start from the adjusted balance rather than the old one.

Correct recording makes your figures sound. It does not reduce returns themselves — that needs measurement rather than impression.

The second is the most neglected and the highest yielding. A supplier whose goods come back often costs you more than their quoted price: freight both ways, inspection and receiving time, and an unhappy customer who may not return. Comparing suppliers on price alone compares half the number.

What the three share is that they are figures that already exist in your movements — they appear when a return is recorded as an operation linked to the original invoice and to the supplier, and vanish when it is handled by hand on a side receipt.

That is why correct recording comes before measurement: whoever handles returns by hand has no data to measure with.

In any demo, ask to have a return created in front of you rather than an invoice, then check:

1. Was a credit note created referencing the original invoice, or was the invoice edited?

2. Did the customer balance change automatically?

3. Did the stock balance rise automatically?

4. Did the tax effect appear in the VAT report?

5. Can part of the quantity be returned while the invoice stays open for the remainder?

6. Is there a “damaged return” option that keeps the item out of available stock?

If the answer to the first four is “yes, automatically”, you are looking at a genuinely integrated system. If any of them is “yes, after a manual step”, know that you will repeat that step on every return — and count how many returns you take a month before deciding that is acceptable.