Reconciliation and payment

Step by step

1. Select an exception Booking Supervisor

   Booking Supervisor opens pending, failed or review-needed operations. Read the action, operation key, expected revision and failure reason before deciding whether another attempt is appropriate.

   • Identify unresolved actions
   • Updates Operation receipts

2. Compare actual effects Booking Supervisor

   Follow effect references to the linked booking and ride records. Compare scope, identity and quantities with the authorized revision. Inspect relevant attachments when the outcome depends on physical service evidence.

   • Test the expected effect against evidence
   • Updates Bookings, Booking resources, Ride sessions, Review decisions, Record attachments

3. Resolve the operation Booking Supervisor

   Record Completed only when the expected effects match. Otherwise keep the operation in need of review with the discrepancy explained. Keep the original receipt and use the stable operation identity so a retry cannot silently duplicate completed service.

   • Record Completed or needs review
   • Updates Operation receipts

4. Verify payment events Booking Supervisor

   Examine provider authorization, capture, refund and void events for the same booking. Check event identity and verification state through the configured provider procedure before using the event in a payment explanation.

   • Check provider events and verification
   • Updates Payment evidence, Bookings

5. Read the reconciled result Auditor

   Auditor reviews operation outcomes alongside verified payment evidence. Keep quoted value, recorded fare and provider event amounts distinguishable, and retain a clear path from each event back to its provider reference.

   • Explain service and payment outcomes
   • Updates Operation receipts, Payment evidence, Ride sessions, Bookings

Booking Supervisor

, Booking Coordinator and Auditor.