Receipts Management for Last-mile delivery companies
Reconcile contracted merchant collections through actual customer payment, custody handover and merchant remittance.
Does this function belong in your operation?
Use only where the operator is authorised to collect money for the merchant; prepaid delivery alone does not create this requirement.
Payment is reported or evidenced for a parcel under an actual collection agreement.
Where the contract includes cash on delivery, identify the merchant that owns the collection, the parcel, payer, evidence and current custodian. Keep a rider’s customer collection distinct from the later office handover and eventual merchant remittance. The same money must appear once as received from the customer. A digital-payment screenshot needs verification, and differences remain unresolved until reviewed. Delivery fees, rider expenses and merchant refunds require separate approved records rather than unexplained deductions.
Bring the records the workflow depends on.
- Actual collection agreement and merchant owner of funds
- Parcel, payer and approved collection amount
- Payment evidence, verification status and current custodian
- Internal handover and merchant-remittance references
Outputs to check
- Merchant-owned collection register by parcel
- Rider and office custody reconciliation
- Pending, evidenced and disputed merchant-remittance statement
Follow the receipts management workflow.
Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.
Who uses the module, and who approves?
Keep responsibilities distinct even when one person holds more than one role.
Decide how exceptions are handled.
These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.
Can this work independently?
An actual collection agreement, approved accounting design and payment-verification process are prerequisites. The merchant’s collection balance requires a separate ledger from service receivables. The module records evidence and allocations; payment execution and authorised deductions need separately supported processes.
Systems and records it connects with
- Delivery orders: Approved merchant collection instructions and parcel references.
- Bank and cash records: Verified funds, custody transfers and reversals.
- Merchant settlement records: Authorised adjustments and actual remittance evidence.
Configure, test and introduce the workflow.
- Trace a contracted cash collection and digital payment through actual custody and settlement.
- Confirm separate merchant and operator accounts with the accounts owner.
- Test direct-to-merchant payment, a short rider handover and reversed remittance without duplicating receipts or netting unexplained costs.
Check the result before rollout.
Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.
- Customer money is counted once despite later internal handover.
- Merchant funds stay distinct from operator delivery-fee receipts.
- Expected, reported and verified amounts remain distinguishable.
- Remittance approval and actual settlement have separate evidence.
How the business operates.
A last-mile delivery company takes custody of a merchant’s parcels at a hub or pickup point and coordinates their delivery attempts and authorised returns. The goods are entrusted for delivery under the accepted merchant instructions and remain outside operator-owned stock; the delivery operator manages the service and custody records. This proposed software scope connects merchant instructions, actual parcels, rider assignments, attempt evidence and commercial reconciliation. Where cash on delivery is contracted, money collected for the merchant must remain separate from the operator’s delivery-service revenue. A completed rider task can represent a failed attempt, so delivery, return and cash outcomes need their own evidence.
The records that hold the operation together.
- Merchant order and accepted delivery-service reference
- Parcel identifier, expected and actual piece counts and custody acknowledgements
- Recipient instructions and authorised changes with access restrictions
- Rider assignment, attempt outcome and supporting evidence
Operational bottlenecks to check
Assignment changes but parcels stay with the first rider
A reassigned task is not a custody transfer. Both workers’ acknowledgements and unresolved parcels need to remain visible.
A closed attempt appears as a delivery
Failure, refusal and incomplete evidence need explicit outcomes. A closed work item must not inflate the delivered-parcel count.
How work flows across this business
This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.
1. Accept the merchant request
Confirm the actual delivery service, parcel references and collection instruction if contracted. Keep specialised goods or handling outside acceptance until separately reviewed.
2. Receive and allocate custody
Match physical parcels to the request and record exceptions. Assign the work and acknowledge the actual handover to the rider.
3. Record each attempt
Capture the attempt outcome and required evidence without turning an address visit into delivery. Refer refused, inaccessible or disputed handovers for the agreed decision.
4. Resolve undelivered parcels
Retain prior attempts while recording an authorised reattempt or return. Confirm physical custody and merchant receipt rather than closing a return from its instruction alone.
5. Reconcile money and fees
Review any customer collection, rider-to-office handover and actual merchant remittance. Separately bill the accepted delivery services and approved additional work.
Industry reports to connect with
- Parcels by merchant, custodian and unresolved mismatch
- Unassigned work and attempts awaiting review or instructions
- Delivered, failed, reattempted and physically returned parcels
- Collection differences by rider, payment evidence and merchant
Questions before implementation.
When should last-mile delivery companies consider receipts management?
Use only where the operator is authorised to collect money for the merchant; prepaid delivery alone does not create this requirement. Payment is reported or evidenced for a parcel under an actual collection agreement.
What should we bring to the requirements discussion?
Bring anonymised examples of Actual collection agreement and merchant owner of funds; Parcel, payer and approved collection amount; Payment evidence, verification status and current custodian; Internal handover and merchant-remittance references. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.
Does this replace our existing business software?
The starting point is your current system and the gap you need to close. Reconcile contracted merchant collections through actual customer payment, custody handover and merchant remittance. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.
What is outside this module?
This record does not move funds, establish bank clearance or authorise collection outside the agreement. It is not the operator’s merchandise-sales ledger.
How are scope, price and rollout decided?
The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Customer money is counted once despite later internal handover. Use this check when reviewing the first working version.
Related functions for last-mile delivery companies.
Discuss receipts management for your business.
Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.
What happens after you share your requirements
- We review your brief and the systems you already use.
- We clarify the workflow, missing information and the work to consider first.
- The proposed scope sets out the deliverables, responsibilities and dependencies.
- Review the scope and commercial terms before deciding whether to proceed.
Start with your requirements
Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.
Share your requirements