How Does a Company Lose 1.35M Without Anyone Noticing?
The answer, in this case, is devastatingly simple: because nobody was looking. Not the logistics team compiling the billing data. Not the logistics head approving the payments. Not the finance team processing the invoices. The transporter was billing correctly based on what the logistics team was telling them. The logistics team was billing based on what the previous MIS person had done. And the logistics head was approving payments based on trust, not verification.
This is a case study of what happens when three separate teams — logistics, finance, and operations — each assume someone else is verifying the numbers. The result was 5,500 in excess charges every single day, accumulating silently across twelve months, into a 1.35 million loss that nobody inside the company knew existed until a suspicious pattern caught someone's attention.
This is also a case study of recovery — of how a focused audit, a methodical negotiation, and one crucial email that took ten minutes to find became the lever that brought 1.3 million back.
The Suspicion That Started Everything
It didn't begin with a tip or a whistleblower. It began with a pattern that didn't quite add up — logistics payments that were running higher than operations seemed to justify. Nothing dramatic. Just a nagging inconsistency between what the company was physically running and what it was paying for.
The first move was to go to finance — not logistics — and request three months of MIS data directly. That decision, to bypass the logistics team for the initial data pull, turned out to be critical. If the request had gone through logistics, the data might have been reviewed before being shared. Going to finance first meant we got the raw numbers without any prior knowledge of what was coming.
The three months of MIS data arrived from finance. We began the analysis looking for anything that stood out. What we found were exceptions — not one or two, but consistently, across multiple data points, involving one specific transporter.
The company had a formal agreement with this logistics provider: fixed vehicles operating on a daily basis, at a defined rate. The MIS, however, told a different story. The vehicles listed as "fixed" were being classified and billed as ADOC (Ad-hoc / Trip) vehicles — a higher-rate category. And the per-day charge in the MIS didn't match the per-day rate in the agreement at all.
In three months, with just this one transporter, the excess charges came to 300,000. We stopped. Looked at each other. Then requested twelve months of data.
The twelve-month data confirmed the extrapolation. 1.35 million. All from one transporter. All from a billing discrepancy that had been running unchallenged, month after month, through an approval process that wasn't functioning as an approval process at all.
"1.35 million didn't vanish in one transaction. It left in 5,500 increments, every single day, for over a year — because no one was comparing what the agreement said to what the MIS said."
— Mithun GS, PreventLoss.orgWhat the Investigation Found: Three Separate Failures
When we sat down with the logistics team to understand how this had happened, we uncovered not one failure but three — operating independently, each one amplifying the others. The combination created a near-perfect environment for unchecked overbilling to persist indefinitely.
When we asked how the MIS was being compiled, the explanation was straightforward and damning: the current MIS person had inherited the template and the method from the previous person, who had left in 2024. Nobody had ever gone back to the vendor agreement to verify whether the inherited template was accurate. The template had been passed down like a document whose origin nobody questioned anymore — because it had always been done this way.
The previous person had apparently been billing at a different rate or under different conditions — possibly reflecting an older agreement that had since been renegotiated, possibly an error that had never been caught. Either way, the MIS was not built from the current agreement. It was built from the last person's MIS. And the discrepancy — 5,500 per day — had been silently compounding ever since.
This is among the most common and most dangerous process failures in any billing function: inherited templates treated as authoritative. When a new person takes over a billing or MIS process, they should be required to reconcile the template against the source agreement before running a single invoice cycle. In this case, that step never happened — and nobody required it.
Beyond the rate discrepancy, there was a second, independent error embedded in the MIS: the vehicle utilization was being billed at 12 metric tons, but the actual vehicles being deployed were 8 metric ton capacity. This is not a small rounding difference — it's a 50% capacity premium being charged on every vehicle, every day.
The capacity listed in the MIS was not being verified against the vehicles actually operating. The transporter was providing vehicles. The MIS was recording a capacity. And at no point was anyone cross-checking the registered capacity of the vehicles against what the MIS was claiming.
| Data Point | What Agreement Said | What MIS Recorded | Gap |
|---|---|---|---|
| Vehicle type | Fixed daily vehicle | ADOC / Trip vehicle | Wrong category |
| Vehicle capacity | 8 MT (actual need) | 12 MT (billed) | +50% capacity |
| Rate per day | Agreement rate | Agreement rate + 5,500 | 5,500/day excess |
| Cross-verification | Required by process | Never performed | Zero checks |
| MIS source | Current agreement | 2024 predecessor's template | Outdated baseline |
The most jarring moment of the investigation came when we asked the logistics head directly: how were you approving these payments?
This is the control gap that allowed Failures One and Two to persist without discovery. Even with an incorrect template and wrong vehicle capacities, a single approval-stage verification — comparing MIS totals against the rate card in the agreement — would have flagged the discrepancy on month one. The approval process was a signature, not a check.
Who Is Responsible — and How Responsibility Is Distributed
In cases like this, the instinct is to find a single guilty party. The reality is almost always more distributed — and in this case, no fewer than four distinct responsibility layers contributed to the 1.35 million loss.
In this case — as in most internal billing fraud and error cases — the fundamental vulnerability was that the same team managed the vendor relationship, compiled the billing data, and approved the payment. There was no independent verification layer anywhere in that chain. Finance processed what logistics approved. Logistics approved what the MIS showed. The MIS showed what the previous person had done. And nobody checked the agreement.
The Negotiation: A Recovery That Almost Didn't Happen
Armed with twelve months of data showing 1.35 million in excess charges, we initiated a meeting with the transporter. What followed was one of the most instructive negotiations in recent memory — not because it went smoothly, but because it almost collapsed twice before a single email turned it entirely around.
The transporter's opening position was firm: they were not receiving any excess payment. From their perspective, this was true — they had provided vehicles, billed for those vehicles, and been paid the invoiced amount. The concept of "excess" assumed a benchmark they didn't agree with.
We took a break. Regrouped. Came back to the table. The transporter, perhaps sensing he had us on the back foot, handed us his phone and said: "Look at the emails. In January 2024 your team requested 12MT vehicles from me. That's why I gave 12MT. That's what was requested."
He was right about the January 2024 email. Our logistics team had requested 12MT vehicles. The RC matched. The invoice matched the request. We were, again, losing ground. And then someone on our team said: can we search through the other emails?
He agreed. With his phone in hand, we started searching. Ten minutes. Scrolling through months of correspondence. And then — there it was.
August 2024
"We do not need the 12MT vehicle. Please provide us with the 8MT vehicle going forward."
We showed him the email. Read it out. Placed his phone on the table face-up. The transporter went completely silent.
That silence was the moment the recovery became possible.
With the August 2024 email on the table, the transporter's position had fundamentally changed. He could no longer credibly argue that he didn't know 8MT was the requirement. The email was in his inbox. His team had received it. And yet the 12MT billing had continued for months after that communication.
The reversal from 400,000 to 1.3 million happened in a single exchange. The logic was precise: our calculation was actually conservative — we had started from April 2025, not from the August 2024 email that proved his awareness of the 8MT requirement. Pointing out that going back further only increased his liability — from 1.35M toward 2M — made the 1.3M credit note feel like a reasonable resolution from his perspective. He took it immediately.
From a 300,000 anomaly spotted in a three-month data sample, to a twelve-month confirmed loss of 1.35 million, to a negotiated recovery of 1.3 million via credit note — against a transporter doing 6–7 million per month in business with the company. The relationship was preserved. The money came back. And a control system that had never existed now had to be built from scratch.
What Every Business Can Learn From This Case
This case is not unusual. The specific details — logistics vehicles, MIS templates, 8MT vs 12MT — are particular to this industry. But the pattern of failures is absolutely universal: inherited process treated as authoritative, approval without verification, and no independent check between the team managing the vendor and the team processing the payment. Some version of this plays out in procurement, payroll, accounts payable, and operations functions across industries every day.
"The email was sent in August. We started calculating from April. When we pointed out that going back to August made the number larger — not smaller — he agreed to 1.3 million in ten seconds. The documentation didn't just support our case. It ended the argument."
— Mithun GS, PreventLoss.orgControls That Would Have Prevented This — and Should Now Be Standard
Based on the three failure points identified in this case, the following controls should be standard practice in any logistics or vendor payment function. These are not theoretical — they are the specific gaps that allowed 1.35 million to leave unnoticed.
- !MIS-to-Agreement Reconciliation on Role Handover: Any time the MIS or billing role changes hands, a mandatory reconciliation of the current template against the active signed agreement is required before the first billing cycle. The outgoing person and incoming person both sign off on the reconciliation document.
- !Quarterly Independent MIS Audit: Finance or Internal Audit — not the logistics team — conducts a quarterly cross-check of MIS billing data against the signed vendor agreement, focusing on: rate per unit, vehicle category classification, and capacity billed vs. operational records.
- !Three-Way Match Before Payment Release: All logistics invoices above a defined threshold must be matched against three independent sources before payment: (1) signed agreement rate card, (2) MIS billing data, (3) operational evidence — trip logs, GPS records, or vehicle RC for capacity verification.
- ✓Defined Approval Checklist: The payment approval step requires a documented checklist, not just a signature. The approver confirms: rate matches agreement ✓ / vehicle category correct ✓ / capacity verified ✓. No checklist, no approval.
- ✓Separation of Vendor Management and Payment Approval: The team managing the day-to-day vendor relationship does not approve the vendor's invoices. Payment approval for major logistics vendors must involve a separate function — finance, internal audit, or loss prevention.
- ✓Mandatory Written Communication for All Operational Changes: Any change to vehicle specifications, routes, capacity requirements, or rate structures must be confirmed in writing by both parties before implementation. Verbal or phone-based instructions are followed up with an email confirmation within 24 hours.
- ✓Automated Rate Exception Alert: Any MIS entry where the per-unit rate exceeds the agreement rate by more than a defined tolerance (e.g., 2%) triggers an automatic alert to finance for review before the invoice is approved for payment.
- ✓Annual Agreement-to-MIS Full Audit: Once per year, an independent party conducts a full comparison of all active vendor agreements against the MIS templates being used to generate invoices, with findings reported directly to senior management.
Every control listed above costs time — a few hours per quarter for most of them. The total annual cost of implementing all eight controls across a mid-size logistics function is likely 15,000–30,000 in labor hours. The cost of not having them, as this case demonstrates, was 1.35 million in twelve months — from a single transporter. The math is not complicated.
The Bigger Picture: What This Case Tells Us About Vendor Payment Risk
This was not a case of elaborate fraud. No one hacked a system. No fictitious vendors were created. No invoices were forged. The transporter billed for what was provided. The logistics team approved what the MIS showed. The MIS showed what the previous person had done. And the previous person had done it wrong, or had done it under an older agreement, or had made an error that nobody had ever been required to verify.
The 1.35 million loss was the product of compounding negligence — not malice — across multiple roles and processes. And that makes it more common, not less dangerous. Malicious fraud requires intent and planning. Process failure requires only a gap in oversight and enough time for the gap to accumulate into a loss that finally gets noticed.
The recovery of 1.3 million — 96.3% of confirmed losses — happened because of three things: a focused data analysis that didn't accept the logistics team's framing, a negotiation that refused to accept the transporter's opening position, and ten minutes spent searching through emails for documentation that turned the entire conversation around. None of those things required exceptional skill. They required persistence, preparation, and the discipline to follow the paper trail.
If your organization manages significant logistics or vendor payments: pull three months of billing data for your highest-spend vendors and compare it directly to the signed agreement rate cards. Check that the unit rates match. Check that the categories are correct. If you cannot do that comparison in under an hour because the MIS and the agreement are not comparable, that gap is itself a finding worth escalating immediately.
Explore More Loss Prevention & Case Study Guides
Real cases, proven controls, and practical frameworks for US businesses — no sign-up required.
Browse All Articles →