At 9 PM the automation pulls each driver's cash-on-delivery stops from the delivery app, compares what was collected with what each order was due, emails finance a per-driver report flagging gaps, and builds a weekly remittance list for every web store.
Typical results
9 PM
Per-driver report in the finance inbox nightly
Same night
Cash gaps above the threshold flagged
≈6.5 hrs/wk
Finance time on reconciliation saved
≈65%
Fewer web store queries about COD payouts
Figures reflect typical results for this kind of automation.
The challenge
A courier collecting cash on delivery for web stores reconciles it from driver sheets and app exports once a week. By then a missing amount could be from any of a hundred stops, drivers no longer remember the details, and stores wait for payouts while finance spends a full day matching orders to cash and card records.
Before and after
Finance hours per week reconciling COD
−81%Hours until a driver's cash gap is flagged
−98%Web store queries about COD payouts per week
−64%The automation
Every night at 9 PM a Make scenario reads each driver's cash-on-delivery stops from the delivery app, including the amount recorded as cash or card. It matches each stop to its order and the amount due, then emails the finance team a per-driver report with totals and any gap above a set threshold, listed by order number. Matched collections go into a Google Sheets ledger, and each week it builds a remittance list for every web store with order-level totals.
How it works
- 01
Day's COD stops pulled
At 9 PM the automation pulls every cash-on-delivery stop from the delivery app, with the amount each driver recorded as cash or card.
- 02
Compared with amounts due
Each collection is matched to its order and compared with the amount due set by the web store.
- 03
Gaps flagged
Any difference above the set threshold is flagged with the driver, the order numbers and the size of the gap.
- 04
Report to finance
Finance gets an email with one line per driver: stops, cash, card, amount due and any gap to check.
- 05
Weekly remittance list
Every week each web store's remittance list is built with order-level totals, ready for the payout.
Starts from
- Driver COD stops in app
- Amount due per order
Delivers
- Per-driver gap report
- Weekly remittance per store
The impact
Cash gaps are flagged the same night, while drivers still remember the stop. Finance spends about 6.5 fewer hours a week on reconciliation, down from roughly 8 to 1.5, and web store questions about COD payouts drop by about 65%, from around 14 a week to 5.
Questions about this automation
How are card payments on delivery handled?
Drivers record each payment as cash or card in the delivery app, and the report shows the two separately for every driver. Cash is what the driver hands in at the depot, so it is compared with the cash total, while card amounts are listed for finance to match with the terminal statement.
What happens when a gap is flagged?
The report shows the driver, the order numbers and the size of each gap, so finance can check it with the driver the next morning. Once a gap is explained, for example a partial payment the web store approved, it is marked resolved in the sheet and drops off the next report.
What is needed before the first nightly run?
Stop data from the delivery app, the amounts due on each web store's orders and the gap threshold finance wants. A week of parallel runs against the manual count confirms the numbers. This is a multi-step build, usually rolled out in stages, with the weekly remittance list added once the nightly check is trusted.