Car Hauler Load File Checklist for Billing

A load can deliver cleanly and still turn into a billing problem if the paperwork is scattered across a dispatch inbox, a driver’s phone, a fuel-card portal, and someone’s desk. By the time a broker questions detention, a customer disputes damage, or accounting needs payment support, nobody’s sure which version is final.

Use this car hauler load file checklist to build one file per load. Organize it by workflow stage: booking, dispatch, pickup, transit, delivery, billing, and dispute follow-up. The goal isn’t paperwork for its own sake. It’s one handoff standard for dispatch, drivers, and billing before an invoice is submitted or a payment dispute is escalated.

1. Booking file: prove what you agreed to haul

Start the load file before the truck is assigned. If the rate, scope, or paying party changes later, the original booking record gives you something to compare against.

• Rate confirmation, shipper or broker name, and contact information
• Pickup and delivery locations, appointment windows, and load number
• Vehicle count, VINs or stock numbers when available, and special handling instructions
• Agreed linehaul, fuel or accessorial terms, detention language, and payment instructions
• Broker or customer packet, carrier setup documents, and insurance requirements
• Notes showing who approved rate changes, added units, reconsignment, storage, or other extras
• A verification record for the contracting party when contact information or payment instructions appear unusual

Keep the original rate confirmation and later revisions together. Don’t overwrite the first version. A note such as “rate increased by $150 for added unit, approved by dispatch contact at 2:14 p.m.” can prevent a long email search later.

2. Car hauler load file checklist: connect the load to the truck and driver

The dispatch section should show who was assigned, what equipment was used, and how the trip was planned. FMCSA identifies bills of lading or equivalent origin-and-destination documents, dispatch or trip records, expense receipts, electronic mobile communication records, and payroll or settlement records as categories of supporting documents used to verify records of duty status. (FMCSA↗ (opens in a new tab))

• Dispatch sheet or trip record with driver, unit, trailer, load number, and dates
• Confirmed pickup and delivery appointments
• Route notes, gate instructions, contact names, and facility requirements
• Messages that change timing, routing, vehicle count, or delivery instructions
• HOS and ELD planning notes when appointment feasibility or delay exposure affects the move
• Truck and trailer assignment, including any equipment substitution
• Driver pay or settlement instructions tied to the load

For ELD supporting documents, FMCSA’s current published guidance states that documents should be linkable to the driver or carrier-assigned identification, date, location, and time. The guidance also addresses retention and document-volume requirements. Verify the current rule and your record-retention process before adopting those details as company policy. (FMCSA↗ (opens in a new tab))

3. Pickup file: establish vehicle condition and custody

Pickup paperwork is where a clean load file starts. A signed bill of lading alone may not explain pre-existing damage, missing keys, warning lights, low fuel, or a unit released under exception.

• Pickup bill of lading, gate release, delivery order, or equivalent freight document
• Vehicle condition report for each unit
• Time-stamped pickup photos covering required sides, visible damage, odometer, fuel level, and accessories when relevant
• Keys, remotes, personal-property notes, and missing-equipment comments
• Shipper or yard exception notes and the driver’s written observations
• Pickup arrival, loading, release, and departure times
• Names or signatures of the facility representative and driver when available

Use one naming convention for photos and scans, such as `load-number_VIN_pickup-front_2026-08-10.jpg`. That makes a condition dispute easier to work than a camera roll full of files named IMG_4821.

4. Transit file: capture costs and delays that affect settlement

Transit records support more than mileage. They help explain why the truck missed a window, why an accessorial was incurred, or why the driver’s settlement includes a reimbursable expense.

• Fuel receipts and toll records tied to the trip
• Scale tickets, parking receipts, washout or equipment-service receipts, when applicable
• Detention or delay logs showing arrival, check-in, loading, release, and departure times
• Facility messages, emails, or texts about gate closures, no-load situations, rescheduling, or storage
• Breakdown, roadside, accident, or damage documentation when an incident affects the load
• Updated instructions and written approval for route changes, extra stops, storage, or reconsignment

FMCSA specifically lists expense receipts related to on-duty not-driving time among supporting-document categories. That does not mean every receipt belongs in the customer invoice. Separate load-billable costs from company operating expenses, then send the correct support to billing and payroll. (FMCSA↗ (opens in a new tab))

5. Delivery file: close the chain of custody

