Skip to main content
← All articles
Payments · November 2026

COD Remittance Cycles and the Cash Flow Gap

10 minutes read
THE COD CASH CYCLE
CASH OUT — DAY 0
Ads · stock · freight
you fund the gap
Order placed
confirm, pick, pack
›
Dispatched
in transit
›
Delivered
cash collected
›
Courier cycle
charges netted off
›
Cash in bank
then reconciled
days you fund yourself
WHAT SHORTENS IT
Faster dispatch
Lower RTO
More prepaid
Paid early
Summary

Your courier publishes one number. Your actual COD cash cycle is five intervals stacked end to end, and only one of them belongs to the courier. Here is how to measure the whole thing, what each day of it costs, and how to decide whether paying for early remittance is sensible or expensive.

A Cash on Delivery order is revenue on the day it is placed and cash on a day you do not control. Everything in between is working capital you are quietly lending — to your customer, to your courier, and in a tight month to your supplier, who is waiting on you. Most brands running COD know the gap exists. Far fewer know how many days it actually is, which is the number every purchasing and ad-spend decision depends on.

What the clock is actually counting

The gap is usually discussed as “the remittance cycle”, as though it were a single figure your courier publishes. It is at least five intervals stacked end to end, and only the fourth is the courier’s remittance policy.

One: order to dispatch. Entirely yours. For COD this interval includes confirmation — the time spent getting an OTP answered, a WhatsApp message replied to, or a call picked up before you commit stock to a parcel. A day spent chasing a confirmation is a day of cash gap, and it is the day most brands do not count because it feels like operations rather than finance.

Two: dispatch to delivery. Transit. Lane-dependent, courier-dependent, and longer for the tier-3 pincodes that often carry your best COD conversion.

Three: delivery to collected funds. The delivery agent takes cash or a UPI payment and it moves up through the courier’s own settlement chain before it is even eligible for remittance to you. Nothing you do affects this, and almost nobody publishes it separately.

Four: the courier’s remittance cycle. The published number. This is the only interval in the chain that appears in a help article.

Five: bank credit to reconciled cash. The money lands as a lump sum with charges netted off. Until you have matched it to orders, you know your balance but not your margin — and you cannot yet tell whether anything is missing.

The practical consequence: merchants plan against a figure that covers stage four and then discover their real cycle is roughly double it. The fix is not to argue with the courier. It is to measure all five.

What couriers publish, and how to read it

Published timelines are a starting point, not a plan. Three examples, with the date each page was last updated, because these figures move and the pages often do not.

Logistics company Delhivery states in its help documentation that “we will transfer the COD amount to the seller’s or client’s bank account within 48 hours”. The same page adds a condition worth noting: you must “maintain a positive wallet balance”, and if the wallet balance is negative “the remittance shall only be processed in the next cycle when the wallet has a positive balance”. That page shows a last update of November 2023.

Shipping aggregator Shiprocket, in a support article on when COD payments arrive, states “you will receive the COD amount in your bank account after 8-9 days of order delivery”, and that merchants can opt for Early COD to “receive COD payments in your bank account as soon as 2 days after delivery”. That support article carries a last-modified stamp of December 2020, so treat the specific figures as indicative and check your own contract. Shiprocket’s current Early COD product page advertises “Guaranteed Remittance in 2 days” with an asterisk, says there is a fee without publishing the amount, and separately markets an Instant COD product it describes as remitting “70% of your COD amount within 24 hours of order shipping”.

Read any such figure with three questions:

From what event does the clock start? “Within 48 hours” and “after delivery” are not the same clock. Delivery, agent deposit, cycle cut-off and bank initiation are four different starting points and the difference between them can be several days. Get the triggering event in writing.

Which days are excluded? Weekends and bank holidays are usually excluded from a transfer cycle and almost never mentioned in the headline number. In a month with a long festive break this is the difference between a comfortable position and a scramble.

Does it describe a clean order? Published timelines describe a shipment that delivered, collected the right amount, and generated no dispute. Your remittance file is not made only of those.

Measure your own cycle, not your courier’s

This takes an hour with an export and it is the highest-value hour in COD finance.

Pull one full month of COD remittance credits. For each remitted order, compute the days between the order placed date and the bank credit date. Not the dispatch date, not the delivery date — order placed, because that is when you committed the cash.

Then take the median and the 90th percentile, and ignore the mean. The mean is distorted by a handful of stuck shipments; the median tells you how the business normally behaves, and the 90th percentile tells you what to plan against. You purchase stock and commit ad spend against the slow tail, not the typical case.

Split the result two ways. By courier, because a courier with slightly higher freight and a materially shorter cycle may be the cheaper option once you price the capital. By lane or zone, because the cycle on a metro lane and a remote-pincode lane are different products and may deserve different COD rules.

Now turn it into a rupee figure. Multiply your median cycle in days by your average daily COD revenue. That is the amount permanently parked in the pipe — money that is yours, that you cannot spend, and that grows in direct proportion to your growth. It is usually a larger number than merchants expect, and seeing it stated is what makes the rest of this worth doing.

The corollary is the useful part: every day you remove from the cycle releases one day of COD revenue as cash, once. Not a recurring saving — a one-time release, which is exactly what you want if you are funding the next inventory cycle rather than servicing a monthly cost.

RTO does not just cost shipping — it inverts the cash flow

A delivered COD order is cash in, late. An RTO is cash out, now, with nothing in, ever. Forward freight, return freight, the COD handling charge where your courier levies one, and the packaging — all of it debited, typically from the same account the remittance credits land in.

