The Freight Invoice Packet Checklist: Rate Confirmation, POD, BOL, and Exceptions

A freight invoice packet that gets paid without a phone call contains four things: the signed rate confirmation, the signed bill of lading, the proof of delivery, and documented evidence for every charge that was not on the rate confirmation. Everything else (lumper receipts, scale tickets, detention logs, photos) is supporting evidence attached to one of those four. If a document in your packet does not either establish what was agreed, prove what moved, prove it arrived, or justify a variance, it is not doing work.

Most invoice disputes are not disagreements about money. They are disagreements about which piece of paper is authoritative. This is a checklist for building a packet where that question never comes up.

The four documents and what each one actually proves

Rate confirmation. This is the agreement. It establishes the agreed linehaul, the accessorial schedule, the load number, the stops, and the equipment. When a broker and a carrier disagree about a number, the rate confirmation is the document that decides it. Every other charge on your invoice is either on this document or needs separate proof.

Bill of lading. This proves what was tendered and picked up. It carries the shipper, consignee, commodity description, piece count, weight, and (critically) the signatures at origin. The BOL is also the contract of carriage in most moves, which is why a BOL with terms that contradict the rate confirmation is a real problem and not a paperwork nuisance.

Proof of delivery. This proves it arrived, when, and in what condition. Usually the signed delivery copy of the BOL, sometimes a separate receipt at a facility that runs its own paperwork. The signature and the legible delivery date and time are the parts that matter. A POD with an illegible date is the single most common reason a clean packet still gets held.

Exception documentation. This justifies anything not on the rate confirmation: detention, layover, lumper, TONU, reconsignment, extra stops, driver assist, scale differences. Each of these needs its own evidence trail. This is where most packets fall apart.

The pre-submit checklist

Run this before the packet leaves your hands. It takes a couple of minutes and it is the difference between a 30-day cycle and a 60-day one.

Identity and matching

• Load or pro number appears on the invoice, the rate confirmation, the BOL, and the POD, and they match character for character
• Bill-to party on the invoice matches the bill-to on the rate confirmation (not the shipper, not the consignee, not whoever the driver talked to)
• Carrier name on the invoice matches the carrier name on the rate confirmation exactly, including entity suffix
• Invoice number is unique and does not collide with a prior submission for the same load

The rate confirmation itself

• Signed by both parties, or shows documented acceptance per the agreement
• Linehaul on the invoice equals linehaul on the rate confirmation, or there is an amendment attached
• Fuel surcharge, if separate, is calculated the way the rate confirmation says it is calculated
• Any rate change is a written amendment, not an email thread summarized by memory

BOL

• Signed at origin, with a legible date
• Piece count and weight match what is being billed
• Commodity description is specific enough to be recognizable, not just "freight all kinds" when the move was priced on something narrower
• No terms on the BOL that conflict with the rate confirmation (watch for prepaid/collect markings and third-party billing boxes)

POD

• Signed, with a legible printed name where the signature is not readable
• Delivery date and time are both present and legible
• Marked clean, or the exception is noted on the document itself
• Every stop on a multi-stop load has its own signed receipt

Exceptions and accessorials

• Every charge not on the rate confirmation has a supporting document attached
• Detention shows arrival and departure times from a source the other party can verify (gate records, facility sign-in, tracking data), not just the driver's text message
• Lumper charge has a receipt that shows the facility, the date, and the amount
• Scale tickets attached when weight drives the rate
• Damage or shortage exceptions are noted on the POD at the time of delivery, not added afterward

Format

• One PDF, right-side-up, in a predictable page order
• Legible at normal zoom (phone photos of paperwork are where legibility dies)
• Filename includes the load number

Why exceptions cause most of the pain

The first three documents are largely mechanical. You either have a signed BOL or you do not. Exceptions are different because they involve a claim about time or an event, and time claims need corroboration.

Detention is the clearest case. A detention charge is an assertion that the driver arrived at a specific time, waited, and left at a specific time, and that the waiting exceeded the free time the rate confirmation allows. Three separate things have to be true and provable: the arrival time, the departure time, and the free-time term. If you can only prove one of the three, you do not have a billable charge, you have an opinion. Capture arrival and departure from a source with a timestamp nobody controls after the fact.

The second pattern is the verbal authorization. A dispatcher approves an extra stop or a reconsignment over the phone, the driver does the work, and the charge shows up on the invoice with nothing behind it. Get it in writing the same day, even if the writing is a short confirming email that restates what was agreed and who agreed to it. A same-day written restatement that went unchallenged is far stronger evidence than a memory of a call.

The third is the exception noted after delivery. If damage or a shortage is not on the delivery receipt, adding it later shifts the burden onto you in a way that is hard to recover from. Note it on the document, at the dock, before the driver leaves.

Building it so the checklist runs itself

If you are doing this by hand on every load, the checklist will hold for a few weeks and then erode under volume. A few things make it durable.

Standardize the page order of the packet and never vary it. Rate confirmation, BOL, POD, then exceptions in the order they appear on the invoice. A reviewer who sees the same shape every time reads faster and asks fewer questions.

Make the load number the primary key everywhere, including filenames. Most reconciliation pain is a matching problem wearing a costume.

Capture at the source. A photo taken at the dock, with a legible timestamp, filed against the load number immediately, is worth more than a perfectly organized packet assembled from memory three days later.

Write down what "complete" means for your operation, in one page, and check against it before submitting rather than after a denial. A denial costs you the original work plus the rework plus the cycle time.

FAQ

Is the rate confirmation or the BOL the controlling document? They control different things. The rate confirmation governs price and terms between the broker and the carrier. The BOL governs the transportation of the goods and is typically the contract of carriage. When they conflict on something like billing party or payment terms, that conflict needs to be resolved in writing before the invoice goes out, not argued about afterward.

Do I need a signed rate confirmation if we have a master agreement? Practices vary by relationship and by what the master agreement says. The point is not the signature ritual, it is that both parties have the same written record of the agreed number before the truck moves. If your process depends on an unwritten understanding, it will eventually cost you a load's margin.

What is the most common single cause of a held invoice? In my experience, a mismatch in the identifiers: load number on the invoice that does not match the rate confirmation, or a bill-to that is close but not exactly the contracted entity. It is boring, it is easy to check, and it accounts for a surprising share of delays.

Should the packet be one PDF or separate files? One PDF, unless the party paying you has told you otherwise in writing. If they have a stated format, follow it exactly. Their stated format beats any general advice, including this.

How long should I keep the packet after payment? Longer than you think. Document retention requirements for transportation records are set by regulation and by your own contracts, and they vary, so check the ones that actually apply to your operation rather than picking a number. Storage is cheap and reconstructing a packet during a claim is not.