These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Pilgrimage / Religious Tourism
- Features
- Delivery and Charges
Delivery and Charges
Record the recipient handoff and review charge lines against the completed trip.
OverviewPending Delivery Evidence×
Pilgrimage / Religious Tourism · Delivery and Charges
New
Pending Delivery Evidence
Confirmed waits for the driver
| Trip | Delivered at | Recipient name | Proof | Status | |
|---|---|---|---|---|---|
| TRP-7676 | 04 Oct | Recipient 311 | PRF-195 | Pending | |
| TRP-7410 | 08 Oct | Recipient 945 | PRF-699 | Pending | |
| TRP-5100 | 09 Oct | Recipient 515 | PRF-803 | Pending | |
| TRP-6144 | 23 Oct | Recipient 520 | PRF-663 | Pending | |
| TRP-5946 | 11 Oct | Recipient 921 | PRF-819 | Pending |
6 of 6 records
Recipient 311Delivery evidence · DE-81989
PendingTripTRP-7676
Delivered at04 Oct
ProofPRF-195
What you can do
Close the operational handoff
Delivery evidence belongs to a trip and records when delivery occurred, who received it, the proof attachment and a confirmation status. Driver captures the handoff after the final stop. A pending entry remains available for review; a confirmed entry identifies a completed recipient handoff, while a disputed entry calls for follow-up. Operations Manager should compare that entry with the trip’s actual end and stop log before reviewing charges.
Each trip charge holds its type, amount, trip and lifecycle status. Delivery confirmation authorizes the trip’s draft charge lines. Operations Manager reviews the authorized lines against the journey before recording them as invoiced. Keep each charge linked to its trip reference so the reviewer can see the customer, route and delivery evidence behind it. Several charge lines may belong to the same journey, and their statuses can differ during review.
How the work is organized
- Recipient handoff. Delivery evidence keeps the recipient, delivery date, proof and status on the trip.
- Charge review. Trip charges show draft, approved and invoiced lines with amount and charge type.
- Trip context. Trip and stop records show the assigned movement and actual route history.
For a journey ending at a group destination, Driver records the recipient’s name and delivery time, attaches proof and marks the handoff confirmed after review. Operations Manager opens the completed trip, checks the last stop and delivery entry, and then reviews a draft transport charge. The manager checks whether the authorized line is supported by the journey evidence. The invoiced status identifies the later billing state of that line.
What to agree during setup
Agree what proof is appropriate for the team’s delivery handoff and who may resolve a disputed entry. Establish when the driver captures recipient details and when Operations Manager reviews them. Decide how charge type and amount are entered, who reviews an authorized line and how the team records an issued invoice. The app carries a charge lifecycle; the business should establish its billing connection and accounting handoff separately.
Keep the last passed delivery decision traceable if a dispute is raised. A disputed status should prompt review of the proof, recipient and trip times. The charge reviewer should not infer a completed handoff solely from a completed trip status. Likewise, an approved charge should be checked against the right trip and customer before invoicing.
Check the handoff on an actual case
Complete a rehearsal trip with its final stop and actual end. Create a pending delivery entry, record the recipient and proof, then review it with Operations Manager. Also test a disputed entry and agree who investigates. Add a draft charge before delivery confirmation. After confirmation authorizes it, have the manager compare amount, charge type, customer and journey evidence before invoicing. Finally, check the open charges view and the charges by trip report to make sure the line appears under the intended journey.
What your team sees
- Pending Delivery Evidence — Review trip handoffs still awaiting confirmation.
- Open Trip Charges — Follow draft and approved charge lines by journey.
- Draft Charge Review — Inspect draft lines before the delivery handoff.
Follow the work through
Use delivery and charges, reports and integrations for the downstream billing handoff.
What it keeps track of
Data model- Delivery evidence
- Proof of delivery recorded at the end of a trip with recipient and confirmation status.
- Trip charges
- Charge lines raised against a trip with draft, approved and invoiced lifecycle.
- Trips
- Planned and dispatched journeys carrying pilgrim groups between origin and destination.
- Trip stops
- Ordered itinerary stops for a trip with planned and actual arrival and departure times.
Who uses it
Permissions- Driver
- Records the handoff.
- Operations Manager
- Reviews authorized charges; Dispatcher and Admin review trip context.
Set up Pilgrimage / Religious Tourism your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.