Lumper fees: who pays, and how to stop losing the receipts

A lumper fee is a small amount of money that causes an outsized amount of trouble. Two hundred dollars at a grocery warehouse, paid in a hurry, by a driver who is already late, using a code issued over the phone. Multiply by several a week and you have a line item nobody can fully account for at month end.

The three outcomes for the same charge

Before the code is issued, somebody has to decide which of these applies:

Billed to the broker. Most common on loads where the rate confirmation says lumper is reimbursed. The carrier fronts it, invoices it back as an accessorial, attaches the receipt. It should never appear as a driver deduction.

Company absorbs it. The rate didn't cover it, or the confirmation is silent and it isn't worth the fight. Goes to the company's cost of the load.

Charged to the driver. Rare and specific — usually where the driver could have avoided it and chose not to. Needs a reason attached, because this one gets challenged.

The money matters less than the decision being recorded at the moment it happens. Three weeks later, nobody remembers.

Why receipts go missing

The receipt exists for about four minutes. It is a thermal slip handed to a driver who is climbing back into a truck. Then it lives on a dashboard until it is unreadable, or in a wallet until it is in a laundry machine.

The practical fix is a photo, taken at the dock, attached to the load — not emailed, not texted to a dispatcher who will forget. If your system can't accept a photo against a specific load from a phone, you will keep losing them, and you cannot bill back what you can't document. Most brokers will not reimburse a lumper without the receipt, which turns a recoverable cost into an absorbed one.

Billing it back properly

Three things have to line up for a broker to pay:

  1. The rate confirmation allows it. Check before the load, not after. If it is silent, ask in writing and keep the reply.
  2. The receipt is attached to the invoice. Legible, showing the facility, date and amount.
  3. It is invoiced as an accessorial, not buried in the linehaul. Buried charges get short-paid.

Carriers routinely lose real money here, not through fraud but through friction — the charge was legitimate, reimbursable, and simply never made it onto the invoice with its paperwork.

The EFS code problem

Most lumpers are paid with a one-time fuel-card code. That creates a transaction in your fuel card portal that looks exactly like every other transaction: an amount, a date, a location. Nothing in it says "this was a lumper at the Joliet DC on load 4412 and the broker owes us for it."

Unless something connects that code to the load at the time of issue, reconciliation becomes archaeology. Somebody sits with the fuel card statement and the load list and matches by date and geography. It takes hours, it is error-prone, and it is the reason lumper costs are so often wrong in the P&L.

The habit that fixes it costs fifteen seconds: when you issue the code, record the load, the reason, and who is being billed. Everything downstream — the driver's settlement, the customer invoice, the P&L — follows from that one entry.

A rule of thumb

If you cannot answer these three questions about any lumper from last month in under a minute, the process is broken regardless of the software: