How to Reconcile Cash on Delivery and RTO in eCommerce

SECTION 01The payout lines a rate card never shows

In brief: Commission and fees can be checked against a published rate. COD remittance, returns to origin and marketplace charges taken as tax cannot. Each involves a third party (a courier, a returns process or a tax authority), each runs on its own timing, and each can land in a different settlement from the sale it belongs to. That is why they cause most of the mismatches a fee check never finds.

A fee error is visible: the rate card says one number and the settlement says another. The three streams below fail quietly. A courier holds cash a little longer than agreed. A returned order is charged freight twice and the fee reversal never arrives. A tax amount is withheld correctly but never claimed, or collected by the marketplace and then counted again in your own tax return. None of these shows up in a monthly total. All of them show up at order level.

SECTION 02Reconciling cash on delivery (COD) remittance

In brief: Match every delivered COD order to the cash remitted for it: the order value collected, the remittance fee deducted, and the date and reference of the remittance. Anything collected but not remitted, remitted short, or remitted against the wrong order goes to an exception queue before the dispute window closes.

Wherever cash on delivery is common, it creates a second money trail next to the settlement. COD reaches you by one of two routes, and each needs its own check:

• Marketplace-fulfilled COD. The marketplace's own logistics collects the cash and folds it into the settlement. The check is that every delivered COD order actually appears in a settlement, at the right value.
• Self-shipped COD, from your own website or from marketplace orders you ship yourself. A courier or shipping aggregator collects the cash and remits it on its own cycle with a remittance report, net of its fee. The check is order by order: collected, remitted, fee.

The routine that works:

1. Pull delivered COD orders from your order system with the delivery date and tracking number.
2. Pull the remittance reports from each courier or aggregator and the settlement reports from each marketplace.
3. Match by tracking number or order ID, never by amount. At common price points, dozens of orders share the same value and amount matching pairs the wrong ones.
4. Check each remittance fee against the contracted rate.
5. Age everything unmatched: orders delivered but not remitted beyond the agreed cycle are cash sitting in someone else's account.
6. Raise disputes with proof of delivery attached, before the courier's or marketplace's window closes.

The usual finds on a first proper COD reconciliation: bulk remittances with no order-level breakup, orders marked delivered that never generate a remittance, and fees charged above the contracted rate.

SECTION 03RTO in eCommerce: following every return to origin

In brief: Treat each return to origin as its own small ledger: the forward shipping charge, the return shipping charge, any commission or fee reversal, and the stock coming back to your warehouse. These arrive in different settlements, often weeks apart, so match them by order ID across cycles and check that every charge is allowed and every reversal actually appears.

RTO in eCommerce means return to origin, also called return to sender: an order that was never delivered, because it was refused at the door, unreachable, or sent to an address that did not work. It is one of the most expensive lines in eCommerce. EasyEcom's State of D2C Fulfilment 2026 report puts the average RTO rate on COD fashion orders at 30%, and RTO accounts for the largest share (42%) of the margin D2C brands lose to RTO and reconciliation gaps. Much of that loss is operational. Some of it is simply charges nobody checked.

Start by separating RTO from customer returns, because the money moves differently:

For every RTO, check four things:

• Freight at the right slab. Forward and return freight charged on the correct weight band and zone for that SKU.
• Reversals that actually arrive. Where the marketplace policy reverses commission or fixed fees on an undelivered order, the reversal must appear in a later settlement. Missing reversals are the classic RTO leak because they are an absence, not a charge.
• No refund deduction on COD RTOs. No cash was collected, so no refund should be clawed back.
• Stock received. The unit logged back into the warehouse against a goods received note. An RTO charged but never received is a lost-in-transit claim.

The operational side of returns, from inspection to restocking, is covered in our returns management guide.

SECTION 04Marketplace charges taken as tax

In brief: Many tax systems make the marketplace, not the seller, responsible for collecting or withholding tax on the sales it facilitates. The reconciliation job is the same everywhere: recompute the tax on each settlement against the right base and rate, match the total to what the marketplace reports to the tax authority, and treat it correctly in your own books, either as a credit you claim or as tax that is not yours to declare.

The rules differ by market. The mistakes do not: tax booked as revenue, tax counted twice, and withheld tax that is never claimed. Here is how the main regimes work from the seller's side.

Sales tax under marketplace facilitator rules

