An invoice you thought was closed comes back to bite you. Three weeks after the drop, the receiver's accounts-payable clerk flags it: came up two pallets short, or no signed receipt on file. The money you already counted gets clawed back as a chargeback, and now it's your job to prove otherwise.
By then the driver has run a couple hundred stops up and down the Loop. He barely remembers the dock, let alone the count on one pallet jack that Tuesday. Your proof, if it exists at all, is a crumpled paper ticket in a truck cab or a photo buried in somebody's camera roll.
The dispute itself isn't the real problem. Disputes happen, and some are honest. The problem is that answering one eats an afternoon of digging, and when you can't put your hands on clean proof, you lose by default and swallow the cost. Fix the capture, and most of these settle themselves before they ever become a fight.
What actually wins a short-pay dispute
A receiver's AP team isn't going to take your driver's word, and honestly they shouldn't have to. What ends the argument is a record that ties the delivery to the order and shows what left the truck.
Four things do the heavy lifting:
- The order it belongs to. The proof has to be filed against the right PO or invoice number, not floating in a folder of loose photos.
- The count. Pallets, cases, or pieces, written down or photographed at the moment of the handoff.
- A timestamp. Date and time the drop happened, generated by the system and not typed in later.
- Who took it. A signature, a printed name, or a texted confirmation from the person on the dock.
Get those four attached to the order and a short-pay claim has almost nothing to stand on. Miss any one of them and you're back to a driver's shrug.
Capture it at the dock, not from memory
The capture has to happen in the thirty seconds the driver is standing there, because nothing gets added accurately after the truck pulls away. Make it so fast the driver has no reason to skip it.
A workable dock routine looks like this:
- Driver pulls up the stop on his phone. The order and the expected count are already on the screen, so he's confirming, not typing.
- He snaps one photo of the staged freight, pallet count visible. Two seconds.
- The receiver signs on the screen, or the driver taps a button that texts a confirmation link to the site contact's phone.
- The app stamps the time and the GPS location automatically. He hits done and rolls to the next stop.
Notice what the driver is not doing: no writing the order number, no emailing a photo to the office, no remembering anything. The one job is point, tap, go. When capture costs almost nothing, it actually happens on every stop instead of just the ones that feel important.
File it to the right order by itself
Here's where most outfits fall down. The photos and signatures exist, but they live in a phone or a shared drive with no link to the invoice, so finding them later is the afternoon of digging you were trying to avoid.
The point of automating this is that the proof attaches to the order without anyone in the office touching it. Because the driver opened the stop from the actual order, the photo, the signature, and the timestamp all get filed against that order number the moment he taps done. No re-keying, no matching photos to invoices by hand on Friday.
This is the part that's genuinely worth setting up carefully, and it's the part a plain camera roll can never do. A photo with no order attached is just a picture of some pallets. A photo filed to invoice 4471 is evidence.
Be honest about the limits, too. The system can force the count field and refuse to close a stop without a photo, but it can't tell you the driver actually loaded the right freight. If he shorts the truck at your own warehouse, clean proof of delivery just documents that you delivered short. Capture settles disputes about what changed hands at the dock. It doesn't replace a good pick-and-load check before the truck leaves your yard.
When the dispute lands, it's one lookup
Now play the chargeback forward. That AP email comes in three weeks later claiming a short delivery. Instead of paging the driver and hoping, whoever handles billing opens the order and there it is: the timestamped photo showing eight pallets staged, the signature from the receiving clerk, the time and location stamp.
You reply once, attach the proof, and the claim is done. No calling a driver who's mid-route on I-10, no reconstructing a day nobody remembers, no writing off eight hundred dollars because proving it wasn't worth the labor.
A quiet bonus: once receivers learn your drops come with a signed count every time, the fishing-expedition short-pays tend to dry up. People stop testing the door they know is locked.
Worth doing this week
You don't need to overhaul dispatch to start. A few concrete steps get most of the protection:
- Pull last quarter's short-pays. Add up what you ate on disputes you couldn't prove. That number is your budget and your motivation.
- Pick the four fields you'll require: order number, count, timestamp, and a signature or texted confirmation. Decide these before you shop for any tool.
- Time your current process. Have a driver capture a delivery the way he does now, then imagine the point-tap-go version. If capture takes more than thirty seconds, it won't stick.
- Run a two-week pilot on one route. Your highest-dispute lane or your most argumentative receiver. Check that the proof actually lands on the right order automatically, not in a photo dump.
- Write the reply template your billing person sends when a chargeback hits, so the answer is copy, attach, done.
Set this up right and the driver's shrug stops being your problem. If you want a hand wiring the dock capture to your order system so it files itself, that's the kind of thing we help Houston delivery outfits put in place. Either way, the goal is the same: when the dispute comes, the answer is already on file.