What's New - TOBI v4.56.0 - Apr 15, 2025
Discover the latest enhancements and features in TOBI version 4.56.0 released on Apr 15, 2025, to boost your productivity and efficiency.
Table of Contents
Hey everyone!
We released Version 4.56.0 on Tuesday, April 15, 2025. In this release, we’ve rolled out a set of impactful updates focused on streamlining claim processing and improving real-time system behavior across dispatch and reporting.
These updates aim to give dispatch teams more control, better visibility into payment processing, and a smoother operational experience across the board.
Enhancements to Auto-Update of Booking's Billing Status from Paid Claims
In addition to our recently released feature of “Auto-Updating Booking's Billing Status” based on a backend-configured threshold, we are introducing the following improvements to give tenants more control and accuracy in claims processing.
Account-Level Threshold Configuration for Paid Claims
Tenants can now configure the threshold amount for marking bookings as Paid directly from the Account Settings >> Claim Provider Settings screen.
Front-end Threshold Setting:
- Previously, the threshold was set at the backend. Now, a dollar value can be entered by the tenant admin in the UI.
- This threshold defines the maximum acceptable difference between the claim paid amount and the invoice amount, within which the booking will be considered fully paid.

Bookings Marked as Paid or Partial Paid (based on UI-configured threshold):
- When a claim is marked as Paid on Kinetik, TOBI will automatically mark the booking's billing status as Paid if the claim amount is within the configured threshold.
- If the difference exceeds the threshold, the booking will be marked as Partial Paid.
- Threshold values can be updated by the user at any time and will apply to all future claims processed.
Billing Status Updates for Bookings Invoiced After Claim Payment
If an invoice is created after a claim has already been marked as Paid on Kinetik,
- TOBI will now evaluate the claim against the invoice using the same threshold logic,
- And will update the booking's billing status to Paid or Partial Paid accordingly.
This ensures bookings remain aligned with payment outcomes, regardless of the invoice creation timeline.
Enhanced Real-Time Operations and API Behavior
We reviewed and refined how the system handles real-time events and API interactions across key modules. These backend enhancements directly contribute to more responsive dispatcher screens and fewer data inconsistencies.
- Real-time events like driver location updates, break time tracking, and driver status changes were validated and improved to ensure accuracy.
- System behavior during trip assignment, driver capacity distribution, and driver availability changes has been made more predictable.
- Driver shift operations - adding, updating, and reflecting changes across screens - are now more stable and reliable.
- Assigning or updating fleet and vehicle details for drivers is now validated more thoroughly to reduce errors.
- Date range filters across critical reporting and operational screens - Workbook, Operations, RP, and Reports - have been verified and stabilized.
These improvements ensure that dispatcher actions are reflected in real time. By improving the way date inputs and filters work, we aim to reduce booking errors and ensure consistent views across operations and reporting teams.
Bug Fixes:
Bug Fix: Driver Unable to Take Break
A critical issue was resolved where certain drivers were unable to initiate their Take Break action despite being eligible.
- The break-time workflow and related driver status APIs were stabilized to address this.
- As a result, drivers can now reliably start, end, and extend breaks - ensuring accurate visibility for dispatchers and minimizing disruption to trip schedules.
Bug Fix: Claim Modifier Update Not Logged
An important fix was made to the Claims section. Previously, updates to the Modifier field in submitted claims were not recorded in the Adjustment log.
- Now, any changes made to the Modifier field during claim resubmission are properly reflected in the adjustment section.
These changes are part of our ongoing effort to make the dispatch experience more reliable, transparent, and efficient for all stakeholders.
As always, we appreciate your support and look forward to your feedback!