COD Remittance and Cash Flow Calculator

COD settlement timing is not the same as revenue recognition or profit. The calculator models successful-order payout, RTO costs and a simple locked-capital estimate; actual remittance depends on marketplace, courier, reconciliation and holidays.

A cash-timing scenario separates order value from cash available: successful COD orders × (order value − COD fee) is modeled against the stated pay-cycle days, while RTO orders consume the entered forward and reverse logistics assumptions. A 7-day cycle is a planning window, not a promised settlement date.

Use a rolling weekly export to replace the preset RTO and fee assumptions. Holidays, reconciliation holds, NDR attempts, partial refunds, deductions and reserve policies can change both the date and the amount remitted.

COD is a cash-cycle problem as well as a fee problem. Separate placed orders, picked-up orders, delivered orders, returned-to-origin orders and remitted orders. A courier may calculate a remittance only after delivery confirmation and may deduct freight, COD fees, claims, refunds or a reserve. For 250 delivered orders at ₹900 each, gross collected value is ₹225,000; a ₹20 COD fee per delivered order leaves ₹220,000 before other deductions. If the stated pay cycle is seven working days, the expected remittance date depends on the delivery scan, weekend and holiday calendar, not the date the order was created. Use cohorts by delivery date to avoid mixing cash from different weeks.

Worked scenario: 500 placed orders become 430 delivered and 70 RTO. If forward freight is ₹65 on every pickup, reverse freight is ₹70 on each RTO and the courier retains ₹25 COD fee on delivered orders, logistics and COD deductions total ₹32,850 before product loss. Gross delivered collection is 430 × ₹800 = ₹344,000. If five returned units are damaged at ₹180 each, add ₹900 of inventory exposure. The useful output is not simply “cash received”; it is remittance, time to cash, failed-order cost and inventory outcome. Run the same calculation by courier and payment mode so a low fee does not conceal a slower cycle or higher RTO.

Assumptions and limits matter. Some contracts charge COD fees on order value, some on collected value, and some use a percentage with a minimum. Remittances may be net of GST, TDS/TCS, dispute reserves or previous-period adjustments. Partial delivery, refused COD, NDR attempts, address corrections and customer refunds can change the final ledger. If a courier pays weekly but holds high-risk pin codes, use a range rather than a single date. The calculator does not connect to a bank, courier manifest or settlement API and cannot promise a payout. Never use a modeled date to commit payroll or supplier payments without a cash buffer.

Update notes and FAQs: export courier remittance data weekly and compare modeled fees with actual deductions. FAQ: Is COD remittance the same as sales revenue? No; revenue recognition and cash settlement can occur at different times. FAQ: How should I handle RTO? Keep the failed order separate from delivered COD and include forward, reverse, packaging and inventory costs. FAQ: Why can two couriers remit different amounts? Their fee bases, tax deductions, reserves and adjustment policies differ. FAQ: Does the calculator know holidays? No; treat the pay-cycle field as a planning window and apply the courier contract calendar before making a promise.