Cash on Delivery (COD): The Accounting Implications

For most Indian e-commerce sellers, Cash on Delivery still represents 40–60% of orders. That single fact reshapes the accounting more than any other channel quirk. COD is not a sale to the customer with cash in hand — it is a sale to a customer that someone else collects from, after carrying the risk that they may not. Here is what your books need to do.

The actual flow

For a COD order, the cash path is:

• You dispatch the order to the courier
• Courier attempts delivery
• Customer pays the courier in cash (or refuses; goods come back)
• Courier remits the collected cash to you in a batch, after deducting fees
• For undelivered orders, courier returns the goods to you (Return-to-Origin, RTO) — sometimes with a charge

The corresponding accounting timeline:

• Dispatch — sale recognised, debtor created (the courier, not the customer)
• Delivery — sale completes; no immediate cash entry
• Remittance — courier settles cash less their charges; debtor reduced
• RTO — goods come back; sale reversed, inventory restored

The single most important entry is the first one: the debtor is the courier, not the customer. The customer is anonymous and has no GSTIN; you are owed the money by the courier whose books you can reconcile.

What goes in your books at dispatch

For a COD order worth ₹2,360 (₹2,000 + 18% GST):

• Debit Courier Receivable ₹2,360 (or the specific courier's ledger)
• Credit Sales ₹2,000
• Credit GST Output ₹360

This is the same accounting as a credit sale — the only difference is who the debtor is.

What goes in your books at remittance

The courier remits, say, ₹2,290 — having charged ₹70 as COD handling fee. Your entry:

• Debit Bank ₹2,290
• Debit Courier Charges (Expense) ₹70
• Credit Courier Receivable ₹2,360

The ₹70 is a real cost — about 3% of order value in this case. Across thousands of orders, that becomes a meaningful expense line that needs visibility.

The RTO problem

If the customer is not at home, refuses delivery, or the address is wrong, the parcel comes back. Most couriers charge for both the failed delivery attempt and the return leg. So a ₹2,000 RTO order might cost you:

• The original outbound shipping
• The COD attempt fee (sometimes)
• The return-to-origin freight (often equal to the outbound)
• Restocking labour at your end
• Often slight damage in transit

A 20% RTO rate — common for low-AOV categories — silently destroys margins. The accounting needs to surface this clearly.

For each RTO:

• Reverse the sale (no revenue, no GST liability) by booking a sales return
• Restore inventory (with a condition check — damaged items go to a write-off)
• Recognise the RTO cost as a separate expense (outbound + return + RTO fee)
• Track the RTO rate per channel, product, geography

The reconciliation discipline

The courier sends a remittance statement — typically daily or weekly — listing the orders settled, the cash collected, the charges deducted, and the net remitted. Reconcile every statement:

• Each order on the statement should match a COD order in your books
• The collected amount should match the order value
• The charge should match the agreed rate
• RTO orders should match your RTO log
• Unmatched lines need investigation

Discrepancies are common: orders missing, charges higher than agreed, RTO orders not credited back. Unreconciled COD ledgers quietly accumulate phantom receivables.

The cash-flow effect of COD

COD shifts your cash cycle. A pre-paid order: customer pays today, you have the cash today. A COD order: customer "pays" today, you have the cash 7–14 days later (after the courier settles).

For a fast-growing e-commerce business, the working-capital impact is material. Days of receivables outstanding for COD revenue can be 10–20 days; for prepaid through marketplaces, 7–30 days; for prepaid through your own gateway, 1–3 days.

Mix shift toward COD = more working capital required. Mix shift toward prepaid = less. Track and forecast this — it can swing your cash runway.

RTO rate as a leading indicator

The single most useful COD metric is RTO rate — RTOs as % of COD orders.

• Below 10% — healthy
• 10–20% — manageable, with active address verification
• 20–30% — eating into margin; investigate by channel, product, geography, AOV band
• Above 30% — unsustainable; either pre-paid only, or stop the channel/category

A rising RTO trend on a category that was previously fine is a flag — often a quality issue, a delivery-area problem, or a fake-order pattern.

Address verification and OTP delivery

Two operational practices that materially affect the books:

• OTP-based delivery confirmation — reduces "marked delivered but not actually delivered" disputes
• Address verification on order — reduces RTO rate, especially for COD

These are operational changes that protect the books from reconciliation pain.

How Booksmor helps

Booksmor handles COD-specific accounting: each COD order books a receivable from the courier (not the customer); courier remittance statements reconcile per order; COD charges and RTO costs are tracked as separate expense lines; RTO rate trends per channel/product/geo are surfaced for action. Start a 30-day free trial and put your COD flow on real books.