The invoice says 176 hours. Your site log says the excavator sat idle from Tuesday through Thursday. The rental company’s telematics says it ran eight hours a day, every day. Somebody is wrong, and proving it costs three phone calls, a spreadsheet you shouldn’t have to build, and a credit that probably wasn’t owed.
This happens because hour meter data lives in systems that were never designed to agree with each other. The rental company tracks utilization in their telematics platform. You track it in project records, timesheets, or an ERP that knows the asset exists but has no idea whether it ran. The invoice pulls from a third source entirely, and reconciliation happens only when one side calls to dispute the charge.
The machine reports hours to the OEM or aftermarket telematics device installed on it. That feed goes to the rental company’s system. At the end of the billing period, someone exports a report, checks the contract terms, and generates the invoice. You receive the invoice. You compare it against... what, exactly?
If you have your own telematics on mixed fleet equipment, you might see your owned machines. You won’t see the rented ones unless the rental company gave you portal access, and even then you’re logging into their system to verify a number they already sent you. If the rental contract includes telematics as a line item, you’re paying twice: once for the device, again for the dispute cycle it creates.
| Where it lives | Who sees it | When you find out it’s wrong |
|---|---|---|
| Rental company telematics | The rental company, maybe you if they granted access | When the invoice arrives and the number doesn’t match your records |
| Your internal records | Your project managers and controllers | When the invoice arrives and the number doesn’t match the portal |
| The invoice | Accounts payable | After AP has already queued it for payment |
The problem is not that one system is better than another. The problem is that reconciliation is a monthly exception process instead of a continuous shared record.
Start with the time. Your controller pulls the invoice, checks it against job costing records or a site supervisor’s log, finds a discrepancy, and emails the rental company. The rental company’s billing team pulls the telematics report, screenshots the portal, and sends it back. You forward it to the site. The site superintendent says the machine was down. Three people have now spent an hour on a billing question that should have taken ten seconds.
Then the goodwill cost. Rental relationships are built on repeated transactions and trust. A monthly dispute cycle signals that someone’s data is wrong, someone’s billing process is sloppy, or someone is trying to get paid for hours that didn’t happen. None of those is usually true, but the dispute creates the question anyway.
The financial cost is harder to see, because most of the time you pay the invoice and move on. Contesting a $400 discrepancy on a $12,000 rental bill might not be worth the cycle time. That calculation is correct for one invoice. Applied across 15 rented machines over six months, the uncontested errors add up faster than the hours you actually caught.
Disputes end when both sides see the same number at the same time, from the same source. That means the utilization data feeding the invoice has to be the same data you see when you check your fleet. Not a screenshot sent after the fact. Not a login to their portal that you remember to check once the bill is already wrong. The same record, visible to both parties, tied to the asset and the contract.
This requires three things. First, the rental company’s telematics data has to flow somewhere you can see it alongside your owned equipment. Second, that data has to tie to the rental contract so the billing terms and the utilization record sit in the same place. Third, the rental company has to give you that visibility as part of the relationship, not as a favor you have to ask for every time a number looks wrong.
Some rental companies now offer customer-facing dashboards that show both what you rent from them and what you own. When the same platform tracks owned and rented assets together, the hour count on the rented excavator sits right next to the hour count on the excavator you own. The rental company can still see it. You can see it. When the invoice generates, there is no surprise, because the number has been visible the entire billing period.
For contractors running mixed fleets where rented equipment moves between jobs, this also solves the job costing problem. You know which rented machine ran how many hours on which project without waiting for the invoice to tell you. That number flows into your costing model in real time, not 30 days later when the bill arrives and the project has already moved to the next phase.
Incus5 unifies owned and rented equipment in one view, and rental companies using it can extend that visibility to their customers. The same data that generates the invoice is the data the customer sees. When both sides are looking at the same utilization record, the dispute never starts.
You can keep reconciling invoices against internal records that were never designed to match. You can keep calling the rental company to ask for screenshots. You can keep paying for telematics on rented equipment and still not seeing the data until the billing dispute forces someone to pull it.
Or you can ask the rental company whether they offer shared visibility. Not portal access you have to remember to use. A unified view where your owned machines and their rented machines show up on the same screen, with the same utilization data that drives their invoice. If they do, the dispute cycle ends. If they don’t, the question is whether the relationship is worth the monthly reconciliation cost.
The machine’s hour meter doesn’t lie. The telematics feed doesn’t lie. The invoice process doesn’t lie. They just never agreed on the same number at the same time, and by the time the dispute starts, it’s too late to fix it without work nobody should have to do.
Why do rental billing disputes happen if the telematics data is accurate?
The telematics data is usually accurate. The dispute happens because that data sits in the rental company’s system, your records sit in a different system, and the invoice pulls from a third source. By the time you compare the numbers, the billing period is over and reconciliation is a manual process. Nobody is lying; the systems just never talked to each other.
Can I just get access to the rental company’s telematics portal to check hours myself?
You can ask, and some rental companies will grant it. The problem is you still have to remember to log in, export the data, and compare it against your own records before the invoice arrives. That’s better than disputing after the fact, but it’s still manual reconciliation. A shared view where both parties see the same data eliminates the reconciliation step entirely.
What happens if the rental company’s telematics shows hours but the machine was actually idle?
If the machine reported hours to the telematics device, something ran. It might have been idling with the engine on, or a hydraulic system running without the machine moving. The telematics tracks what the engine did, not what the operator intended. The dispute is usually about whether that qualifies as billable time under the contract terms, not whether the data is real.
How does a shared utilization record prevent disputes if the contract terms are still unclear?
It doesn’t prevent contract disputes; it prevents data disputes. If both sides see the same hour count in real time, the argument is never about whether the machine ran 176 hours or 160. It’s about whether idling counts as utilization, and that conversation happens once when you write the contract, not every month when the invoice arrives. Shared data makes the terms enforceable without reconciliation.
Schedule a demo with your data and see how Incus5 tracks all five utilization metrics across your entire fleet.