All posts
08-11-2026

8 Hours 80 KM: How Trip Billing Software Stops You Losing Money on Local Packages

The 8 hours 80 km local package looks simple, but the extra hours and kilometres after hour 8 are where most car rental duties quietly lose money. Here is how to bill every rupee you earn.

8 Hours 80 KM: How Trip Billing Software Stops You Losing Money on Local Packages

A customer books a car for a day of city meetings. You quote the 8 hours 80 km package. Simple. Everyone in Mumbai, Delhi and Pune runs on it. The driver finishes at 21:30. The trip actually ran 11 hours and 140 km. On paper you earned the package rate. In your diary, the extra 3 hours and 60 km just disappeared. This is exactly where local bookings leak money, and exactly where trip billing software earns its keep. The 8 hours 80 km model is not the problem. Not measuring what happens after hour 8 is.

Here is how the package really works, and where your margin quietly walks out the door.

What 8 Hours 80 KM Actually Means

The 8 hours 80 km package is a fixed local rate. You give the client a car and driver for up to 8 hours and up to 80 kilometres inside one city. One flat price. Anything beyond that is billed extra.

Two meters run at the same time:

  • The clock. It usually starts when the car leaves your garage, not when it reaches the guest.
  • The odometer. It counts every kilometre from garage to garage.

Cross 8 hours, you charge for extra hours. Cross 80 km, you charge per extra kilometre. In most cities the extra rate sits around ₹150 to ₹250 per hour and ₹12 to ₹18 per kilometre for a Dzire or Etios, higher for an Innova Crysta.

Sounds clean. On a whiteboard it is. In the evening rush it is not.

1. Extra Hours That Never Reach the Invoice

The guest keeps the car till 21:30. The package covered 8 hours from a 09:00 garage-out. That is 12.5 hours on duty. Four and a half hours of overtime.

Your driver mentions it on a call. "Sir, guest late tak ruka, bill mein daal dena." You are juggling three other cars. You forget. The duty slip never gets the hours written down. The invoice goes out at plain package rate.

Every untracked hour is money you earned and then handed back for free.

2. Extra Kilometres That Vanish Between Driver and Diary

The odometer does not lie. Your process does.

Garage-out reading: 45,120. Garage-in reading: 45,290. That is 170 km against an 80 km package. Ninety extra kilometres. At ₹14 a kilometre that is ₹1,260 on a single duty.

But nobody photographs the odometer. The driver gives a round figure from memory. The booking desk writes "approx 80, local only." The extra 90 km is gone before the invoice is even raised.

3. Garage to Garage vs Point to Point

Half your billing fights start here. You bill garage to garage. The corporate client insists on point to point, meaning only the kilometres the guest actually travelled. If your paperwork cannot show the split, you lose the argument every time, and you quietly eat the dead running to and from your garage in Andheri.

Decide the basis before the trip, in writing, or you will negotiate it after the trip, at a loss.

The Real Number

Rajesh runs 22 cars in Andheri, mostly Dzires with three Crystas. He does about 18 local 8 hours 80 km duties a day. On a careful count, each duty loses roughly ₹300 in unbilled hours and kilometres, because the slips are filled from memory at 22:00 when the phone will not stop ringing.

₹300 x 18 duties x 26 working days = ₹1,40,400 a month. Over a year that is close to ₹17 lakh. That is one new car, sitting in the gap between what the meter showed and what the invoice said.

No client was cheating him. He was just not counting.

How Trip Billing Software Closes the Gap

This is the boring part that pays. Good trip billing software does three things a diary cannot:

  • It captures garage-out and garage-in time and odometer readings at the point of the trip, not from memory hours later.
  • It applies the 8 hours 80 km package and auto-calculates extra hours and extra kilometres against your rate card, per vehicle type.
  • It prints the duty on the invoice line by line, so the client sees package plus extras, not a round number they can talk down.

A connected system beats loose tools here. FleetUp links the booking, the vehicle, the driver and the billing in one place, so the extra 3 hours and 60 km stay attached to the duty the moment it closes. You can also just ask it, "How many local duties crossed 80 km yesterday?" and see the leak in seconds. It sits alongside the rest of your car rental software and feeds the same profit per trip view as your outstation work.

Before: package rate, extras lost, margin guessed.

After: package plus every extra hour and kilometre, billed the same day, nothing argued.

Frequently Asked Questions

What does 8 hours 80 km mean in car rental?

It is a local full-day package. The client gets a car and driver for up to 8 hours and up to 80 kilometres within one city for a fixed price. Go past either limit and you bill extra hours and extra kilometres on top, usually counted from the garage-out time and odometer reading.

How do I bill extra hours and kilometres without an argument every time?

Record the garage-out and garage-in time and odometer readings for every duty, ideally with a photo or an app entry, never from memory. Fix garage to garage or point to point in writing before the car moves. When the numbers are captured at source, trip billing software turns them into an invoice line the client can see and trust.

Can one system handle local packages and outstation trips together?

Yes. A proper fleet management software setup runs 8 hours 80 km local packages, outstation per-kilometre trips and monthly corporate duties on the same rate card, so your billing stays consistent whichever way the car goes out.

Count the hours and the kilometres at the gate, not from memory. That is the whole game. The 8 hours 80 km package was never losing you money. Not using trip billing software to catch what comes after hour 8 was.

Helpful? Upvote it. No signup, no email.