In the United States, marketplace facilitator laws make the marketplace responsible for collecting and remitting sales tax on the sales it facilitates. The tax usually appears in the settlement as collected and then withheld again, so the net effect on your payout is zero. Two errors are common. The tax is booked as revenue because it passed through the settlement, or the same sales are reported again in your own sales tax returns. Some states still ask sellers to report facilitated sales even though no tax is due on them, so check each state's filing rules.

VAT under deemed supplier rules

In the United Kingdom since 1 January 2021, and in the European Union since 1 July 2021, the marketplace is treated as the supplier for VAT purposes on specified sales. These include goods imported in low-value consignments (up to £135 in the UK and €150 in the EU) and goods already in the market sold to consumers by sellers established outside it. For those sales the VAT is the marketplace's to account for. The reconciliation job is to identify which of your sales fall under the rule, keep their VAT out of your own return, and make sure the rest stays in it.

TDS and TCS on marketplace sales

In India, the marketplace withholds TDS at 0.1% of the gross amount of sales (Section 194-O of the Income-tax Act, 1961, carried into Section 393(1) of the Income-tax Act, 2025 from 1 April 2026). It also collects TCS at 0.5% of the net value of taxable supplies under Section 52 of the CGST Act, and reports that monthly in GSTR-8. Both are credits, not costs. Recompute TDS on gross sales, not the net payout, and check it against your tax credit statement. Reconcile TCS per GST registration against your sales register net of returns, then accept it on the GST portal so it reaches your electronic cash ledger. Accepting also confirms the supply values behind it, so reconcile first and accept second.

SECTION 05What about different settlement calendars?

In brief: Reconcile by settlement ID and order ID, not by calendar month. Every marketplace pays on its own cycle and in its own report format, so one order's sale, fees, RTO charges, tax and reversals can span several settlements. The month-end close then books what is reconciled and carries the rest as aged receivables.

Two matches keep the calendars under control. First, every bank deposit to its settlement ID, using the bank's transfer reference, so you know which settlement each deposit belongs to. Second, every settlement line to its order, so an order's full financial life can be read in one place however many settlements it touched. High-volume, low-value channels such as quick commerce raise the stakes, because adjustments are netted into payouts and line-level matching is the only way leakage surfaces. Our quick commerce guide covers that channel in depth, and the order-to-cash process shows where reconciliation sits in the wider cycle.

SECTION 06Your month-end checklist

In brief: Import every settlement, match deposits to settlements and settlement lines to orders, then work the off-rate-card lines: COD remittance, RTO trails and marketplace charges. Raise claims before windows close and post reconciled figures to your accounting system.

1. Import every settlement report for the month, for each marketplace and channel.
2. Match bank deposits to settlement IDs using the transfer reference.
3. Match settlement lines to orders, by order ID.
4. Tie delivered COD orders to remittances and age anything unremitted.
5. Follow each RTO across cycles: freight at the right slab, reversals received, stock back in the warehouse.
6. Verify commissions and fees against each marketplace's current rate card.
7. Recompute marketplace charges taken as tax against the right base and rate for each market, and flag differences.
8. Match tax totals to what each marketplace reports to the tax authority, then claim credits or exclude facilitated sales from your own returns as the rule requires.
9. Raise claims for every exception, with evidence, before the dispute window closes.
10. Post reconciled revenue, fees and tax to your accounting system or ERP, so the books close on verified figures.

SECTION 07Where EasyEcom comes in

In brief: EasyReco, EasyEcom's reconciliation engine, reconciles marketplace settlements against the orders, COD shipments, RTOs and returns EasyEcom already manages, tracks the tax marketplaces withhold so it is claimed as credit, and syncs reconciled figures to accounting systems such as Tally and SAP. Swiss Military reconciles 85% faster at up to 99.99% accuracy.

A payout line is only correct relative to the order that shipped, the COD cash that was collected, and the RTO that did or did not come back. When reconciliation runs on the same platform that holds those records, there is no import gap for a discrepancy to hide in. That is how EasyEcom is built: every settlement line meets its order, and every deduction meets its evidence.

Swiss Military, selling across the major marketplaces, was verifying payouts by hand in spreadsheets. On EasyEcom, reconciliation runs 85% faster at up to 99.99% accuracy within months, with invoices and credit notes syncing straight to Tally, through 10x order growth over four years. Borosil runs orders, invoices and payments into SAP through EasyEcom without touching its SAP setup.

Put a month of your own settlements through it: explore EasyEcom's payment reconciliation software, check our pricing, or book a demo and we will reconcile a sample settlement cycle with your team.