Delivery management systems

Restaurant Rider Cash Settlement: A Daily Reconciliation Process

Set up a clear rider cash settlement routine using order references, expected collections, approved adjustments and documented handovers.

By Restrova Team · Published · Updated

4 min read · How we prepare our guides

Illustration of sealed takeaway bags beside a yellow insulated delivery bag
Editorial illustration, generated with AI · Not a product screenshot or customer photograph
Your practical checkAccount for cash after delivery is completed
  1. List expected collections
  2. Record the actual handover
  3. Investigate and assign differences

Delivered status and settled cash should remain separate until the restaurant can explain the handover.

Illustrative decision process, not a product screenshot or customer result.

A restaurant can complete every delivery and still have an unclear cash position at closing. Cash may remain with riders, an approved adjustment may be missing from the record or a delivered order may have been paid through another route. A daily settlement routine makes those differences visible.

This is an operating checklist, not formal accounting or legal guidance. Agree the records, responsibilities and treatment of adjustments with your business’s authorised decision-makers. The guide does not claim that every step is automated in Restrova Fleet.

Start from the orders assigned to the rider

Create a list of relevant order references for the settlement period. For each one, identify the expected collection route and amount. Separate cash due from orders already confirmed paid through another method.

Keep assignment, delivery completion and cash handover as distinct facts. A rider may have completed the customer handoff before returning to the restaurant. Do not mark cash settled only because the delivery stage is complete.

Use a simple settlement record

FieldPurposeExample entry type
Period and riderDefines the handover being reviewedShift and authorised rider reference
Order referencesLinks the amount to actual workList of assigned completed orders
Expected cashStates what should be handed overSum of confirmed cash-due amounts
Approved adjustmentsExplains agreed differencesAuthorised change with reason
Actual handoverRecords what the restaurant receivedCounted amount and receipt acknowledgement
Unresolved differenceKeeps an issue visibleAmount, explanation and review owner

Collect the information needed for accountability without placing unnecessary customer details into a shared settlement sheet.

Work through a sample calculation

Suppose three illustrative cash-due orders are PKR 1,200, PKR 900 and PKR 1,400. The expected collection is PKR 3,500. If an authorised PKR 200 adjustment is documented against one order, the adjusted expectation is PKR 3,300, assuming no other agreed movements.

If the rider hands over PKR 3,250, the PKR 50 difference remains unresolved until reviewed. Do not automatically label it theft or silently spread it across unrelated orders. Check the source records and retain the explanation of the final decision.

Control adjustments before closing

Identify who can approve an amount change and what evidence is required. A customer complaint, failed drop or returned item may require a business decision, but that decision should be linked to the relevant order and authorised role.

Avoid a process in which the person recording the handover also invents an adjustment solely to make totals agree. Where staffing permits, use an independent review for material differences. Ask the software supplier what approval and history mechanisms are actually available.

Handle incomplete and failed deliveries separately

An order that was not completed may have a different collection expectation from a completed cash delivery. The dispatcher should confirm the final operating outcome before settlement is closed. Record the responsible person for any customer or payment follow-up.

Do not use a generic delivered status to clear an unresolved task. The restaurant needs to know what happened to the order, the food and any collected amount. Use delivery exception planning alongside the settlement process.

Make the handover itself observable

Count the money through the agreed process and record who received it. Link the acknowledgement to the settlement period. If a handover is split across times or people, make each part explicit so the final total remains explainable.

At closing, list outstanding rider balances separately from cash physically received by the restaurant. The POS closing guide explains why those measures should not be collapsed into one number.

Ask Restrova to demonstrate the available records

Restrova offers Fleet delivery and rider management. The accompanying delivery video introduces the module, but it does not establish every settlement field, approval rule or report in this checklist.

Bring the three-order example to a demo. Ask which records the proposed system provides and which parts of the routine your team must perform. Review dispatch help and pricing before approving the scope.

Settlement questions

Is delivery completion enough to close a rider balance?

No. Confirm the expected collection and the actual handover through the agreed process.

What should happen to a small difference?

Keep it explainable and apply the business’s approved review procedure. Do not alter unrelated orders to conceal it.

Does delivery software guarantee that cash will reconcile?

No. Useful records support the process, but staff responsibilities, authorised adjustments and actual handovers still matter.

Use this delivery-management introduction to prepare the dispatch discussion. Verify the specific tracking, settlement, zone or recovery requirements in this guide separately; the video is not proof of each capability.

Restrova Deliveries Demo | Restaurant Delivery Management System

Restrova’s deliveries demonstration introduces organizing and managing customer delivery orders.

Watch this demonstration on YouTube · Published

Written overview, not a transcript. Use a live demonstration to verify the specific requirements in this guide.

Review customer implementations · Discuss your requirements

Keep reading