Lumper Receipt and Accessorial Fraud

How this comes up in practice

A driver submits a lumper receipt two days after delivery. The amount is plausible, but the receipt has no facility name, no printed timestamp, and no load number. The rate confirmation allows reimbursable lumper charges only when the broker approves them before service. The dispatcher remembers a phone call at the dock, but no one saved a written approval. Accounting now has three separate questions: whether the service occurred, whether the receipt belongs to this load, and whether the broker agreed to reimburse it. The receipt image alone cannot answer all three. The file becomes usable when the team adds the appointment record, driver message, facility contact, rate confirmation accessorial language, and any approval note in the order they occurred.

Why accessorial disputes are almost always a documentation problem

Lumper and accessorial charge disputes share a predictable structure: the charge was incurred without the written approval the rate confirmation or broker agreement required, and the question of who owes what is decided by whoever has better documentation. The carrier has a receipt but no prior approval. The broker has a payment terms clause but no authorization record. Neither side can easily resolve it without the document that was never created. For adjacent verification steps, compare this with Broker Non-Payment Checklist, and POD and Delivery Confirmation Risk.

The step that prevents this — written approval before the work is done — takes a few minutes and requires nothing more than a timestamped email or portal message. That document, combined with the receipt, creates a complete record. Without it, the dispute becomes a question of credibility rather than documentation, which is a harder position for either party to defend.

This guide covers the documentation structure of accessorial charges rather than the contractual analysis behind them. Whether a specific charge is enforceable under a particular agreement is a question for whoever reviews freight contracts — the documentation task is making sure the written record exists before the dispute begins.

Documenting accessorial charges before they become disputes

Lumper and accessorial charge disputes share a common origin: a charge incurred without the written approval the rate confirmation or broker agreement required. The rate confirmation may reference detention or lumper as possibilities, but the actual charge needs its own paper trail: written broker approval before the work was done, a receipt with a specific dollar amount, and the date and location of the service.

Drivers who accept lumper or detention charges without documented approval find those charges disputed when invoiced — the prior-written-approval requirement exists because this outcome is predictable. Brokers who receive accessorial charges without prior written authorization have a reasonable basis to dispute them. The documentation habit that prevents this is simpler than the disputes it avoids.

Documents to compare across the transaction

Document review starts by lining up the rate confirmation with the BOL, packet, shipper instructions, lane, commodity, and payment terms. In this guide, that starts with receipts, approvals, timestamps, rate confirmation terms, and billing proof.

The strongest signal is often a change between versions, not the wording of any single PDF. Keep the question practical: what changed, who introduced it, and which dated record can be saved before anyone acts on it.

What the paperwork can show

For lumper receipt and accessorial fraud, the useful record is usually the one that shows where receipts, approvals, timestamps, rate confirmation terms, and billing proof first entered the file.

That record is stronger when it sits beside the dated lookup, the original message, and a note from the dispatcher, billing contact, or document reviewer. It is weaker when it has been renamed, cropped, forwarded without headers, or separated from the transaction timeline.

When the document set should stop moving

Hold the dispatch, release, invoicing, or document-change decision when the file depends on a new contact path, revised document, missing official record, or mismatch that no one has explained.

The pause should be narrow and written down: the field that does not line up, the source used to check it, and the person or channel that must answer before the work continues.

Records to preserve before pickup

Keep original files unedited and preserve revised documents as separate records. In this guide, that starts with receipts, approvals, timestamps, rate confirmation terms, and billing proof.

If a mismatch later matters, the file should show who sent each version, when it arrived, and what instruction changed. Keep the question practical: what changed, who introduced it, and which dated record can be saved before anyone acts on it.

Questions to ask about each document

Document questions should ask who created the instruction and which record supports it. In this guide, that starts with receipts, approvals, timestamps, rate confirmation terms, and billing proof.

The goal is not to debate the PDF; it is to confirm whether the parties, lane, and payment details match the actual shipment. Keep the question practical: what changed, who introduced it, and which dated record can be saved before anyone acts on it.

Mistakes in document review

A signed document can still contain stale or mismatched information. Signatures do not resolve identity or payment conflicts by themselves. In this guide, that starts with receipts, approvals, timestamps, rate confirmation terms, and billing proof.

Treat document conflicts as a reason to verify through a known channel before freight moves or payment instructions are changed. Keep the question practical: what changed, who introduced it, and which dated record can be saved before anyone acts on it.

When a document mismatch requires escalation

Escalate when the document trail no longer identifies the same parties, freight, or payment path. In this guide, that starts with receipts, approvals, timestamps, rate confirmation terms, and billing proof.

Before escalation, save the mismatch plainly so the next reviewer can see the exact field, version, and sender involved. Keep the question practical: what changed, who introduced it, and which dated record can be saved before anyone acts on it.

Source Notes

FAQ