← Back to blog

CDL Supporting Documents in 2026: ELD Receipts, Records, and the 13-Day Rule

Learn which records support a CDL driver's ELD log, when to submit them, what data they need, and how the eight-document and six-month rules work.

Commercial truck driver organizing fuel receipts and trip documents beside a tractor with an electronic logging device

An electronic logging device records duty status, but it is not the only record used to review a driver's workday. Fuel receipts, bills of lading, dispatch messages, trip records, and settlement sheets can show when and where work occurred. Federal rules call these supporting documents because they help verify the log, especially on-duty time that is not driving.

The rule does not require creating a purchase merely to generate a receipt. It requires drivers and carriers to preserve, submit, link, and retain documents that arise in the normal course of business. A reliable workflow protects an accurate ELD log during an audit or roadside review.

What counts as a supporting document

Section 395.11 identifies five categories. The first is a bill of lading, itinerary, schedule, or equivalent record showing the origin and destination of a trip. The second is a dispatch record, trip record, or equivalent document. The third is an expense receipt related to on-duty not-driving time, such as a fuel, repair, lodging, or other work-related receipt when the facts connect it to the duty day.

The fourth category is an electronic mobile communication record sent through a fleet-management system. The fifth is a payroll record, settlement sheet, or equivalent record showing driver payment. These records are not interchangeable with the ELD record. They provide independent points that a carrier or investigator can match against the locations, times, vehicle assignments, and duty-status changes in the log.

Four data elements make the document useful

A supporting document generally needs four elements: a link to the driver, the date, the location, and the time. The driver link may be the driver's name or carrier-assigned ID. A unit number can also work when the carrier can associate that vehicle with the driver. The location should identify the nearest city, town, or village, and the recorded time must be convertible to local time at that location.

There is a limited rule for days with fewer than eight documents containing all four elements. A document with the driver link, date, and location—but no time—can still count toward the supporting-document requirement. That does not make missing information a good practice. When a receipt or electronic record naturally includes all four elements, preserve them so the carrier can match the document efficiently.

Drivers generally have 13 days to submit records

Except for the specified private-motor-carrier-of-passengers nonbusiness situation, a driver must submit supporting documents to the employer within 13 days. The clock runs from either the 24-hour period to which the document relates or the day the driver receives the document, whichever is later. A delayed settlement statement received after the trip therefore uses the later possession date.

Thirteen days is a federal outer deadline, not permission to wait when company policy requires daily uploads. A carrier may reasonably require receipts and trip documents at the end of a shift, load, or tour. Follow the shorter internal deadline, use the approved app or scanning process, and confirm that the upload succeeded. Keep the original until the carrier's procedure says it may be discarded.

The carrier normally retains up to eight per duty day

For an individual driver's 24-hour period, the carrier generally does not have to retain more than eight supporting documents under §395.11. If more than eight exist, the documents with the earliest and latest time indications must be included among the eight retained. This helps preserve the outside points of the workday while limiting unnecessary volume.

Electronic mobile communications are treated differently for the count: the information applicable to one driver's 24-hour period counts as one document. The carrier, not the driver, controls the compliant retention system and selects what must be kept when the file exceeds the limit. Drivers should submit the records they possess instead of trying to choose the final eight themselves.

Toll receipts receive special treatment with paper logs

Section 395.11 separately addresses toll receipts for periods when a driver keeps the paper record of duty status described in the rule. The carrier must retain those toll receipts in addition to the other required supporting documents, and they do not disappear merely because the ordinary eight-document cap has been reached.

A toll record can establish location and timing that is easy to compare with a paper log. Keep the unaltered receipt or electronic toll statement and link it to the correct driver, unit, and day. If the carrier assigns transponders to tractors rather than drivers, its system must still be able to identify who operated the unit during the recorded event.

Carriers keep RODS and supporting documents for six months

Under 49 CFR §395.8(k), a motor carrier must retain each driver's records of duty status and required supporting documents for at least six months from the date of receipt. FMCSA guidance repeats that six-month period. The carrier should store the documents so they can be effectively matched to the corresponding daily log, not as an unsearchable folder of unrelated images.

Drivers have a separate roadside obligation to possess the previous seven consecutive days of duty-status records while on duty. Do not confuse that seven-day driver requirement with the carrier's six-month retention period or the 13-day submission deadline. They address different parts of the compliance chain: immediate log availability, prompt document submission, and longer carrier recordkeeping.

What a driver may be asked to show at roadside

During a roadside inspection, a driver must make available any supporting document already in the driver's possession when an authorized Federal, State, or local official requests it. The driver does not have to convert the record into a different format. A paper receipt may remain paper, and an electronic record may be shown in the format in which it is possessed.

That rule does not require handing over unrelated personal content. Use the carrier's approved business systems and keep work records separated from personal photos, messages, and accounts. Know how to locate the relevant document without editing it, and follow the officer's instructions. The ELD transfer or display remains a separate part of presenting the required duty-status records.

Never alter a receipt to make it match the log

Federal rules prohibit a driver or carrier from obscuring, defacing, destroying, mutilating, or altering existing information in a supporting document. Changing a timestamp, cropping out a location, rewriting a total, or modifying an image to make it agree with an inaccurate log creates a larger compliance problem. The correct response is to preserve the original record and correct the ELD entry through the permitted process when a correction is needed.

An annotation can explain a legitimate difference: a receipt printed in another time zone, a delayed authorization, a co-driver purchase, a unit swap, or a transaction posted after the activity. Explain facts without changing evidence. Notify the safety department early so the log, dispatch record, and document can be reviewed while the trip is still easy to reconstruct.

Use supporting documents to audit your own log

Before certifying a daily ELD record, compare it with the day's work trail. Check the first dispatch message, departure, fuel stop, shipper and receiver activity, repairs, tolls, and final release time. A fuel receipt during an off-duty segment or a delivery timestamp during sleeper-berth time is a signal to investigate—not automatic proof that either record is wrong.

The document shows an event, while the duty-status classification depends on what the driver was doing and whether the driver was relieved from work. For example, buying personal food during a valid off-duty period differs from fueling the commercial vehicle. Use the event to ask the right question, then apply the HOS definition and carrier policy honestly.

A practical daily document routine

At the start of the shift, confirm the ELD login, power unit, trailer, carrier, and shipping-document information. During the day, protect paper records from damage and capture clear images through the approved business system. Check that each image includes the full document and that the driver or unit, date, location, and time can be linked without guessing.

At the end of the day, compare documents with the ELD graph, resolve unidentified driving, enter permitted corrections and annotations, then certify the record. Submit supporting documents under the carrier's process and retain proof of successful transmission when available. Never share another driver's login or attach a receipt to the wrong unit simply because the trip number looks similar.

Build compliance habits before the first dispatch

Federal Part 395 rules primarily govern covered interstate operations, while States and employers may add stricter procedures. During orientation, ask which documents the company collects, when uploads are due, how time zones are handled, who corrects a bad scan, and when originals may be discarded.

CDL Compass Class A and Class B ELDT theory courses introduce hours-of-service and driver responsibilities. Pair that foundation with device-specific ELD training and the carrier's workflow. A clean compliance day is a legal log supported by ordinary business records that tell the same truthful story.

Helpful links and official resources

Start the CDL Compass Class A ELDT theory courseStart the CDL Compass Class B ELDT theory courseReview hours-of-service rules for new driversUnderstand personal conveyance and ELD entries49 CFR §395.11: Supporting documents49 CFR §395.8: Records of duty statusFMCSA: Supporting Documents overviewFMCSA: Required data elementsFMCSA: RODS and document retention