A driver waits, the system records it, the contract allows a charge, but the invoice goes without one. This is the most common form of revenue loss in logistics and the hardest to see.
You know the scenario: A shipment is delivered after a failed first attempt and a short period of storage. Both events are recorded against the shipment, and both are chargeable under the customer contract.
But the invoice goes out with only the base rate and the fuel surcharge on it, not the redelivery or storage fees. The customer pays without query, because the invoice is lower than it should be. It looks clean. The freight moved, the shipment closed, and the customer was happy.
The only trace of the missing revenue sits in an operational record that nobody compares against the contract. Exception reports are built to catch charges that are wrong. To a system, there is nothing wrong with an invoice that is simply short in a line and looks like a clean operation at face value.
Why unbilled charges survive
Financial controls in Logistics are built around evidence. A wrong rate leaves a variance you can study; a disputed charge leaves a dispute you can research. Each gets investigated because each leaves something behind. An unraised charge leaves nothing behind at all, which is exactly why it survives.
The mechanics behind it are dull. The chargeable event lives in an operational system, whose job is execution. The entitlement lives in a contract, sometimes in a signed PDF on a shared drive. Billing runs from whatever charges were raised. For the accessorial to reach an invoice, someone has to know that this customer, on this service, can be charged for this event, and act on it inside the billing period.
One experienced person carries that across twenty contracts. Nobody carries it across four hundred, with locally negotiated pricing inside global accounts and surcharge tables that move every quarter.
Where the missed charges hide
- Event-driven accessorial charges: waiting time, redelivery attempts, failed collections, out of hours delivery, additional handling for non-conveyable items.
- Storage and demurrage after a free period, where the trigger date sits in operations and the entitlement sits in the contract.
- Dimensional and weight-break rules, where the billable basis differs from the basis recorded against the shipment.
- Minimum charge floors that go unapplied on low-volume lanes and ad hoc movements.
- Supplier service credits and data-breach remedies, which are entitlements the business gives up by default.
- Ad hoc and exception movements handled outside the normal flow, the most likely to be delivered and the least likely to be billed.
Why sampling never finds them…
The usual response is a periodic review. Pull a sample, check it against the contracts, and extrapolate. That will tell you roughly how big the problem is but will not automatically recover anything.
Missed charges are high in frequency and low in individual value, spread thin across every customer and service rather than concentrated anywhere specific. To be confident about one accessorial type on one contract, you would have to check almost all of it.
There is a timing problem on top of that. A review finished after the billing period closes produces findings you can no longer bill. Raising a three-month-old waiting time charge means going back to a customer who considers the transaction finished. Most organizations decide not to, so the loss gets written off in practice without ever being recognized in the accounts.
…and the comparison that does
The storage and the redelivery were both recorded; both were chargeable. Nobody put those two facts side by side, and nothing in the billing process was ever going to.
Closing that gap needs a figure that does not currently exist: the charge the contract implies, worked out from the rate card, the business rules and what the shipment actually did, independently of whatever anyone raised. Set that against the invoice and a missing accessorial shows up as a difference instead of as nothing at all.
Producing that figure once is straightforward enough. Doing it for every shipment means holding activity, contract terms, rate cards and business rules in the same place, and rating the whole population from the contract. No team does that by hand at volume, which is why sampling persists.
Automate it and the charges surface inside the billing period, while adding them to an invoice is still routine. The measurement is worth as much as the recovery. Once an expected figure exists for every shipment, the gap between what was earned and what was billed becomes a number finance can report monthly, trend, and hold someone accountable for.
The cost of the storage and the second delivery attempt is already in the accounts. Both were provided, both consumed resource, and neither produced revenue. Billing them needs no new volume, no new customers and no new capacity.
Where Revenue Protect fits
Revenue Protect is part of IFS.ai Logistics. It brings revenue, cost, activity and contract data into a single layer, then rates every shipment from the contract that governs it, so the charge that should exist gets calculated whether or not anyone thought to raise it.
Four capabilities do the work on the losses described above.
Rating and charge automation calculates expected customer charges from configured contracts, rate cards, business rules and shipment activity, so there is a figure to compare the invoice against.
Revenue capture identifies missed charges, validates surcharges and detects billable activity, then supports recovery. Entitlements surface before the billing period closes rather than in a review three months later.
Unified shipment activity consolidates shipment records, milestones, supplier invoice associations and customer activity, so a charge can be tested against what actually happened on a shipment even when several suppliers and legs are involved.
Customer billing and AR integration prepares validated charges for publication and feeds accounts receivable, shortening the route from earned to invoiced to collected.
Underneath all four, data validation and compliance rules catch the missing and non-compliant records that stop a charge being raised in the first place.
For finance the outcomes are the ones that show up at close: more accurate charge capture, reduced revenue leakage, improved billing accuracy, and cleaner operational and financial data feeding month end. Stop revenue leakage, protect margin, and accelerate cash flow.
Start with your own numbers
Revenue Protect assessments start with a defined population of your own shipments and customer charges, tested against the contracts that govern them. The output is a quantified view of what is leaking and where, which makes the business case run on your numbers instead of an industry average.
SOURCE: Philip Ashton (2026 September 7) The Cost of Unseen Logistics Revenue Leakage. IFS Blog. https://blog.ifs.com/the-cost-of-unseen-logistics-revenue-leakage
