Cash is the only metric that keeps a high-velocity FMCG brand alive in the Indian market. Everything else—brand equity, "community engagement," and "customer delight"—is just noise if your working capital is trapped in a courier partner's reconciliation bucket for seven days.
The T+7 standard is a relic of manual processing. It’s a luxury for brands with massive balance sheets. For the high-volume, low-margin players (think personal care or essential spices), waiting a week to see your COD cash hit your account while simultaneously paying out heavy CAC on Meta and Google ads is a recipe for a liquidity crunch.
Moving to T+3 isn't just a "policy change." It’s an engineering requirement.
The Friction of the Status Quo
Currently, most 3PLs and courier partners operate on T+7 or even T+10 because their internal reconciliation systems are broken. They aggregate thousands of waybills, manually (or via semi-automated batch processes) reconcile "Delivered" statuses against cash collected at the doorstep, and then dump a lump sum into your account once they’ve cleared their own administrative hurdles.
During this 7-day window, you aren't just waiting for money; you are actively losing the ability to scale. If you can hit T+3, you shorten the cycle between "Order Placed" and "Cash in Bank." This allows for aggressive reinvestment into active customer acquisition during high-velocity windows like festive sales or influencer-led bursts.
The Anatomy of a Failed Reconciliation
I once worked with an FMCG brand moving 50,000 units monthly across Tier 2 and Tier 3 cities. They were hemorrhaging roughly 4% of their COD revenue—not because the customers didn't pay, but because the reconciliation between their ERP (Unicommerce) and the courier’s actual payout logs was a mess.
During an October sale, they saw a 150% spike in volume. Because they were relying on manual daily reports to match "Delivered" statuses with bank credits, they couldn't identify missing payments until three weeks later. They literally didn't know which orders had been paid for and which were still "pending" in the courier’s local hub's cash bag. By then, the marketing team had already burned their budget on a campaign that was under-funded by nearly ₹12 Lakhs because of this lag.
The T+3 Implementation Architecture
To hit T+3 without hiring 50 more people to chase settlement reports, you have to strip out the human element from the reconciliation loop. You need an automated logic gate triggered by three specific data points:
- The Delivery Ping : As soon as the courier’s rider marks a "Delivered" status via their mobile app (the source of truth), an API call must hit your middleware.
- The Payment Validation : The system must instantly flag that specific waybill as "Cash_Collected."
- The Settlement Trigger : Instead of waiting for the courier’s batch upload, your system should poll their API every 60 minutes to verify receipt of funds against a unique Transaction ID (the Waybill Number).
If the merchant's ERP sees "Delivered + Payment Confirmed" but no corresponding bank credit within 24 hours, it flags an exception. Don’t wait for T+7 to find out there’s a discrepancy; flag it the moment the courier fails to sync the data.
The Rules of Engagement for CFOs
Stop treating the "Remittance Gap" as a logistics problem. It is a finance and systems integration problem.
If your courier partner claims they can't do T+3 because "it’s too complex," they are telling you their tech stack is antiquated. You need to demand a direct API integration where the settlement logic is driven by status changes in real-time rather than end-of-day batch files.
Cut the fat. Automate the reconciliation of waybill IDs against bank reference numbers. If you can't sync your order management system with their payout ledger in under 24 hours, you aren't running a modern supply chain—you’re just running a slow one. Tighten the loop, grab your cash faster, and use that liquidity to win the next customer before your competitor even clears their first batch of receipts.