Cutoff Passed Cases – Resolution Process

Overview:
Cutoff Passed Cases refer to bookings where the assigned vendor was unable to allocate a cab before the scheduled start time of the trip. These instances may occur due to several reasons, including:

• API failures on our end

• Unexpected payload or request formats from external vendors

• Manual oversight in the case of internal vendors

• Other unforeseen issues

Next Steps:
When a Cutoff Passed Case is identified, the Client must first confirm that the trip was manually completed by the vendor. Once confirmation is received, the resolution steps vary based on whether the vendor is internal or external.

For Internal Vendors:

1. Client Action:
   Share the specific instance(s) with us, including relevant booking IDs.

2. Our Action:
   We will convert the booking into a backdated booking through a data fix.

3. Post-Fix Actions:
   Once the booking is backdated:

   • The cab can be allocated via the Rentlz dashboard

   • Duty details can be edited via the Invoices and Payments dashboard

   • After marking the trip as completed, the vendor can proceed with invoicing

For External Vendors:

1. Client Action:
   Share the specific instance(s) with us, including:

   • The MoveInSync Booking ID

   • The corresponding Booking Reference Number generated by the vendor

2. Our Action:
   We will convert the booking into a backdated booking through a data fix.

3. Post-Fix Actions:
   Once the booking is backdated:

   • The vendor can allocate the cab via API

   • Push duty details through the API to mark the trip as completed

   • The vendor can then proceed with invoicing