Day 1. The email arrives at 08:14. A leasing company is returning 340 laptops from a major bank. The manifest says Dell Latitude 5430. The SLA says 10 business days from receipt to settlement. The contract is clear. The timeline is clear. Nothing about the next 47 days will be clear.

Day 1-3: The Arrival

The truck shows up on schedule. Twelve pallets. Your receiving team starts scanning. Pallet one: Dell Latitude 5430. Good. Pallet two: Dell Latitude 5430. Good. Pallet three: Lenovo ThinkPad T14.

Wait.

Your receiving operator checks the manifest again. Line 1-340: Dell Latitude 5430. There are no ThinkPads on this manifest. But there are ThinkPads on this pallet. Fourteen of them.

Nobody catches this until pallet six, when someone notices the running total doesn't match and starts counting backward. By then, 140 devices have been scanned as Dell Latitude 5430 — including 14 that aren't. The discrepancy has entered the system. It will live there, quietly creating problems, for the next six weeks.

Day 4-8: The Confusion

Your team flags the discrepancy. An email goes to the leasing company: "Manifest says Dell Latitude 5430. We received 14 Lenovo ThinkPad T14 units." The leasing company forwards this to the bank. The bank says they'll investigate. "Investigate" means someone in IT will check a spreadsheet that was last updated when the devices were deployed three years ago.

While the investigation is "in progress," 326 devices sit in your receiving zone, taking up space. They can't move to testing because the discrepancy hasn't been resolved. Or rather, they could move to testing, but nobody is sure whether the 14 ThinkPads should be processed under this contract or held separately. The contract doesn't address this scenario. Nobody's contract addresses this scenario, because nobody plans for the manifest being wrong.

In lease returns, the manifest is the single source of truth. When the manifest is wrong, there is no single source of truth. There is only email.

Day 9-15: The Workaround

Day 9. The leasing company says: process the 326 confirmed Dell Latitudes, hold the 14 ThinkPads. Fair enough. But now your testing queue has 326 devices that need processing, and your SLA clock — which started on Day 1 — is already at 9 days. The 10-day target is tomorrow. You're not going to make it.

Testing begins. The team processes about 40 devices per day. At that rate, 326 devices will take roughly 8 days. The SLA will be missed by a week. Nobody formally resets the SLA clock because the contract doesn't have a clause for "manifest was wrong and we argued about it for a week."

Day 16-25: The Grading Dispute

Devices are being tested and graded. The contract specifies chargebacks for cosmetic damage: €120 for a cracked screen, €60 for a damaged casing, €25 for a missing charger. Your grading team finds 23 devices with what they classify as "cosmetic damage — casing."

The leasing company disagrees. Their definition of "cosmetic damage" and your definition of "cosmetic damage" are... different. They argue that normal wear on the palmrest is not "damage." You argue that a visible crack on the bottom panel is definitely damage. Both of you are right, according to your own internal definitions. The contract says "cosmetic damage" without defining it further.

Eleven emails over four days. A phone call where nobody agrees. A compromise where 15 of the 23 are accepted as chargeable. The other 8 are disputed. The dispute will be "escalated," which means someone higher up will have the same argument in three weeks.

Day 26-35: The Settlement Calculation

Your settlements team starts the calculation. It should be straightforward: take the contract pricing, apply grades, calculate chargebacks, generate the report. But the chargeback calculation requires the grade distribution, and the grade distribution is being done in Excel because your system doesn't connect contracts to grading results automatically.

The Excel sheet has a formula error. Someone used VLOOKUP instead of INDEX/MATCH, and the 14 ThinkPads — which were supposed to be excluded — are included in the totals. The first draft of the settlement is off by €8,400. Nobody notices until the leasing company's analyst spots it. Another round of emails.

Day 36-42: The Correction

The settlement is recalculated. The ThinkPads are excluded. The 8 disputed cosmetic chargebacks are held in a separate line item pending resolution. The report is sent for approval. The leasing company takes five business days to review it, because their approval process involves three departments and a signature from someone who is on holiday.

Day 43-47: The Resolution

Day 43. The settlement is approved, minus the 8 disputed chargebacks (still pending). An invoice is generated. The invoice references the wrong settlement number because of a copy-paste error that will take two more emails to resolve. Day 47: the correct invoice is sent. The SLA was 10 days.

Forty-seven days. Not because anyone was incompetent. Not because anyone was lazy. Because the process had gaps: no manifest verification at scan time, no standardised grading definitions in the contract, no connection between grading results and settlement calculations, no automated discrepancy handling. Each gap added days. Each day added frustration. Each frustration added emails. Each email added cost.

A system that catches the ThinkPad discrepancy at pallet three — not pallet six. That grades against contract-defined criteria, not personal interpretation. That calculates settlements automatically from grading results. That generates the invoice without copy-paste. That system doesn't need 47 days. It needs 10. Which is, coincidentally, what the SLA said all along.

Request a collection

Contact information