Record what goes back to a supplier and why, and follow the credit until it arrives.
Purchase returns record what goes back to a supplier and why: broken in transit, wrong specification, near expiry, or rejected at the quality check. A debit note is raised against the supplier’s bill, stock comes down, and the amount stays in the supplier’s account until it is settled. Chasing it stops being a chat message to the salesman.
Four tiles of the lot are cracked. The salesman says he will adjust it in the next bill, and everyone believes him. Three bills later the adjustment has not appeared and the salesman has changed jobs. The amount is small enough that you let it go, and small amounts add up by March.
A return is entered against the receipt it came from. The reason goes on the line, and the debit note carries the value and the tax working. The vendor’s outstanding falls by that much. What is still unsettled shows with its age, oldest first.
What your team uses today.
The module takes over these, one at a time, so nothing has to stop while it is set up.
- A chat message to the supplier’s salesman
- A debit note typed in a spreadsheet
- A notebook of material sent back
The problems this is meant to ease.
What purchase returns and debit notes does.
What this looks like in a working week.
Illustrative scenarios, written to show the shape of the work. They are not accounts of client systems.
The people who open this every day.
From first conversation to daily use.
Describe your return routine
You explain how returns and credits happen now. You get a written flow showing receipt, return and debit note.
Set your reason list
Common reasons are agreed and loaded. You approve the list before staff use it.
Tie to receipts
Goods receipts are connected so returns pick up the original rate. A few past receipts are tested.
Try a return end to end
A sample return goes through gate pass, debit note and stock. Accounts check the tax working.
Follow the pending list
The buyer works from the ageing list each week. Training covers replacement and credit.
How you would know it is working.
Record where you stand before it goes live, so the change is measured against your own figures.
- Returns by reason and by supplier
- Debit notes unsettled past their expected date
- Replacements still awaited
- Returns carrying a gate pass
- Stock adjustments made for returns
It is one part of a system, not an island.
A module earns its place by what it passes to the next one. These are the connections we set up most often.
- Goods receipt
- Vendor management
- Stock
- Quality control
- Your accounting software
How we would put it in.
Questions owners ask about purchase returns and debit notes.
Who raises the document, us or the supplier?
In practice both happen. You raise a debit note, the supplier raises a credit note, and the two are matched. The software keeps yours and records theirs against it. Which document your books should carry is your accountant’s call.
Is a diary enough when we return goods twice a month?
Twice a month, with one person watching it, a diary works. It fails when the credit takes three months, when returns cross a year end, or when the man who remembers has left. Send us last year’s debit notes and we will read them together with you, because the pattern in them usually settles the question.
Does this handle expiry returns to a distributor?
Yes. Near-expiry stock is picked by batch and date, listed for the distributor, and tracked until the credit note arrives. Whether the distributor accepts them is between you and them.
Will it prepare the transport document for material going back?
It prepares the details and passes them to your tax service provider for the document itself. Your accountant decides whether a given movement of goods needs one.
How is the cost of purchase returns worked out?
The count of suppliers, stores and users shapes it. Links to goods receipt, stock and accounting add effort, and so does the tax format of the note. Purchase returns and debit notes can be taken in parts, and a part you skip comes off the total. Scope sets the figure.
What decides the time needed for purchase returns?
Whether goods receipts already sit in the system decides it. A release with returns, reasons and debit notes can come first. Supplier details and the note format come from you, and the proposal sets out when each stage lands. Existing data speeds it.
Businesses that ask for this.
Modules that work with it.
Tell us how you handle purchase returns and debit notes today.
A spreadsheet, a register or another system: say which, and we will tell you plainly what is worth changing.
What happens after you share your requirements
- A senior engineer reads your answers. Nobody phones first.
- Within one business day you get a written note: what we understood, what we would start with, and the questions we still have.
- If it fits, a proposal follows with the order of work, what we need from you and what you receive at each step.
- No call is booked and nothing is paid until you have read the note. Your details stay with us.
Start with your requirements
Seven short steps that tell us what you need. A senior engineer reads them before anyone gets in touch.
Share your requirements