Reviewing a flagged document, line by line
A missing-POD flag that page two disproves, and a $10.52 gap that turns out to be one case of freight.
The flag, and the carrier's covering email
The document arrives flagged missing_pod, sitting in a queue of 402. The carrier's covering email is on screen beside it. Start here rather than at the numbers: the email frequently explains the anomaly you are about to spend ten minutes deriving.
The money doesn't match
The extraction totals $536.79. The system holds $526.27 for the same load. A $10.52 gap — small enough to wave through, large enough to be a symptom. The instinct is to blame the fuel surcharge, because a percentage applied to a different base is the usual cause of a small freight discrepancy.
The 40.5% that clears the surcharge
The instinct is wrong here, and it is checkable. Extracted: 382.06 freight + 154.73 fuel = 536.79, and 154.73 / 382.06 = 40.5%. In system: 374.57 freight + 151.70 fuel = 526.27, and 151.70 / 374.57 = 40.5%. Both sides carry fuel at exactly the 40.5% the invoice states. The surcharge is not the disagreement — every cent of the gap is in the freight base.
- Extracted — 382.06 + 154.73 = 536.79
- In system — 374.57 + 151.70 = 526.27
- Both at — 40.5% fuel surcharge — so the surcharge is exonerated.
Freight is billed by weight, so check the weight
The invoice bills 7.87 hundredweight at $48.55 — that is 787 lb. The system holds 750 lb. Thirty-seven pounds light. Now the question has moved from "why is the money different?" to "which weight is right?", which is a question a document can answer.
Page two settles it
The BOL on page two grand-totals 787.04 lb gross across 117 cases — backing the carrier's figure almost exactly. And the extracted piece count of 117 already matches the system exactly. So the pieces agree and the weight does not, which is the signature of an order booked on an estimated weight and delivered at its real one. The document supports 787; the system is carrying the estimate.
And the flag was wrong
The flag said missing_pod. Load Documents already holds the proof of delivery on page two, signature confirmed. The flag fired on an absence that isn't one — worth noting, because a rule that raises hundreds of false flags is itself a finding.
The Validation tab
The second tab compares the document against the TMS order: the PO matches, and the weights are exactly where the disagreement showed up. Two views of the same conflict, which is what gives you the confidence to act on it.
Clear Flag, and what you actually decided
Clearing steps the queue from 402 to 401. But the useful output isn't the counter — it is a documented conclusion: the POD exists, the fuel surcharge is correct on both sides, and the $10.52 is a real freight difference caused by a 37 lb weight variance that the delivered BOL supports. That is a note a carrier can be shown, and it took one screen.
Ready to build your own?
Start free and ship your first app in minutes — or have us set it up with you.
More resources