Fuel card data, native, not exported nightly.
Fuel is the second-largest expense in a trucking operation after driver pay. The carriers that don't track it tightly leak margin every week. Keelway pulls Fleet One EFS transactions every 10 minutes via static-IP proxy, attributes each transaction to the right truck and the right active load, and feeds the per-state gallons directly into the IFTA worksheet.
Fleet One EFS every 10 minutes
Total spend, gallons, avg $/gallon
Gallons-by-state feed for IFTA
CSV upload for non-EFS cards
Frequently asked questions
Which fuel cards does Keelway support?+
Fleet One EFS is the day-one integration. Comdata and EFS Smart Funds are on the roadmap. WEX and TCH are scoped but not yet in active build. CSV upload supports any fuel card that exports a transaction CSV.
How does the sync work?+
Two paths. Auto-sync via static-IP proxy pulls Fleet One EFS transactions every 10 minutes — works on enterprise tenants where the IP allowlist on EFS is configurable. CSV upload works on every tier for periodic batch import.
What does the per-state breakdown enable?+
Direct IFTA filing. The per-state gallons by truck feed Keelway's IFTA quarterly worksheet automatically. The accountant gets real gallons, not estimates from odometer-and-MPG math.
What is an unmatched transaction?+
A fuel transaction that Keelway couldn't attribute to a specific active load (because no truck was assigned, the timestamp didn't overlap a load window, or the truck wasn't recognized). Unmatched transactions surface for the controller to assign manually.