Most carriers think dead freight billing is not worth it. The dispute costs more than the claim. That is almost never true. It is only true as long as the evidence is missing.
The right to bill has stood for decades. Section 415 of the German Commercial Code covers cancellation by the shipper. The carrier then gets a choice. Either the agreed freight, minus saved costs. Or one third of it as dead freight compensation. Section 412(3) covers demurrage. If the carrier waits beyond the agreed time, through no fault of his own, he earns a fee. Both rules fit the futile trip exactly. Goods not ready. Receiver closed. Wrong address. The law was never the problem.
The problem is one question. Every customer asks it once the invoice lands. How do you know that? The honest answer is usually: we remember.
Here is how a futile trip plays out, the case you later want to cover with dead freight billing. The driver arrives. Something is wrong. He waits. He calls. Eventually he drives on. If it gets logged at all, it happens that evening, from memory. Or three weeks later, when billing spots a gap in revenue. By then, four questions remain. Nobody can answer them with certainty. When exactly did the truck arrive? How long did it wait? Why could it not load? Who reported it, and when?
Miss one of these four answers with a timestamp, and the invoice is a claim, not proof. The customer disputes it. He stands a good chance. Not because he is right. Because the other side has nothing timestamped to show.
That is the same gap as the demurrage dispute at the ramp. There, the fight is about minutes between arrival and unloading start. Here, the question runs deeper. Did loading happen at all? Both cases need the same rule. The evidence forms on the day itself. Not after.
The four sources for proof already exist in most fleets. Just not as one record.
Telematics gives the timeline. Geofence arrival. Standstill duration. Departure without a loading confirmation. Here, this long, then gone.
The driver notice gives the reason. A photo of a closed gate. A reason code through the app: receiver closed, goods not ready, wrong address, contact unreachable. Skip this step, and telematics stays silent. It shows someone arrived and left. Not why.
Order data gives the target state. The agreed time slot. The contact person. The address on the order. Without this baseline, a trip cannot count as futile. It is just a trip.
Customer communication gives the fourth piece. The timestamp of the cancellation. An email where the customer writes that loading cannot happen today. That timestamp is often the strongest evidence in the whole case. It comes from the customer.
Each source alone proves little. Telematics shows only a standstill, meaningless without a reason. The driver notice shows only a claim, worthless without a timestamp. Combined, the four sources build one dead freight record with reason, evidence and a billing line. Only then does the case hold up.
Not every dead freight case gets documented equally well. A review queue sorts by evidence grade. Not by date.
Documented means: all four sources exist. They line up in time. The telematics standstill matches the order time slot. The driver's reason code is present. The customer email confirms the cancellation. This case moves to billing.
Partially documented means: the telematics timeline holds. One piece is missing. The driver logged no reason code. Or the cancellation only happened by phone, with no email. This case needs a follow-up.
Undocumented means: only a claim, no timeline. A late report with no telematics match, for example. This case does not get billed. A plain spreadsheet could never make that call. It only knew one case. Not three evidence grades.
At this point, automation stops on purpose. The record with its evidence grade goes to billing. Not to invoice generation. A system that bills the moment a case is marked documented hands a commercial call to a machine. The machine does not know the customer relationship. Whether a documented case actually gets invoiced. Whether a credit note, a goodwill gesture, or a waiver for the next tender fits better. A person in billing decides that. With the record as basis. Not with automation as the decision-maker.
Dispatch still changes day to day. The driver logs the reason through the app. Instead of trying to remember it after the shift. Billing changes more. It no longer has to reconstruct. It only has to decide. And the customer relationship changes the most. The argument shifts from tone of voice to a timestamp. That ends most disputes before they start. Both sides see the same timeline.
Three honest limits.
Not every driver logs reliably. A reason code takes one tap. The tap has to happen while the driver waits. Not afterward. Miss the log, and the case stays partially documented. No matter how good the telematics is.
Not every cancellation arrives in writing. Many receivers say it at the gate. Not by email. Then the fourth piece is missing. The case rests on three sources instead of four. Often enough. Still weaker.
And the record replaces no judgment about fault or reasonableness. Section 415 requires a risk-area assignment. Section 412 a reasonableness check on waiting time. Both are legal calls. Not data questions. The record supplies the facts. The decision stays with people.
How many futile trips did your fleet run last quarter that never got billed, because the evidence was missing? If you do not know the number, that is the real answer. Tell me which of the four sources you already have, and which one is missing. We will look at the process check for exactly this case.