Delivery is not complete from a billing standpoint until the file shows what arrived, when it arrived, and whether the consignee accepted it without exception.

If the receiver refuses to sign, record the refusal, identify the person or facility involved, preserve the delivery photos, and notify dispatch or claims staff using the company’s escalation procedure.

6. Billing file: assemble the invoice packet before submission

Billing should receive a packet that answers three questions without a second round of emails: what was hauled, what was agreed, and why the amount invoiced is correct.

• Invoice matching the load number, rate confirmation, customer, and payment terms
• Signed POD or approved electronic delivery record
• Bills of lading, condition reports, and delivery exceptions
• Approved detention, layover, stop-off, storage, re-delivery, or other accessorial documentation
• Receipts or third-party charges that the contract allows you to pass through
• Email or message approval for any rate or scope change
• Payment instructions confirmed against the booking record and the customer’s known contact path
• A final load summary showing the amount invoiced, expected deductions, and outstanding support

The IRS identifies invoices, receipts, paid bills, deposit information, and proof-of-payment documents as examples of supporting business records. It says records should clearly show income and expenses and be kept in an orderly system suited to the business. Use that as a tax-recordkeeping review point, not as a claim that one universal load-file format satisfies every tax situation. (IRS)

7. Payment and settlement file: track what happened after invoicing

A submitted invoice isn’t the closeout. Keep the payment trail with the load so accounting can reconcile the receivable and the operator can explain driver pay or deductions.

FMCSA includes payroll records, settlement sheets, or equivalent documents that indicate what and how a driver was paid among supporting-document categories. Keep settlement support connected to the trip record, while maintaining payroll records in the system and retention process your company uses for employment and contractor records. (FMCSA↗ (opens in a new tab))

8. Dispute follow-up: create a short, dated case file

When payment is short, damage is alleged, or a broker says the POD is unacceptable, stop adding random attachments to the original email chain. Create a dispute subsection with a clear timeline.

If the dispute involves suspicious broker identity, changed payment instructions, or a load brokered under another carrier’s identity, preserve the communications and verify contact information through a trusted channel. FMCSA advises carriers to confirm broker and carrier phone numbers using SAFER and warns that fraudulent documents and contact information can be used in these transactions. (FMCSA↗ (opens in a new tab))

Final load-file review before invoicing

1. The load number, customer, driver, unit, and vehicle count match across the file.
2. The rate confirmation matches the invoice, including approved accessorials.
3. Pickup and delivery records are present for every unit.
4. Condition photos and exception notes are stored where claims staff can find them.
5. Receipts are legible, dated, assigned to the correct load when appropriate, and routed to the correct accounting category.
6. POD is signed or the delivery exception has been documented and escalated.
7. Payment instructions were not changed solely because of an unverified email or text.
8. Billing, dispatch, and payroll have received the records each function needs.
9. The file has an owner and a next action if payment or documentation remains open.

Frequently asked questions

What records should a trucking company keep for each load?

At a minimum, build a file around the booking, dispatch assignment, origin and destination documents, pickup and delivery records, condition evidence, receipts, invoice support, payment trail, and dispute correspondence. The exact retention period and required contents depend on the record and rules that apply to your operation, so separate operational guidance from tax and regulatory review. FMCSA and IRS materials identify different record categories and purposes. (FMCSA↗ (opens in a new tab); IRS)

What documents are needed to invoice a car haul load?

Usually, billing needs the invoice, rate confirmation, signed POD or approved delivery record, relevant bills of lading, accessorial approval, and any receipt or third-party charge required by the customer’s terms. Your broker or shipper may require a specific submission packet, so confirm those terms before invoicing.

Should receipts be stored in the load file or the accounting system?

Use both when the receipt affects more than one workflow. Store or link the receipt in accounting for expense support, and connect it to the load file when it supports a reimbursable charge, detention event, route change, or settlement entry. The IRS says supporting documents should identify details such as the payee, amount, proof of payment, date, and business purpose when needed to support a transaction. (IRS)

Related TruckTA resources

• How to Verify a Broker Before Accepting a Car Haul Load
• A Practical Car-Hauling Dispatch Workflow From Booking to Proof of Delivery
• Car Hauling Vehicle Condition Checklist: Pickup to Delivery SOP
• Car Hauling Accounts Receivable Checklist: From POD to Payment