How should returns and RTO be accounted for in an ERP?

Handle customer returns and RTO correctly in your ERP: reverse sales, update stock by condition, capture costs and track claims, so margins reflect reality.

Anadoris Digital · · 4 min read

Ships out today
Photo: Bench Accounting / Unsplash (CC0)

Returns and return-to-origin parcels are part of D2C life in India, especially on COD orders. They cost money twice: shipping out and shipping back, plus any unit that cannot be resold. Yet many brands never see these costs clearly because returns are handled in a courier dashboard and a corner of the warehouse, not in the system of record.

Getting returns right in the ERP means three things: the sale and tax are reversed correctly, stock reflects what actually came back and in what condition, and the costs are visible against the SKU and channel.

Customer returns versus RTO

  • Customer return: the customer received the product and sent it back. The sale happened and is reversed.
  • RTO: the parcel was not delivered, because it was refused, the address was wrong or the customer was unreachable, and it comes back to you.
  • Exchange: a return linked to a new outgoing order for a different size or variant.

The accounting differs. If you invoice at dispatch, an RTO parcel already has an invoice, and the usual treatment is a credit note or cancellation depending on timing and your CA’s advice. A customer return almost always needs a credit note linked to the original invoice.

Receiving returned stock by condition

Not every returned unit can go back on the shelf. Inspect each return and grade it.

  • Resaleable: sealed and undamaged, goes back to saleable stock in its original batch.
  • Refurbish or repack: usable after new outer packaging.
  • Damaged or expired: moved to a scrap location and written off with a reason.
  • Wrong item or missing: returned parcel does not contain what was sent, raised as a claim.

Use separate locations in the ERP for returns awaiting inspection, refurbish and scrap. Stock in these locations should not count towards what channels can sell.

Capturing the costs

Forward shipping, reverse shipping, COD charges on refused orders, packaging and the value of written-off units are all costs of returns. Record them against the order, so you can report return cost by SKU, channel, pin code and payment method. That is the data you need to decide where to restrict COD, which products need better descriptions and which channels are not worth their return rate.

Claims for lost or damaged returns

Couriers and marketplaces sometimes lose returns or send back damaged or wrong items. Most have a claim process with time limits. Record each case in the ERP with photos and the AWB, and track it until it is paid or rejected. A simple claims list prevents money from being written off without being chased.

Returns accounting checklist

  • Agreed treatment for customer returns, RTO and exchanges, confirmed with your CA.
  • Credit notes linked to original invoices for customer returns.
  • Return locations for inspection, refurbish and scrap.
  • Returns graded and processed within a set time.
  • Forward and reverse shipping recorded per order.
  • Claims list with deadlines and owners.
  • Monthly report of return rate and cost by SKU, channel and payment method.

The GST treatment of returns, especially RTO parcels invoiced at dispatch and returns crossing a financial year, depends on timing and documents. Confirm the approach with your CA before configuring the ERP.

Exchanges and replacements

Exchanges are often handled informally: a new unit is sent out, the old one comes back, and nobody records the pair. In the ERP, link the return and the new outgoing order. The outgoing replacement should reduce stock like any other dispatch, and the return should go through the same inspection and grading. Whether a fresh invoice and credit note are needed depends on the case, so agree the treatment with your CA.

Free replacements for damaged deliveries are a cost of the original order. Record them against it so that the true cost of damage in transit is visible, and so you can raise claims with the courier where the damage was theirs.

Marketplace returns

Marketplace returns follow the marketplace’s own process and timelines. Returned units may come back to your warehouse or stay in the marketplace’s fulfilment centre as unsellable stock. Record both cases: returns to your warehouse through your normal inspection flow, and unsellable stock at the marketplace as a separate location until you arrange removal or disposal. Match marketplace refunds to these returns during settlement reconciliation.

Agree a fixed rhythm for removals from marketplace warehouses. Unsellable stock left there can attract storage charges and may eventually be disposed of under the marketplace’s policy. A monthly review of unsellable stock by marketplace keeps the value visible and prompts a decision on each batch.

Where to start

  • Count returns currently sitting unprocessed and clear the backlog.
  • Create return, refurbish and scrap locations in the ERP.
  • Agree accounting treatment for each return type with your CA.
  • Start grading every return and recording costs per order.
  • Review return cost by channel and payment method each month.

Anadoris Digital can set up returns and RTO flows in your ERP so that stock, tax and costs all update from one return record.

Related service: ERP Solutions · More on this topic: ERP Solutions articles

Common questions

Should RTO orders get a credit note?

It depends on whether an invoice was issued before dispatch and on timing. If an invoice was raised, it usually needs a credit note or cancellation within the allowed window. Your CA should confirm the treatment, and the ERP should then apply it consistently.

How do I reduce RTO with ERP data?

Report RTO rate by pin code, payment method, channel and SKU. Use the results to restrict COD in high-RTO areas, confirm COD orders before dispatch, improve product information and adjust courier allocation. The ERP provides the data; the decisions are operational.

Can returned units go back into the same batch?

Yes, if the unit is sealed, undamaged and within shelf life. Record it back into its original batch so traceability is preserved. Opened or near-expiry units should go to a separate location rather than saleable stock.

Your next chapter

Let’s build what comes next.

A new website. A better system. A simpler way to work. Tell us where you want to begin.

Discuss your project