How COD Reconciliation Works — And Where It Goes Wrong

Cash on delivery is straightforward for the customer and awkward for everyone else. Every COD parcel creates two trails — the parcel and the money — and they move through different hands at different speeds. Reconciliation is the process of proving those two trails agree.

When it is done badly, the losses are rarely dramatic. They are small, frequent and very hard to investigate after the fact.

The four stages the money passes through

1. Collection

The delivery executive collects cash or takes a digital payment at the door. The critical requirement is that the amount is recorded against the specific shipment, at the moment it happens, by the person who took it. Recorded later from memory, at the end of a run of sixty deliveries, it will not be accurate.

2. Handover

At the end of the run, the executive hands cash to a supervisor or cashier. This is the single most important control point, because it is the first moment the system can compare an expectation against reality: the sum of what the app says was collected, against what is physically counted.

A discrepancy found here is solvable — the person is standing there and the day is fresh. A discrepancy found three weeks later is an argument.

3. Deposit

Cash goes to a bank. The deposit needs to be linked back to the specific handovers it contains, or the audit trail breaks at exactly the point where the amounts get large.

4. Remittance

The money is paid to the client whose goods were sold, usually net of your charges, on an agreed cycle. This is the stage the client sees, and the one they will query.

Where it goes wrong

Collection recorded after the fact

If the app makes recording a collection slow or awkward, staff will do it in a batch afterwards. From that point on your COD data is a reconstruction rather than a record, and small errors are inevitable.

Partial payments and amount changes

The customer does not have the full amount, or the order was modified after booking. If the system only accepts the expected figure, staff will record something inaccurate to get past the screen. The system has to allow a different amount with a reason attached.

Digital payments treated as cash

A customer paying by UPI or card at the door has settled — but not into your cashier's hands. If the system does not distinguish payment modes, the end-of-run count will never balance, and staff will learn to ignore the discrepancy.

Returns and RTO after collection

A parcel that was delivered, paid for, then returned creates a refund that has to reverse through the same trail. If the reversal is handled outside the system, the parcel and money records diverge permanently. Related reading: NDR vs RTO.

Multi-day floats

Staff holding cash across days, or working weekends when no cashier is present, create a float that nobody is tracking. This is the most common source of genuine loss, and it is a process problem that software can only make visible — not prevent.

What good reconciliation looks like in software

  • Collection recorded per shipment, at the door, with payment mode
  • Expected-versus-actual comparison at handover, the same day
  • Partial and modified amounts permitted, with a mandatory reason
  • Digital payments tracked separately from cash
  • Deposits linked to the handovers they contain
  • Client remittance calculated from recorded collections, not re-entered
  • An ageing report showing cash outstanding by person and by day

That last item is the one most often missing and the most valuable. A simple list of who is holding how much, and for how long, turns a diffuse risk into a specific conversation.

The principle underneath all of it

Reconcile at the smallest interval you can manage. Daily beats weekly; per-run beats daily. The cost of investigating a discrepancy rises sharply with time, because the people involved stop remembering and the transactions stop being distinguishable.

Software does not stop cash going missing. What it does is make the gap visible within hours instead of weeks, and at that point most gaps turn out to be recording errors rather than losses.

Where we come in

COD collection, handover, deposit and remittance are part of the courier management systems and delivery management software we build. The field side of it — recording accurately at the door — is covered in courier mobile app development.

More reading

NDR vs RTO: What They Mean and How to Handle Them

Two of the most expensive words in delivery. One is a failed attempt, the other is a parcel going home — and how you handle the first largely determines how much of the second you get.

What Is Courier Management Software?

A plain explanation of what courier management software does, which parts of a courier operation it covers, and how to tell whether you actually need one.

Courier Aggregator vs Courier Management Software: Which Do You Need?

They sound similar and are priced similarly, but they solve opposite problems. One runs your own delivery network; the other distributes shipments across other people's.