The Goods You Can Send Back
Goods can arrive against a purchase order, and goods can leave to a customer. And they can go back to the supplier who sent them, as a return with a debit note — rather than leaving your books as a write-off, the one exit with nobody on the other side of it.
Stock moves in a small number of directions, and a system tends to be judged on the ones it handles. Ours handles arrival carefully: what physically turned up is counted rather than copied from the order, an over-delivery is refused against everything already received, and a short delivery is recorded and reported without ever being blocked.
It handles departure to a customer carefully too, including the reverse — a till return puts the stock back and reverses both the revenue and the cost of sales, with the cost leg conditional on whether the goods were actually fit to restock.
And it handles the direction most demonstrations skip: sending something back to the supplier. The shape of that is worth describing, because a return is the direction with the money attached.
What happens to a rejected delivery
Follow it through, because the sequence is where the control lives.
The goods arrive and are received, because they physically turned up and refusing to record them would be worse. Somebody inspects them and marks them as failed, and the supplier agrees to take them back, which is the good outcome.
That agreement has a record. A supplier return names the supplier and the order the goods came in on, the lines going back, the warehouse they leave from and the reason. It refuses to send back more than was received on that order. When it is approved, the stock leaves at what it cost, and a debit note is raised for what the supplier now owes you — with the VAT on it reversed out of input tax, as the supplier’s credit note will be.
A return to a supplier is the most documented thing that happens in a warehouse. It is documented in the database too — with a counterparty, an order and a figure owed.
What actually happened
- Goods were rejected for a stated reason
- The supplier agreed to take them back
- They physically left on a specific date
- A credit is now owed against a specific order
- The payment for that order should not be released
- A commercial event with two parties and a paper trail.
What the system records
- A supplier return, with its reason
- The supplier, and the order the goods came in on
- Whoever raised it, whoever approved it, and the date
- A debit note for the credit owed, open until applied or refunded
- The note set against that supplier’s bills when a payment run pays them
- A commercial event, with both parties on it.
The three things the return record does, in cost order
The credit is tracked. The money you are owed is a debit note with a number, a supplier and an amount, listed beside the returns and open until it is applied against a bill or refunded. Nothing about it lives only in an email thread.
The payment is reduced where it is made. When a payment run pays a supplier’s bill, that supplier’s open debit notes are set against it, so the cash that leaves is net of what they owe you. One edge remains: the order-matching gate, which compares what was ordered against what was received, still reads returned goods as received — so a payment made outside a payment run should be checked against the open notes.
Your loss figures do not hide a supplier problem. A returned delivery does not land in the same bucket as damage and breakage. It leaves through a return filed against the supplier, so the supplier who ships you unusable goods every month shows up as returns against their name rather than as shrinkage.
Why we are putting this on the Gulf
Because of the length of the chain rather than anything regulatory. A great deal of what is consumed here arrives through a long import route — a supplier somewhere else, a freight leg, a port, a clearing agent, an inland movement — and every additional handover is another opportunity for what arrives to differ from what was ordered.
Long chains also make rejection expensive and slow to resolve. The counterparty is in another country and another time zone, the credit is a negotiation rather than a formality, and the goods may sit for weeks while it is settled. That is precisely the situation in which the system should be holding the position for you — what was rejected, when it left, what is owed, and what must not be paid in the meantime — and it is exactly the situation where a write-off with a reason code tells you none of it.
What to do today
Raise rejected goods as a supplier return against the order, not as a write-off. Keep the open debit notes owned by somebody, and pay suppliers through a payment run so the notes are set against their bills. For a payment made any other way, check the open notes first, because the order matching will still read the goods as received. It is a procedure for one edge rather than the whole record, and it is the honest answer until the order matching reads returns too.
Two, on top of the return record
The supplier return, the debit note and the payment-run offset are built. What sits beyond them reaches the payment gate and the supplier scorecard.
Returns read by the order-matching gate
The matching treating returned quantities as not received, so the payment gate blocks payment for goods you sent back on every payment route, not only through a payment run. The gate is the single definition of payability, so this is one input to an existing control rather than a new one.
Returns on the supplier scorecard
A return rate per supplier beside delivery and price performance, so the supplier you send goods back to every month looks different from one you never do.
The first is the one to raise if you pay suppliers outside payment runs. A return record that reduces what you pay in one route is a control; one that reduces it in every route is the whole control.
Talk to us about supplier returnsFour questions about the direction nobody demonstrates
Show me a goods return to a supplier, end to end.
What a straight answer sounds like
A flow, or an admission. Ours is a flow: return, approval, debit note.
Why it matters
Every demo shows goods arriving. Almost none shows them going back, and that is the direction with the money attached.
After a return, what does the system say is payable?
What a straight answer sounds like
A reduced figure. Ours nets the debit note off in a payment run.
Why it matters
This is the expensive consequence — ask which payment routes see the return, because a control satisfied by goods you no longer have is the costly one.
Where do I see credits owed to me by suppliers?
What a straight answer sounds like
A list of open debit notes. Ours has one.
Why it matters
Untracked credits are money that quietly does not arrive, and nobody is assigned to notice.
Do returns appear in that supplier's history?
What a straight answer sounds like
Yes, or no. Ours files them against the supplier.
Why it matters
A supplier whose goods you reject monthly should look different from one whose goods you never reject. Ask whether the scorecard sees it too.
What AWRA OpsHub does today
- Customer returns at the till, with stock returned and both revenue and cost of sales reversed, the cost leg depending on whether the goods can be restocked.
- Over-receipt refused against everything already received on the order, with a tolerance you set.
- Short deliveries recorded and reported, with the order left open for the balance.
- Attachments on adjustments, where the supplier's acknowledgement can be kept.
- A return to supplier: a record type, a document and a flow, refused beyond what was received on the order and taking the stock out at cost on approval.
- A debit note raised by every approved return, or on its own for a price agreed down, with the VAT on it reversed out of input tax.
- Expected credit tracking: debit notes listed and held open until they are applied against a bill or refunded.
- A link from returned goods to the order and supplier they came from, so returns are filed against the supplier.
- Open debit notes set against the supplier’s bills when a payment run pays them.
More we can add to your workspace
- Returned quantities read by the order-matching gate, so a returned delivery stops reading as received on every payment route. Commission it
- A return rate on the supplier scorecard, beside delivery and price performance. Commission it
Where we point you to a specialist
- We make no claim about when a debit note is legally required or what it must contain. The instruments themselves are explained in credit notes versus debit notes; what your jurisdiction requires is your adviser's question.
- We describe no country's invoicing rules in this post, in this region or any other.
The verdict
Receiving is one of the better-built parts of this product, and returning sits on the other side of the same doorway with a record, a debit note and an offset in the payment run. The practical effect is that a rejected delivery leaves your business as a claim on a named supplier rather than a loss with no counterparty — with one edge left, the order matching, to watch on payments made outside a run. If your goods arrive down a long import chain where rejection is a real and recurring event, that edge is the part of our procurement module we would most want you to know about before you buy — and the one question worth asking every vendor is not whether they handle returns, because they will all say yes and mean the till.
Tell us how often you send things back
How often, to whom, and what happens to the credit. We will be straight about what the return record and the debit note handle today, and what is still a procedure.
Talk to us about supplier returns