That netting has two consequences people miss.

First, your net remittance is a smaller share of your COD order value than your margin sheet implies, and the gap widens as RTO rises. Growth financed by COD at a high refusal rate consumes cash faster than it produces it, which is the mechanism behind brands that look profitable on a P&L and cannot pay a supplier.

Second, charges and credits share a queue. Delhivery’s own documentation describes remittance being held to the next cycle while the wallet balance is negative. Read that operationally: a bad RTO week can delay the cash from a good week. The cost of RTO is not only the freight — it is the freight plus a delay applied to unrelated, perfectly good orders.

If you are working on one thing, work on the RTO rate itself. It is the only lever that improves margin and cycle time at the same time.

Reconciliation is where the money actually leaks

Remittance arrives as a net figure. Net figures hide three distinct failures, and all three are recoverable only if you catch them inside the courier’s dispute window.

Short remittance. The credit lands but does not match the order total, and the deduction is not clearly itemised. Sometimes a legitimate charge, sometimes a weight dispute you never saw raised, sometimes an error.

Missing remittance. A shipment shows delivered and no credit ever appears against it. This is the expensive one, because nothing prompts you — an absent line item is invisible unless you are looking for it specifically.

Duplicate or phantom charges. Return freight billed on a shipment that was not returned, or billed twice on one that was. Rare per shipment, meaningful at volume.

The practice that catches all three is unglamorous: reconcile at order level, weekly. Not bank statement against invoice, monthly — order against credit, weekly. Maintain a standing list of delivered but unremitted shipments with an age column. Anything older than your measured cycle plus a short buffer goes to the courier as a query, with the shipment ID and, where the courier exposes one, the bank transaction reference; Delhivery’s remittance screen provides a Bank Transaction ID for exactly this purpose.

Two process notes. The person reconciling should not be the person dispatching — not as an accusation, simply because the same pair of eyes misses the same things twice. And the query window matters more than the query: a dispute raised inside the courier’s stated window is usually settled, and the same dispute raised two months later usually is not.

The four levers, in order of return

1. Dispatch speed. Yours alone, costs nothing, and it is almost always the largest single interval that is actually under your control. Two changes do most of the work: a hard same-day dispatch cut-off, and confirmation that runs on a timer rather than on someone remembering to call. Automated confirmation with a fallback channel turns “we confirmed it eventually” into “confirmed or cancelled within hours”, which compresses stage one and reduces the number of parcels that were never going to land.

2. RTO rate. Compounding, for the reasons above. Each avoided RTO converts a guaranteed outflow into a delayed inflow and removes a drag on the rest of your remittance queue.

3. Payment mix. A prepaid order settles on gateway terms and carries no RTO freight exposure. Shifting even a modest share of orders prepaid shortens your blended cycle twice over — the prepaid orders settle faster, and the COD queue they leave behind is smaller. Prepaid conversion is usually framed as a margin exercise; it is at least as much a cash-cycle one.

4. Paying for early remittance. A real option, and a priced one. The way to evaluate it is to convert the fee into an annualised cost of capital, because that is what it is.

The arithmetic: fee percentage × (365 ÷ days saved) = effective annual rate. Suppose a provider quoted 1% to advance your money seven days earlier. That is 1% × (365 ÷ 7), or roughly 52% a year. The same 1% to advance it thirty days earlier is about 12% a year. Nothing about the fee tells you which it is — only the fee together with the days saved does, and the days saved must be measured against your cycle, not the standard one on the brochure. Run the sum on the fee you are actually quoted; the numbers above are illustration, not a quote from anyone.

A high implied rate is not automatically a bad deal. If that cash funds inventory that turns within the period at a gross margin comfortably above the implied rate, or if it replaces more expensive borrowing, paying for speed is correct. Judge it against your genuine next-best source of working capital, not against zero. What you should not do is take early remittance as a default because the cycle feels long — that is paying a finance charge to avoid an operations fix, and the operations fix is free.

The sheet that prevents the squeeze

One rolling view, four lines, 28 days forward, updated weekly:

Expected remittance by day, built from your delivered-but-unremitted list aged by your measured cycle — not the published one. Expected courier debits, including return freight on shipments currently in RTO transit, which is the line most sheets omit and the one that bites. Committed outflows: supplier payments, ad spend, salaries, rent. Resulting daily balance.

The point is not forecasting accuracy. It is seeing the trough before you reach it, while you still have the cheap options available — slowing ad spend for three days, asking a supplier for a week, dispatching a backlog earlier. Those options disappear in the last 48 hours, which is when most brands first look.

Festive season is where this breaks, and predictably so. Dispatch volume spikes, ad spend is front-loaded into the peak, remittance arrives on the ordinary cycle, and bank holidays extend it. The trough is not during the peak — it lands a fortnight after, when the spending has happened, the RTO wave from impulse orders is coming back, and the corresponding remittance has not yet arrived. Build that fortnight into the sheet before the season rather than during it.

COD King works on levers one and three: it confirms COD orders by OTP and WhatsApp so the confirmation interval is hours rather than days, and it handles COD fees, partial advances and prepaid nudges inside Shopify’s native checkout. It does not touch your remittance cycle — only your courier can shorten that, and only your own measurement will tell you what it currently is.

The brands that run COD comfortably at scale are rarely the ones with the best courier terms. They are the ones who know their cycle to the day, reconcile every week, and treat the gap as a number to manage rather than a condition to endure.