Understand what an ELD file is
An Electronic Logging Device file is a structured transfer file containing driver, carrier, vehicle, duty-status, certification, diagnostic, and related event information. Regulators define the expected shape so records can be reviewed outside the original device or system.
This application builds files from the data you recorded or imported. It cannot invent missing certified-device events, engine data, authentication events, carrier details, or driver licence data. A successful export means the local preflight checks passed; it does not mean a regulator or roadside officer has accepted the file.
Prepare required data before export
- Create the driver profile with name, licence jurisdiction, and licence number where required.
- Create or confirm the active carrier profile for the export date.
- Add at least one Daily Log and at least one active ELD event for the driver.
- Confirm truck and trailer identity details when they are part of the record.
- Review annotations, locations, dates, times, timezones, and certification events.
- Driver licence numbers are encrypted at rest and normally shown only in masked form.
- The full licence value is used server-side only where the ELD filename convention requires licence digits.
- Missing mandatory profile or event data blocks export instead of creating a misleading file.
Export Canadian or U.S. files
Canadian ELD export follows the Canadian ELD Technical Standard 1.3 profile used by the module, including Canadian event extensions and checksum handling. U.S. FMCSA export uses a separate U.S. profile and does not simply rename the Canadian file.
- Open the Road ELD export page or the export controls from My Road Entries.
- Choose Canadian ELD (CCMTA/Transport Canada) or U.S. FMCSA ELD.
- Select the driver and date range if requested.
- Resolve any preflight warnings.
- Generate the file and inspect it before sharing it with a carrier, auditor, or authority.
Import data
ELD import stages rows before committing them. The preview identifies new rows, duplicates, and invalid rows so re-uploading the same file does not create duplicate events.
Committing an import only inserts new events. It does not overwrite existing events. Corrections after import still use the event correction workflow.
- Open Import Data from the Road entry workflow.
- Upload a supported Canadian or U.S. ELD file.
- Review the preview states and errors.
- Commit only the rows you want to add.
- Open the affected Daily Log and verify the event timeline.
If something goes wrong
- If export is blocked, complete the listed driver, licence, carrier, truck, or event data first.
- If import shows duplicates, those rows already match events in the logbook and can be skipped.
- If a third-party file does not parse, confirm the format; ELD providers vary and not every vendor file is guaranteed to match the supported parser.