Skip to content

Fleet Toll Expense Tracking That Reaches a Ledger, Not a Dashboard

Toll slips live under a rubber band on a dashboard for three weeks and then become a cost head. KO Fleetz posts tolls, fuel and roadside spend to distinct heads, keeps what is owed to a vendor apart from what has been paid, and publishes the closed runs that still have no expense against them.

The slips are in the cab and the month has already closed

The quickest way to understand a transport office's expense problem is to look inside the cab of a truck that has been out for three weeks. There is a rubber band around a wad of paper on the dash. Toll slips, a weighbridge chit, a fuel bill, a number written in pen for a puncture. That wad is the source document for a cost head that finance will confidently report on.

It arrives when the driver next comes in, which may be after the customer has been invoiced and is certainly after the month the spending belongs to. A clerk keys in whatever is still legible. Whatever faded, whatever the roadside mechanic never wrote down, and whatever slipped out of the rubber band at a dhaba becomes a difference that gets absorbed without anyone deciding to absorb it.

What you end up with is a toll figure and an expense figure that are directionally true and operationally worthless. You can see that tolls cost something last month. You cannot see which corridor, which vehicle or which customer's load paid for them, because the slip was never attached to the run that generated it. The head is real. The attribution never existed.

Heads, payables and the runs that are missing an entry

KO Fleetz keeps expense, payables and payments as three ideas rather than one column called costs. An expense is what was incurred. A payable is what is owed to somebody for it. A payment is money leaving. Holding them apart is precisely what lets you answer whether a toll cost is unpaid, paid, or simply never recorded — three states a single spreadsheet column cannot tell apart.

The management view rolls the heads up: total expense, toll expenses, fuel expenses, each as its own category. That roll-up is only ever as good as what got entered, which is why Trip Planner publishes the list of completed trips with no expense entry against them. Read that list as the honest measure of how much of your monthly spend is still under a rubber band somewhere on the highway.

One thing to be exact about, because the industry is full of the opposite claim. The fuel expense figure here is built from Fuel Entry records — odometer, litres, price per litre, total amount, keyed in per fill. It is a transaction record. Nothing on this page reads a tank, infers consumption from hardware or detects a drop in level. A fuel bill nobody enters is a fuel bill this module cannot see, and it will not pretend to have seen it.

Capabilities

What KO Fleetz toll & expense management gives your team

  • Expense heads that stay separate

    Toll, fuel, hiring and general spend are distinct categories, so the toll figure on the management view is a real head rather than a slice of one pool.

  • Payables against the vendor

    What is owed to a toll operator, a workshop or a supplier is held as an obligation in its own right, before anybody has decided when to settle it.

  • Payments recorded on their own

    Money leaving is a separate entry from the cost being incurred, so an expense that is booked but unpaid never masquerades as one that is closed.

  • No expense entry list

    Completed runs with nothing spent against them are named in Trip Planner, which is the difference between a costing gap and an invisible costing gap.

  • Fuel Entry as a transaction

    Each fill records odometer, quantity, price per litre and total amount, giving a fuel cost line built from a keyed record rather than inferred from a sensor.

  • Expense analysis over time

    Spend by head and by period is charted, so a toll bill climbing on a corridor becomes a question somebody asks rather than a total somebody accepts.

  • Consolidated finance view

    KO Fleetz makes advances, salary, expenses and payables readable in one place, so the office is not opening four registers to answer one question about a month.

  • Spend attributed to the run

    An expense posted against a trip travels with it into lane and booking costing, which is the only way a toll ever becomes a customer's cost.

How it works

How KO Fleetz does it

  1. Step 1: Set your heads

    Decide the categories your business actually argues about — toll, fuel, hiring, general — rather than inheriting a chart of accounts nobody in operations reads.

  2. Step 2: Enter spend against the trip

    Each cost posts to the run that caused it. Fuel goes in as a Fuel Entry with litres and rate; tolls and roadside costs go in as expenses on the same trip.

  3. Step 3: Work the missing-entry list

    Completed runs with no expense against them get chased while the driver is still reachable and the paper is still in the cab rather than in a bin.

  4. Step 4: Reconcile payable to payment

    What is owed is settled and marked settled. Anything sitting long in payables is either a dispute or a forgotten obligation, and both are worth knowing about.

Outcomes

What changes

Toll and fuel counted as categories, not one pool
By head
Closed trips missing an entry are listed, not estimated
Named runs
Payables and payments stay separate facts
Owed vs settled
Fuel cost comes from a keyed transaction
Entered, not inferred

Frequently asked questions

Yes — FASTag is a named integration, so toll transactions can be pulled in and reconciled against the trips that incurred them rather than relying only on a driver keying each slip. Where a vehicle is not on FASTag, or a toll was paid in cash, it is still recorded as a manual expense entry against the run, so the toll figure is complete either way. The value of the feed is that the automatic transactions arrive already attributed to a vehicle and a time — which is exactly what a rubber-banded slip on a dashboard never was.

From Fuel Entry records, keyed one per fill. Each carries the vehicle, the odometer reading, the quantity in litres, the price per litre and the total amount, and rolls up into the fuel head. This is a transaction ledger, not a tank measurement. It tells you what you bought and what you paid for it. It does not tell you what entered the tank or what left it afterwards, and no amount of charting an entered figure will turn it into a measured one.

That page is about capture — the driver, the roadside, the moment money changes hands. This one is the office side of the same rupee: which head it lands in, who it is owed to, whether it has been paid, and what the month's categories genuinely add up to. A fleet that captures well but has no heads ends up with tidy records and no analysis. A fleet with heads and no capture has a clean chart of accounts describing a fiction.

The toll is an expense against the run and the advance is a balance against the driver. Posting the expense draws the advance down, so the same rupee is recorded once as a cost to the business and once as an accounting of the cash you handed over. That mechanism is what makes settlement arithmetic rather than negotiation. It only works if the expense actually gets entered against the trip, which is the whole reason the missing-entry list exists.

KO Fleetz reports what was entered, and the missing-entry list tells you how much to trust it. That pairing is the design. A system showing you a confident total without mentioning that a large share of runs contributed nothing to it would be actively misleading. Treat the list as your data quality measure: as it shrinks, the cost heads become worth deciding from. Until then, read them as a floor rather than a total.

As far as attribution reaches. An expense entered against a run inherits that run's route, vehicle and booking, which is what lets it aggregate up to a lane or an account. An expense keyed straight into a head with no trip on it lands in the monthly total and stops there. Corridor-level toll cost is entirely achievable, and it is a discipline question rather than a software question — the entries have to name a trip.

Find the spend that never reached the office

Take one truck that has been out for a fortnight. We will walk its costs from the cab to a head and show you what fell out on the way.