You need to assign vehicles to drivers in the Fleet Portal and ensure the ELD device is connected and recording trips. No separate IFTA setup is required — mileage data collection starts automatically once the vehicle is active.
No separate IFTA configuration is required. Mileage data collection begins automatically once the ELD device is connected to the vehicle and trips are recorded. However, three things must be in place for the data to be accurate and complete.
Required Setup
1. **Vehicle added to the Fleet Portal** — the vehicle must exist in your account with the correct fuel type. Fuel type affects IFTA fuel tax calculations. See what vehicle information is required when adding a truck. 2. **ELD device installed and connected** — the device must be plugged into the vehicle's diagnostic port and paired with the driver app before each trip. See the ELD installation guide for setup steps. 3. **Driver logged in and connected** — the driver must be logged into the driver app and connected to the ELD device for mileage to be attributed to the correct vehicle and jurisdiction.
What Starts Automatically
Once these three elements are in place, the ELD records odometer readings from the engine ECM at the start and end of each driving segment, and GPS coordinates throughout the trip for jurisdiction attribution. No additional toggle or IFTA-specific setting needs to be enabled.
Avoiding Data Gaps
Missing mileage data happens when the ELD is not connected during a trip — for example, if the driver forgot to pair the app before departing. Encourage drivers to confirm ELD connection before every trip. See do you need to turn on the ignition before connecting the ELD for the correct connection sequence.
Verifying Collection Is Working
Fleet managers can verify mileage is being recorded by checking trip logs in the Fleet Portal. If a vehicle shows no activity during a period it should have been in use, investigate whether the ELD was properly connected during those trips.