Why is there a discrepancy in the trip report?

Issue Title

Trip report discrepancy

Issue Summary

A discrepancy in the trip report may occur when the device sends incomplete, delayed, inaccurate, or duplicate location and vehicle-status data, or when the system's trip calculation rules and configuration do not correctly interpret the received data. This can affect trip start/end times, duration, distance, stops, and trip status.

Symptoms / How to Identify

Trip distance does not match the actual distance travelled.
Trip start or end time is incorrect.
Trip duration is higher or lower than expected.
Trips are missing or split into multiple trips.
Multiple trips are created for a single journey.
A trip is shown when the vehicle did not move.
A trip is missing even though the vehicle travelled.
Stop locations or stop durations are incorrect.
Trip information differs between reports, history, or playback.

Information Required Before Troubleshooting

Vehicle/Object name or ID
Device IMEI/Serial Number
Report name
Date and time range
Actual trip details, if available
Trip distance shown in the report
Trip start/end time shown in the report
Trip duration
Relevant Status/Raw Data
Vehicle/device configuration
Trip calculation settings and thresholds
Screenshot or exported report
Whether the issue affects one vehicle or multiple vehicles

Troubleshooting Steps

Check on Device

Verify that the device was powered ON and transmitting data during the trip.
Check the GPS coordinates received throughout the journey.
Verify that the coordinates change correctly while the vehicle is moving.
Check the speed and ignition values generated by the device.
Check for missing, delayed, or duplicate GPS data.
Verify whether the device experienced network interruptions.
Check whether stored data was retransmitted after connectivity was restored.
Verify device configuration and transmission interval.

Check in System

Verify the report's date, time range, vehicle, and filters.
Check the vehicle's history and playback for the same period.
Open Status/Raw Data and review the location, speed, and ignition data.
Compare the trip start and end points with the actual journey.
Verify the configured trip start/stop conditions and thresholds.
Check the configured minimum stop duration, speed threshold, or other trip parameters, if applicable.
Compare trip distance and duration with other relevant reports.
Verify timezone and date/time settings.
Check whether the same discrepancy occurs for other vehicles.

Compare and Identify

Incorrect or incomplete GPS data from the device: Investigate device/GPS/network issues.
Incorrect ignition or speed data: Investigate device inputs or configuration.
Correct raw data but incorrect trip calculation: Investigate trip rules and system configuration.
Missing GPS points: Investigate device transmission or network connectivity.
Trip differs only in one report: Investigate that report's calculation or processing.
Multiple trips generated for one journey: Check trip thresholds and stop/start rules.

Possible Causes

Missing or inaccurate GPS data.
Poor GPS signal.
Delayed or duplicate location data.
Incorrect ignition or speed data.
Network connectivity issues.
Incorrect trip start/stop thresholds.
Incorrect minimum stop duration.
Incorrect device configuration.
Incorrect timezone or date/time settings.
Different calculation methods between reports.
System-side trip calculation or processing issue.

Resolution / Action

Compare the actual journey, device data, system raw data, history/playback, and trip report for the same vehicle and time period.

If the device is providing incorrect or incomplete GPS, speed, or ignition data, investigate the device, sensor, network, or configuration. If the raw data is correct but the trip is calculated incorrectly, verify the trip configuration and escalate to the technical/system team if required.

For escalation, provide the vehicle ID, IMEI, report name, date/time range, expected and reported trip details, trip configuration, and relevant raw data.