
Alvys stores all fuel and toll transaction times in UTC and converts them to your local time zone for display; a transaction date in Alvys may differ by one day from the same transaction in your provider’s portal.
Overview
Alvys stores all fuel and toll transaction timestamps in Coordinated Universal Time (UTC) and converts them to each user’s local time zone at the point of display. This approach ensures that transaction data synced from multiple providers such as EFS, Comdata, Relay, and Loves is stored on a single consistent standard, regardless of the time zone each provider uses internally. The result is that the time shown in Alvys for any given transaction reflects your local time, while the same transaction in your provider’s portal may show a different time. In some cases, the UTC conversion can shift a transaction into a different calendar day, which matters when you are filtering by date. Synonyms: UTC time, time zone conversion, transaction time discrepancy, date filter, time zone offset, fuel transaction date, toll transaction date.Where to Find It
Fuel and toll transactions are visible in Driver Settlements. Open the Driver Settlements module, locate the relevant driver or truck record, and navigate to the Fuel or Tolls tab to see transactions with their converted timestamps.Key Concepts
UTC storage All transaction timestamps are stored in UTC when they arrive in Alvys, regardless of the time zone used by the originating provider. Local time display When you view a transaction, Alvys converts the stored UTC timestamp to your local time zone based on your browser or device settings. Two users in different time zones viewing the same transaction will each see a different local time. The one-day shift Because a UTC timestamp is always ahead of US time zones, a transaction that occurred late in the evening local time may be stored in Alvys with a UTC date that falls on the following calendar day. Conversely, a transaction stored at midnight UTC may display as the previous evening in your local time zone. This is expected behavior and is not a data error. Example: a transaction timestamped 2024-12-10 at 02:14 UTC will display as:- 2024-12-09 at 20:14 in Central Time (UTC-6)
- 2024-12-09 at 19:14 in Mountain Time (UTC-7)