Collections Management
Version: v1.0
Last Updated: June 6, 2026
How to manage customer money collected by riders on behalf of partners and keep remittance accurate.
What a collection is
A collection is money a rider takes from a customer during a pay-later fulfillment flow, such as:
- cash on delivery
- card on delivery
- other supported collection-at-handoff flows
This money is not the rider's earnings and not the delivery company's revenue. It belongs in the wider settlement flow and must be tracked accurately.
Not every task creates a collection
Some tasks are paid online before the rider arrives. Others are collected at handoff.
That means:
- restaurant/shop COD-style tasks often create rider collections
- some other delivery or handoff flows may create collections
- parcel delivery often uses online payment instead of rider-collected cash
- mixed-source reporting may therefore show both collection and non-collection deliveries side by side
What the collections screens show
Collections views typically help you review:
- total collected per rider
- total remitted
- outstanding amount still held by the rider
- transaction-level breakdown by source and reference
📸 Screenshot: Delivery-company app — collections dashboard
Where supported, the breakdown may span mixed sources rather than only simple order rows.
Confirming remittance
When a rider hands in collected cash or reconciles collected amounts:
- Open the rider or collections view
- Review the outstanding items
- Mark the relevant amounts as remitted
- Verify the outstanding balance has reduced correctly
This keeps both finance and settlement reconciliation accurate.
Reconciliation and settlement
Collections feed into the wider settlement model.
That means:
- collected customer money must be distinguished from delivery-company earnings
- partner remittance and platform settlement depend on correct collection tracking
- inaccurate remittance states create downstream finance mismatches
For that reason, do not mark items remitted unless the money has really been accounted for.
Handling discrepancies
If the amount collected does not match what the system expected:
- inspect the per-reference breakdown
- confirm what the rider actually collected
- review the payment mode on the source task
- escalate unresolved mismatches through support instead of force-clearing the balance
Mixed-source operations make this even more important, because not every delivery follows the same financial pattern.
Exports and reporting
Use the collections and finance reports to:
- filter by rider or date range
- export CSVs
- review outstanding remittance
- reconcile partner-facing collections against completed delivery work
These reports are especially useful at end-of-day and end-of-shift reconciliation time.