To match return and RTO deductions on a seller payout, take each deduction line, find the original order it refers to, and note why it was charged: a customer return, a parcel that came back undelivered, or something else. Then mark each one as your cost, a possible dispute or unclear. Keep the log so the same questions are not asked again next month.
What are you looking at on the payout statement?
A payout statement lists money credited for orders and money taken off. Deduction lines often carry an order number and a short label. Names differ between marketplaces, so read the labels on your own statement and the seller terms. The usual families are a reversal of the sale amount for a returned order, shipping charged for sending the parcel back, and a handling or failed-delivery fee for undelivered parcels returned to origin, commonly called RTO.
How do you match a line to an order?
- Copy the order number from the deduction line.
- Open your order record and see what happened: delivered, returned by customer, or returned undelivered.
- Check that the sale amount, product and date match.
- Note the courier tracking history, since it shows delivery attempts and return events.
- Write the result in your log.
What does a matched list look like?
Here is a made-up weekly payout with ₹18,400 credited and five deduction lines. The labels and amounts are invented.
| Order | Line on statement | Amount | What happened | Action |
|---|---|---|---|---|
| A1042 | Sale reversed | ₹799 | Customer return, item came back fine | Accept; lost sale |
| A1042 | Return shipping | ₹95 | Same return | Your cost, check seller terms |
| A1051 | Shipping on undelivered parcel | ₹85 | Customer unreachable, parcel returned | Your cost, check tracking |
| A1051 | Return handling fee | ₹60 | Same parcel | Your cost, check seller terms |
| A1060 | Sale reversed | ₹649 | Customer returned an empty box | Dispute with photos |
The deductions total 799 + 95 + 85 + 60 + 649 = ₹1,688. Of that, ₹649 is worth disputing and the rest is the normal price of returns in this example.
Which deductions can be disputed?
Whether a charge can be reversed depends on the marketplace's rules, so read the seller terms before you raise it. Common grounds to check:
- The returned item was not what you sent: wrong product, empty box, used or damaged.
- The tracking shows no genuine delivery attempt before the parcel was sent back.
- A deduction appears twice for the same order.
- The order was cancelled before dispatch but was still charged.
A return that is simply a customer changing their mind is usually yours to absorb. Do not count on a dispute succeeding; treat it as a request, not a certainty.
How do you log them?
Keep one row per deduction with these columns: payout date, order number, deduction type, amount, reason, action, dispute date and outcome. A simple monthly total by deduction type shows whether returns are a small leak or a big one. If the same product keeps coming back, the fault may be in the listing or packing, not in the courier.
Can a tracker help?
Your marketplace payout reaches your bank as one credit, so the individual deductions only show on the statement the marketplace gives you. If you import your bank statement into SpendixAI, you can at least see the net credit against its date and category, but the line-by-line matching still has to happen on the payout statement.
Add one column for the customer's reason where the platform shows it. After a month, return reasons such as size, colour or damage tell you which listing needs a better photo or description, and which items are packed badly.
A monthly routine
- Download the payout statements once a week.
- Match every deduction line to an order.
- Raise disputes inside the allowed window.
- Total returns and RTO costs for the month and compare with last month.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


