Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
D2C apparel and beauty brands run two parallel settlement flows — 3PL cash remittance for COD orders (T+5 to T+10 from delivery, net of RTO and COD handling charges) and gateway payouts for prepaid (T+1 to T+2, net of MDR) — and collapsing them into a single revenue line hides RTO leakage, commission errors, unremitted cash, and working-capital lag that commonly runs 20–30% on COD-heavy categories.
Maintain two independent receivable sub-ledgers: gateway receivable matched against Razorpay, PayU, or Cashfree payouts, and 3PL receivable matched against Delhivery, Shadowfax, or Shiprocket remittance. Match at AWB level for COD and order-ID level for prepaid. Reverse RTO provisional revenue, book reverse-logistics fees, and track inventory return. GST on MDR (18%) and GST on 3PL fees (18%) are booked as separate ITC claims against different expense heads.
Order management connector with AWB-to-order mapping, 3PL adapters for Delhivery, Shadowfax, Shiprocket, Ecom Express; gateway adapters for Razorpay, PayU, Cashfree; RTO classification rules; reverse-logistics fee schedule per 3PL; inventory return trigger to stock ledger.
Two reconciled sub-ledgers with AWB-level COD cash traced from delivery to bank credit, order-ID-level prepaid cash traced from transaction to payout, RTO leakage isolated, 3PL commission errors surfaced, and working capital lag quantified for board reporting.
A D2C apparel brand operates on Shopify with Razorpay for prepaid and Delhivery for COD. In a normal week, 55 percent of orders are COD and 45 percent are prepaid. Prepaid cash arrives on Monday as a Razorpay payout. COD cash arrives on Thursday as a Delhivery remittance, net of RTO charges from orders placed three weeks earlier. These two flows share nothing — different timing, different deduction structure, different source document. This article is for finance and operations teams at Indian D2C brands managing both channels.
What D2C COD vs Prepaid Settlement Reconciliation Involves
D2C settlement reconciliation matches three data sets on two parallel tracks. For prepaid orders, the tracks are gateway payout report, bank statement, and OMS order records. For COD orders, the tracks are 3PL remittance advice, bank statement, and OMS order records with AWB assignment. Each track produces its own variance report, and the two are consolidated only at the revenue reporting layer — not at the matching layer.
The India-specific complication is the scale of COD share. Unlike markets where COD is marginal, Indian D2C brands in apparel, beauty, accessories, and electronics routinely see 40 to 60 percent COD volume. This share brings RTO exposure, 3PL counterparty risk (unremitted cash from lost shipments), and a settlement cycle that stretches working capital by 2 to 3 weeks versus prepaid. Reconciliation must catch RTO leakage, missed remittances, and reverse-logistics fee errors at the AWB level, not at the aggregate.
How D2C COD vs Prepaid Settlement Reconciliation Works
Reconciling the Prepaid Flow
The prepaid flow mirrors a standard gateway reconciliation. Razorpay, PayU, or Cashfree settles gross transactions net of MDR and GST on MDR on a T+1 or T+2 cycle. The reconciliation matches each settlement batch in the bank statement to the gateway’s settlement report, then matches each transaction in the settlement report to a Shopify or custom OMS order. Variances typically fall into MDR rate mismatches (gateway applied wrong category rate), missing refund offsets (refunds processed but not yet settled), and timing breaks (transactions successful in the previous cycle showing up in the current settlement due to late capture).
Reconciling the COD Flow
The COD flow is structurally different. 3PL partners aggregate cash collected over a period and remit net of fees. The remittance advice typically shows each AWB with order value, COD handling fee, and status (delivered, RTO, in-transit, lost). The reconciliation matches each AWB to the original order, verifies the cash collected equals the order value, subtracts the correct COD handling fee per the contract, and flags any AWB marked delivered without a corresponding remittance line. Unremitted cash beyond the agreed cycle is the single largest variance category and the primary operational risk in 3PL relationships.
Handling RTO and Reverse Logistics
An RTO shipment triggers a reverse-logistics charge and, in most 3PL contracts, a forward-logistics charge that is still billable. Both appear as deductions in the 3PL remittance statement against the brand’s payable balance. The reconciliation step is to match each RTO AWB to the original order, ensure revenue recognition is reversed in the OMS and ERP, book the twin logistics charges as an expense with 18% GST claimable on the logistics GST component, and update inventory once the returned shipment is received back at the warehouse. Brands that skip the inventory step carry phantom stock-outs while actual inventory sits at the 3PL return hub.
D2C Settlement Cycle and Deduction Reference
| Flow | Typical Cycle | Primary Deductions | Variance Pattern |
|---|---|---|---|
| Prepaid Razorpay | T+1 UPI, T+2 cards | MDR 1.75 to 2.5% cards, 0 to 0.4% UPI, 18% GST on MDR | MDR rate mismatch, refund timing |
| Prepaid PayU | T+1 to T+2 | MDR 1.75 to 2.5%, 18% GST on MDR | Settlement split across batches |
| COD Delhivery | T+5 to T+10 from delivery | ₹25 to ₹60 COD fee per shipment, ₹40 to ₹80 RTO fee | Unremitted AWBs, RTO charge disputes |
| COD Shadowfax | T+5 to T+7 from delivery | ₹30 to ₹70 COD fee per shipment, RTO charges | Delivery confirmation timing lag |
| COD Shiprocket | T+7 to T+14 remittance window | Variable by courier partner, platform fee | Multi-courier consolidation complexity |
India Compliance Angle: GST and Cash Handling
Cash remittance from 3PL partners to brands operates under escrow-style arrangements regulated under the RBI’s PA-PG guidelines for aggregators handling customer funds. While 3PL partners are not formally payment aggregators, the operational analog applies — cash collected belongs to the brand and must be remitted within the contractual cycle. Delays beyond the cycle are a commercial dispute, not a payment aggregator violation, but brands maintaining cash-remittance sub-ledgers often find aging analysis mirrors the same logic used for nodal account reconciliation.
GST on 3PL services — both forward logistics and reverse logistics — attracts 18% GST, which is ITC-eligible against the 3PL’s tax invoice. Brands reconciling only at the net-remittance level miss this ITC entirely, understating credits by an amount that compounds over months. A brand shipping 10,000 COD orders per month at ₹50 average logistics cost carries roughly ₹90,000 in recoverable ITC on logistics GST alone each month — material at D2C scale.
Finance teams using payment gateway reconciliation pipelines can extend the same pattern-matching logic to 3PL remittance files, matching AWB-level cash collections to OMS orders with the same order-ID key. Reconciliation software India finance teams use that can handle both gateway and 3PL streams in one pipeline avoids the reconciliation silo where prepaid variance gets caught but COD leakage runs for months. The Reserve Bank of India publishes the PA-PG framework that indirectly governs how customer cash held by aggregators and intermediaries is treated.
The following questions address the reconciliation issues D2C brands running dual-channel settlement encounter most often.