Each reading also carries the date and time and the vehicle or unit number. Files must be XLS, XLSX, CSV or delimited text, not PDF or images. IFTA Procedures Manual P540.200; IRP Plan Section 1010(b).
The P540.200 standard
The IFTA Procedures Manual has two sets of distance record rules. P540.100 covers trip sheets and other records kept by hand (see IFTA record keeping). P540.200 covers distance records produced by a vehicle-tracking system that uses latitude and longitude. For those, “a record must be created and maintained at a minimum every 10 minutes when the vehicle's engine is on”, and each record must contain four data elements:
| Data element | Section | Detail |
|---|---|---|
| Date and time of each system reading | P540.200.005 | Every reading, not a daily total |
| Latitude and longitude of each reading | P540.200.010 | At least 4 decimal places (0.0001) |
| Odometer reading from the engine control module (ECM) for each reading | P540.200.015 | If no ECM odometer is available, a beginning and ending dashboard odometer or hubodometer reading for the trip |
| Vehicle identification number or unit number | P540.200.020 | Ties every reading to one qualified vehicle |
The standard came from Ballot 1-2023, which the membership ratified at the 2023 Annual Business Meeting, effective January 1, 2024 (P540 commentary). IFTA, Inc.'s ballot page lists it as the standardization of electronic audit records. The ballot set the minimum reading interval, the decimal places for latitude and longitude, and the meter reading for each system reading.
Many base jurisdictions now repeat the standard word for word. Idaho's IFTA handbook (September 2026) and Illinois Publication MFUT-53 both print the 10-minute rule and the same element list. Some older state publications do not: Florida's IFTA Trucking Manual (HSMV 85920, December 2021, before the ballot) describes electronic distance records with location “documented at most every 15 minutes”. For IFTA records kept today, the Procedures Manual is the rule: R1320 requires every IFTA audit to comply with the Agreement and both manuals.
The spreadsheet rule
P540.200 ends with a format requirement that trips up many carriers: “This data must be accessible in an electronic spreadsheet format such as XLS, XLSX, CSV or delimited text file”. It then rules out the reports many systems print: “Formats from a vehicle tracking system that provides a static image such as PDF, JPEG, PNG, or Word are not acceptable”.
In practice that means the raw readings, one row per reading, with columns for the date and time, latitude, longitude, odometer and unit number. A quarterly state mileage summary in PDF form is a summary, not the underlying record. Keep the summary if it helps, but make sure the raw export exists and that you can produce it for any quarter in the last four years. P530 adds the general rule: records in a form the auditor cannot audit have not been made available as required.
A GPS or ELD vendor's IFTA mileage report in PDF does not satisfy P540.200. Keep the raw readings in a spreadsheet format, and keep them yourself for the full four-year retention period in P510.
There is no IFTA-certified ELD
No IFTA document certifies devices, and the 2026 Articles, Procedures Manual and Audit Manual do not mention electronic logging devices. The Texas DMV, which runs IRP in Texas, says it directly on its apportioned registration page: “There is no such thing as an IFTA- or IRP-certified ELD. Be cautious of vendor claims.” The same page adds that buying an ELD does not guarantee it is compliant for IRP or IFTA recordkeeping.
State fuel tax agencies say the same. Illinois tells its licensees that “the primary function of an electronic logging device (ELD) required by the Federal Motor Carrier Safety Administration (FMCSA) is for logging a driver's record of duty status, not for keeping records required by IFTA”. Idaho's handbook is blunter: “ELD's are NOT a substitute for the recordkeeping requirements for IFTA or IRP.” Both agencies accept electronic records; their point is that the device has to produce the P540.200 data, and you have to keep it.
What a federal ELD records, and what it does not
The federal ELD rule is in 49 CFR part 39549 CFR part 395Code of Federal Regulations, eCFR, the hours-of-service rules. Under 49 CFR 395.26(b), an ELD automatically records the date, time, location information, engine hours, vehicle miles, and driver, vehicle and carrier identification. Those records are made at each change of duty status. While the truck is moving without a status change, 395.26(d)(1) requires an intermediate recording when there has been none “in the previous 1 hour”. One reading an hour is far from the IFTA minimum of one every 10 minutes.
Personal conveyance is another gap. During authorized personal use, 395.26(d)(2) says engine hours and vehicle miles are left blank and location is recorded only to about a 10-mile radius. Total distance on the IFTA return covers all travel by the qualified vehicles in your fleet (P710.100), so you need another record of those miles.
| IFTA GPS record (P540.200) | Federal ELD (49 CFR part 395)49 CFR part 395Code of Federal Regulations, eCFR | |
|---|---|---|
| Purpose | Distance by jurisdiction for fuel tax | Hours of service |
| Reading frequency | At least every 10 minutes with the engine on | At each duty status change, plus an intermediate recording after 1 hour in motion |
| Location precision | Latitude and longitude to 4 decimal places | Location information; about a 10-mile radius in personal use |
| Odometer | ECM odometer at each reading | Vehicle miles, left blank in personal use |
| Retention | Four years from the later of due date or filing date (P510) | Not less than 6 months (395.8(k)) |
The ELD and hours-of-service sections saved for this site (395.1, 395.8, 395.11, 395.22 and 395.26) do not mention fuel or fuel tax at all. Many ELD systems also include a separate GPS feature; whether that feature meets P540.200 is a question about the data it exports, not about the ELD certification.
IFTA 10 minutes, IRP 15 minutes
The International Registration Plan, which apportions registration fees by distance, has its own GPS rule. IRP Plan Section 1010(b) requires a record “at a minimum of every 15 minutes when the Vehicle's engine is on”. Ohio's Department of Taxation, which audits both programs, sums it up: a record must be made “at a minimum of 15 minutes for IRP and 10 minutes for IFTA”. A system set to the IRP interval does not meet the IFTA one. Set it to 10 minutes or less and the same data serves both. IRP keeps records three years after the registration year (Section 1000(a)); IFTA keeps them four years from each return (P510). See IRP records and audits.
How auditors use GPS data
Audits are done on a sample basis unless a specific situation calls for more (IFTA Audit Manual A330). For distance, the Audit Manual says “If the base jurisdiction utilizes a distance software program to verify the records of the licensee, that software program shall be used as an audit tool for verification of reported distances”. In other words, the auditor may run your readings through the jurisdiction's own software and compare the result with your returns.
Gaps in the data become audit issues. If the auditor finds distance you did not report and cannot tell where it was driven, A340 says it is allocated using a rational and unbiased approach. The Texas Comptroller's FAQ calls the difference between trip-sheet miles and odometer miles "gap miles" and says they are usually an audit issue. A GPS record with ECM odometer readings at each point is the best defense against both.
If the auditor decides the fleet's records as a whole are not adequate, the formula in P570 applies: fleet MPG reduced to 4.00, or the reported consumption factor cut by 20 percent. See IFTA assessments when records are missing.
Checking your system
- Interval: confirm the system logs a position at least every 10 minutes while the engine is on, not every 15 minutes or only at events.
- Precision: open an export and check that latitude and longitude carry four decimal places.
- Odometer: confirm each reading carries the ECM odometer. If a vehicle has none, record a beginning and ending dashboard odometer or hubodometer reading for each trip.
- Export: pull the raw readings each quarter as CSV, XLSX or delimited text, by vehicle, and store them where you control them.
- Reconcile: compare GPS distance with odometer distance for each vehicle and explain gaps (repairs, device outages, personal conveyance) in your records.
- Keep: hold the files four years from the later of each return's due date or filing date (P510). Illinois puts it in capitals: keep all fuel and distance electronic data for each qualified vehicle for four years.
This page is general information about the IFTA rules, not legal or tax advice; your base jurisdiction's law and audit practice also apply.
Questions filers ask
Is there an IFTA-certified ELD?
No. IFTA does not certify devices, and the Texas DMV warns there is no such thing as an IFTA- or IRP-certified ELD. What matters is whether the data you keep meets P540.200.
Do I have to use GPS for IFTA?
No. Trip sheets and other records that contain the seven P540.100 elements are accepted. P540.200 applies only if your distance records come from a vehicle-tracking system.
Can I give the auditor my ELD provider's PDF mileage report?
Not as your only record. P540.200 says static formats such as PDF, JPEG, PNG or Word are not acceptable; the readings must be available in a spreadsheet format.
How often must GPS record a location for IFTA?
At least every 10 minutes while the engine is on, under P540.200, in force since January 1, 2024. IRP's rule is every 15 minutes.
My GPS data for one quarter is gone. Can I use routing software miles?
Routing miles alone are weak evidence; Idaho's handbook warns not to rely only on map or computer distances. Rebuild what you can from odometer readings, fuel receipts, bills of lading and dispatch records. If the fleet's records as a whole are inadequate, P570 applies.
How long do I keep GPS data?
Four years from the later of the return's due date or filing date (P510), the same as other IFTA records. Do not rely on a vendor's storage period.