Plant and tool hire
The hire revenue that never made it onto an invoice.
Hire is billed on rate cards, over long periods, across a lot of accounts. That combination is exactly where revenue goes quiet: a rate agreed three years ago that nobody has revisited, a collection that failed on a Tuesday and was never retried, a trade account ageing while the equipment stays on site.
Rate cards that stopped moving
What LeakIQ detects
- Accounts invoiced the same amount through several contract anniversaries
- The annualised value of each frozen account
- How many anniversaries have passed without a change
- The invoice history behind it, so you can check it yourself
The problem
Long-term hire agreements usually carry an annual increase. It is agreed at the point of sale and then it lives in a contract document, while the invoices come out of the billing system. Nobody owns the handover between the two, so the rate quietly stays where it was. Miss it three years running and you are not 4% light, you are compounding off a stale base on every invoice.
How LeakIQ surfaces it
LeakIQ reads the invoice history for every account and flags the ones that have never changed value. It cannot see your contracts, so it does not claim the uplift was missed. It gives you the shortlist, the annualised value and the anniversary dates, and you check the agreement.
Collections that failed and were never retried
What LeakIQ detects
- Direct debits that failed with no retry queued
- Card payments declined against hire accounts
- The amount at risk on each one
- How long the balance has been sitting
The problem
A failed direct debit does not announce itself. The equipment stays on hire, the customer notices nothing, and the balance ages quietly until someone runs a report. Around 2.9% of UK Direct Debits fail, and roughly 30% of churn is involuntary, customers who wanted to keep paying and whose collection simply did not clear.
How LeakIQ surfaces it
Every failed collection is raised as its own issue with the amount, the customer and the source record from GoCardless or Stripe attached, then routed to an owner with a deadline rather than sitting in a report nobody opens.
Trade accounts ageing past their terms
What LeakIQ detects
- Invoices past their due date and still unpaid
- How many days each balance is overdue
- The outstanding value per account
- Duplicate charges raised against the same account
The problem
Hire runs on trade credit, so there is always a tail of unpaid invoices. The problem is not that they exist, it is that nobody can see which ones have drifted past the point where they usually get paid, and no one person owns chasing them.
How LeakIQ surfaces it
Overdue balances are surfaced with their age and value, prioritised by exposure, and given an owner and a deadline. Anything settled outside the system auto-resolves on the next sync, so the queue stays honest.
Invoices part-paid and left short
What LeakIQ detects
- Invoices where part of the balance was paid and the rest is past due
- How much was paid and how much is still outstanding, per invoice
- The remaining balance at risk on each one
- The source invoice, so the shortfall can be confirmed
The problem
On a trade account, hire invoices often get part-settled rather than paid in full. A customer clears the hire but queries the transport or the damage waiver, pays against an older statement total, or rounds the payment down and means to sort the rest later. The moment money lands the invoice stops looking unpaid, so it drops off the chasing list while a slice of the balance quietly stays outstanding. Nobody owns the gap between paid and unpaid, and the shortfall ages without anyone chasing it.
How LeakIQ surfaces it
LeakIQ compares each invoice total against what has actually been collected and flags the ones that are part-paid and past their due date. Because the customer already engaged and paid something, the remainder is highly collectable, so it hands your team a review list with the amount still outstanding and the source invoice attached, to confirm before chasing.
The same hire invoiced twice
What LeakIQ detects
- The same account invoiced the same amount twice inside a short window
- How far apart the two invoices were raised
- The value billed beyond a single invoice
- Both source invoices, so the duplicate can be confirmed
The problem
A long hire passes through several hands: the hire desk raises the contract, someone bills the off-hire, and a period-end run sweeps up anything still open. It is easy for the same charge to go out twice, once on the contract and once on a manual invoice, or across two overlapping billing runs. Unlike a double payment, a double invoice does not take the customer's money, it overstates what they owe, and a customer who spots a duplicate bill starts querying every invoice you send them.
How LeakIQ surfaces it
LeakIQ flags where the same account was invoiced the same amount twice in a short window and puts both source invoices side by side. It says possible rather than certain, because a genuine repeat hire can look identical in the data, so your team confirms before crediting the duplicate.
Credit notes left sitting against open accounts
What LeakIQ detects
- Accounts holding a credit balance while unpaid invoices sit open
- The value of the credit tied up on each account
- The open invoices that credit could be settling
- The source records for both sides
The problem
Credit notes build up in hire: an off-hire that landed early, a damage waiver reversed, a rate correction, an over-charge put right. The credit gets raised and then it sits, while the same account carries live invoices it could be clearing. Cash is tied up on both sides of the ledger, the credit unspent and the invoice unpaid, and it usually stays that way until the customer remembers the credit and asks for it back.
How LeakIQ surfaces it
LeakIQ surfaces accounts that are holding a credit while open invoices sit against them, with the value on each side. Your team decides whether to apply the credit to the open balance or refund it, rather than leaving it forgotten on the account.
Want to see an example of the free report you'd receive?
The headline figures, then every finding with its amount, the customers affected and the source records behind it.
More sectors
Where revenue leaks in other industries.
Revenue recovery for builders and timber merchants
Trade accounts past terms, stale account pricing, duplicate invoices and unused credit notes.
Read more→Revenue recovery for waste and environmental services
Indexed contracts still billing last year's rate.
Read more→Revenue recovery for facilities, cleaning, security and pest control
Contract rates that never moved while wage costs rose.
Read more→“My team recently started using LeakIQ and found over £49k of leakage across our systems within the first month.”
Free revenue leakage report
See what it finds in your own numbers.
Connect your billing and accounting systems and LeakIQ will show you the frozen rates, the failed collections and the ageing accounts in your own data, each with the underlying record attached so your team can verify before acting.
Read-only. LeakIQ never writes back to your systems and never moves money.