Cash on delivery is still essential in many markets, and it is the fastest way to lose money quietly. The customer pays the rider; the rider owes the platform; the platform owes the restaurant and maybe the rider. Every handover is a chance for a shortage, a fake refund or a delayed deposit.
Software can record the flow, but reconciliation is an operating discipline. The platform needs a daily close, a named owner and a variance process that everyone understands.
The cash chain
- Customer places a COD order; the amount is recorded.
- Rider collects cash at the door.
- Rider marks the order delivered and the amount collected.
- Rider hands cash to the cashier or deposits it.
- Finance reconciles collected, deposited and expected.
- Restaurant and rider payouts are settled from the reconciled amount.
Every step needs a timestamp and an actor. If the rider can mark “delivered” without recording the cash, the chain is broken.
| Control | Purpose | Frequency |
|---|---|---|
| Opening float | Change for customers | Each shift |
| Per-order cash confirmation | Match order to collected amount | Each delivery |
| Shift handover count | Transfer responsibility | Each shift |
| Daily deposit | Reduce cash held by riders | Daily |
| Variance report | Find shortages and duplicates | Daily |
| Random audit | Deter fraud | Weekly |
| Restaurant settlement | Pay the correct vendor share | Weekly / biweekly |
Set a float policy, not a guess
Each rider starts a shift with a fixed change float. The float is not revenue; it is a loan. At the end of the shift, the rider returns the float plus collected cash minus approved expenses. If the float is $20 and the rider collected $180, the handover is $200, not $180.
Keep the float small enough that a loss is painful but not catastrophic. Review it as order values change.
Variance thresholds
Not every shortage is fraud. A customer may have short-changed the rider, or a refund may have been approved verbally. Define a threshold: small variances are logged and absorbed; repeated or large variances trigger an investigation. The threshold should be in writing and applied consistently.
Look for patterns: the same rider, the same restaurant, the same neighbourhood, the same time of day. A single shortage is noise; a cluster is a control problem.
Refunds and cancelled orders
COD refunds are operationally awkward because the platform may not have received the cash. Define who can approve a refund, what proof is required and how the rider is reimbursed. If a rider pays a customer back from their own cash, the reconciliation must record it as an approved adjustment, not a shortage.
Reports finance actually needs
- Expected cash by order, rider and shift.
- Collected cash and variance.
- Approved refunds and adjustments.
- Outstanding rider balances.
- Restaurant payable after commission and refunds.
- Daily bank deposit match.
Reduce cash over time
Offer a small incentive for digital payment, such as loyalty points or a waived fee. Add wallets and local payment methods where customers trust them. Keep COD for customers who need it, but make digital the easier default. The goal is not to eliminate cash overnight; it is to shrink the float and the fraud surface.
See the management software, the payment gateway guide, or vendor settlements.
COD control mistakes
- Letting riders mark delivered without recording the cash collected.
- Depositing weekly instead of daily.
- Treating every shortage as fraud instead of separating error from theft.
Run one shift with a paper backup of the software flow. If the two do not match, fix the process before adding riders.