Cash-on-delivery reconciliation automation

COD reconciliation is the job of proving that the cash a driver collected at a doorstep is the cash that reached the bank, and that the right amount was then settled to the shipper. Most operators still do it monthly, from exported spreadsheets, and it takes a finance team two days or more to close. Automated reconciliation does the matching daily, at delivery level, and leaves people only the exceptions. This article explains how the automation works, what data it needs, where it breaks, and what it costs to build.

The important shift is not speed. It is that a daily, delivery-level match finds shortfalls while the driver is still on shift and the memory is fresh, rather than thirty days later when nobody can explain a missing amount.

Why COD reconciliation matters more than it looks

Cash on delivery is still a large share of parcel volume in India and in many other markets, and every rupee of it passes through a driver, a hub cashier and a bank before it reaches the shipper. Each hand-off is a place where money can be delayed, mis-keyed or lost. When reconciliation is monthly, the operator carries the float and the risk for the whole month, shippers wait for settlement, and disputes arrive with no evidence trail.

Daily reconciliation changes the economics. Shortfalls are small and attributable, deposits are verified before the next shift, and settlement to shippers can move from monthly to weekly or daily, which is a commercial advantage for the operators we describe on the logistics industry page.

Manual versus automated reconciliation

The four ledgers you are matching

Reconciliation is easier to design once you name what is being matched. There are four records for every COD parcel, and they are created by different people at different times.

• Expected collection: the COD amount on the consignment, set by the shipper when the order was created
• Actual collection: what the driver recorded at the doorstep, including method (cash, UPI, card on a handheld) and any partial or refused delivery
• Deposit: what the driver handed to the hub cashier or deposited at a bank or cash-management partner, per shift
• Settlement: what the operator paid the shipper, net of freight and COD handling charges, per cycle

The automation matches expected to actual per delivery, actual to deposit per driver-shift, deposit to bank credit per hub-day, and settled to collected per shipper-cycle. Each layer produces its own exception list, and each exception has an owner.

Where the data comes from

The driver app is the source of truth for collections

If drivers record collections on paper or in WhatsApp, no reconciliation software will fix the numbers. The driver app must capture the amount, the payment method and a proof (photo of the UPI confirmation, signature, or OTP) at the moment of delivery, and it must do this offline, because the doorstep often has no signal. We covered the sync design in building an offline-first driver app.

UPI and bank feeds

UPI collections settle to the operator's account with a reference that can be matched to the delivery if the QR was generated per consignment. Static QR codes on a driver's phone make matching much harder, because the credit carries no consignment identity. Where a dynamic QR is not possible, the app should record the UPI transaction ID from the customer's confirmation screen. Bank statement feeds can be pulled through the bank's API or a daily file; the NPCI documentation is the reference for UPI settlement behaviour.

Cash-management partners

Operators using a cash-pickup partner receive a daily file of deposits by location, which becomes the deposit ledger matched against the hub's per-driver slips.

Driver cash management: exceptions and controls

The purpose of daily reconciliation is to turn a vague monthly shortfall into a specific, same-day question. Good driver cash management is mostly about how exceptions are handled, not about how matches are computed.

• A driver's deposit is below expected collections: hold the exception against the driver, notify the hub supervisor before the next shift, and allow a reason code (customer paid by UPI, parcel refused, partial delivery)
• A delivery is marked collected but no payment proof exists: flag for supervisor review within 24 hours
• A UPI credit exists with no matching delivery: park it in an unapplied-receipts queue and match it when the sync arrives
• A shipper disputes a settlement line: show the delivery record, proof and deposit chain in one screen
• Repeated shortfalls by one driver or one hub: trend report to operations weekly, with thresholds set by finance rather than hard-coded

Controls should be proportionate: a system that blocks the next shift over a small rounding difference will be worked around.

Shipper settlement: from monthly to daily

Once collections and deposits reconcile daily, cash on delivery settlement to shippers can follow the same cadence. The settlement engine takes reconciled collections per shipper, applies the freight and COD-handling charges from the contract, nets any deductions, and produces a settlement file with delivery-level lines. Shippers can then reconcile on their side without raising queries.

Settle only reconciled deliveries, and keep settlement rules per contract in configuration so finance can change them without a developer.

Choosing logistics reconciliation software

There are three routes: a module in a logistics ERP, a standalone reconciliation tool, or a custom build on top of the existing dispatch and driver app. The right one depends on where the collection data lives today. If the driver app is already yours and captures collections properly, a custom reconciliation service is usually smaller than people expect, because the hard part, delivery-level data capture, is already done. If the driver app is a vendor's and cannot be changed, an ERP module or a standalone tool that ingests its exports is more realistic. We described the broader ERP landscape in logistics ERP: fleet, dispatch, settlements and reconciliation.

Whatever you choose, insist on delivery-level matching, same-day exception queues with owners, configurable settlement rules and an immutable audit ledger. Otherwise finance will keep the spreadsheet.

A worked example

A last-mile operator we worked with ran COD reconciliation monthly, from driver-app exports and bank statements, and closed in about two days of finance effort each month. Shortfalls were discovered weeks after the fact and rarely traced to a driver. As part of the dispatch platform and driver app build, the driver app captured amount, method and proof at delivery, and hub cashiers confirmed per-driver deposits on a tablet at end of shift.

A reconciliation service then matched collections to deposits nightly and deposits to bank credits the following morning. Exceptions went to hub supervisors with the driver, route and delivery attached. Finance moved from a monthly close to a daily review of a short exception list, and shipper settlements moved to a weekly cycle with delivery-level files. The qualitative change reported by the finance team was that disputes stopped being arguments and became look-ups.

Team and timeline

A reconciliation service on top of an existing driver app is typically a six-week build for a small team: one backend engineer for the matching and settlement engine, one for bank and UPI integrations, a designer for the exception and cashier screens, and a delivery lead who spends the first fortnight with finance mapping the four ledgers and the contract rules. This fits the Launch 6 programme at $26,500–45,500 or from ₹17,60,000 on a fixed date. If the driver app also needs to change, scope it under product and platform development, which starts at $42,000 or ₹28L, and see the pricing page for how programmes are credited against builds.

If the ledgers are unclear or the data sources are uncertain, start with a Sprint Zero discovery at $3,250 or ₹2,00,000, which is credited to the build. After go-live, a Standard Care Plan covers bank feed changes and new shipper contracts.

Before you start: a checklist

• Confirm the driver app captures amount, payment method and proof at delivery, offline
• List every deposit channel: hub cashier, bank branch, cash-management partner
• Get API or daily-file access to bank statements and UPI settlement reports
• Write down the settlement rules for your five largest shippers
• Agree exception owners and tolerances with finance and operations
• Decide whether settlement will be daily, weekly or per contract
• Export three months of history to test the matching before go-live
• Name the finance owner who will review the exception queue each morning

Glossary

• COD: cash on delivery, where the customer pays the driver at the doorstep
• Expected collection: the COD amount set on the consignment by the shipper
• Deposit slip: the record of what a driver handed over at the hub or bank per shift
• Unapplied receipt: a bank or UPI credit not yet matched to a delivery
• Settlement cycle: the period after which reconciled collections are paid to a shipper
• Exception queue: the list of mismatches awaiting a person's decision

Related reading

See dispatch and routing engines for the dispatch side of the platform, AI in logistics: dispatch, exceptions and customer updates for what sits on top, and the logistics industry page for the full picture.

Reconcile daily at delivery level, give every exception an owner, and the monthly close becomes a short morning review.