Process map · Trading
Returns and credit notes in a trading company
A trading company handles returns every week: the wrong size was picked, a carton was crushed in the van, a unit failed in the customer's hands. Most of what comes back was bought from someone else, so each return is also a question for a supplier. This map follows a trader's return, with batch and serial numbers doing the tracing.
The full map is free
15 steps, 3 decisions, 1 road into another map. Sign in once to open every approval and branch, larger ERPNext screens and a printable sheet.
Select a step to see who does it, the document and the ERPNext screen.
Step by step
-
The customer reports wrong, damaged or faulty goods. The salesperson finds the original delivery from the invoice number, or from the serial or batch number on the unit, and logs the request with the reason and the customer's photos.
- Who does it
- Salesperson
- Document that comes out
- Issue
ERPNext then does this by itself
- Emails to and from the customer are kept on the record
- The request stays open until someone closes it
Without an ERP
A customer returns a unit that was bought from a competitor, or years ago. With no serial record the counter staff cannot tell, and the company credits it.
-
The storekeeper makes the return from the original Delivery Note and scans the serial or batch numbers of what came back. Wrong picks, transit damage and faults each go in with their reason, into the returns warehouse.
- Who does it
- Storekeeper
- Document that comes out
- Delivery Note (return)
ERPNext then does this by itself
- Serial and batch numbers are checked against the original delivery
- Stock goes up at the cost it went out at
- The original delivery shows how much has come back
Without an ERP
Returns are counted but not identified. Ten units went out from two batches, three come back, and nobody knows which batch has the problem.
-
Each returned item is examined: is it what was sold, is it unused, is the packaging intact, is the fault real. The finding is written on the return, because it decides both what happens to the goods and how much is credited.
- Who does it
- Storekeeper or quality inspector
ERPNext then does this by itself
- Returned stock shows under its own warehouse, apart from stock for sale
Without an ERP
Returns are put straight back on the shelf unchecked. A damaged unit is sold again to the next customer, who returns it too.
-
Accounts make the credit note from the original Sales Invoice, for the quantity the store received back. Items, prices and VAT come from that invoice, so the customer is credited exactly what they were charged.
- Who does it
- Accountant
- Document that comes out
- Sales Invoice (credit note)
ERPNext then does this by itself
- Sales, VAT and what the customer owes are reduced
- The credit note names the original invoice and carries the TRN
- The credit shows on the customer's statement at once
Without an ERP
Credit notes are typed in a word processor from memory. The price is today's, not the one charged, the VAT is wrong, and the store never confirmed the goods came back.
-
If the original invoice is still unpaid, the credit note is matched against it in the Payment Reconciliation tool and the customer simply owes less. If it was paid, accounts refund the money with a Payment Entry, or leave the credit on the account and match it to the next invoice.
- Who does it
- Accountant
- Document that comes out
- Payment Entry
ERPNext then does this by itself
- The customer's balance and credit room update at once
- Credits not yet used are listed until they are matched or refunded
Without an ERP
A credit is promised but never applied. The customer short-pays the next invoice by their own figure, and the two sets of books never agree again.
ERPNext 16 · Payment Reconciliation
The Full map adds 10 more steps: the approvals, checks and branches between these.
A contractor returns 3 pumps that leak. Their serial numbers show they came in one shipment from one supplier. The 12 pumps from that shipment still in the warehouse are held, and all 15 go back on one debit note.
What changes in a trading company. The same process, the steps this industry really uses.
-
Serial and batch numbers prove the sale
The number on the returned unit is checked against the original delivery. Goods bought elsewhere, or long ago, are spotted at the counter and not credited by mistake.
-
One faulty unit puts its batch in question
The stock ledger shows what is left of the same batch and which customers received the rest, so a fault is contained before more complaints arrive.
-
The supplier pays for the supplier's faults
The return to the supplier and its debit note are made from the original receipt and invoice, so the claim is exact and comes off the next payment.
-
Good stock is back on sale the same day
Goods sent in error and returned sealed go back to the shelf under their own batch or serial number, with their batch and expiry date unchanged.
Where this map leads
Processes feed each other. Follow the work into the next map.
Free tool
Build your company's map
Pick your industry and the processes you run. Get one printable document with every map and step, ready to show your team or your ERP partner.
- Returns and credit notes
- Order to cash
- Purchase to pay
- Inventory management
- Month-end close
Questions about returns and credit notes
Ask us anything elseCan ERPNext trace which supplier a returned item came from?
What if the customer wants a replacement and not a credit?
How do we keep damaged goods apart from good stock?
See this process run on your own data
A 45-minute ERPNext demo that follows this map with an example from your business.