Trip sheet and settlement software holds the trip as a record from the moment it opens to the moment it closes: vehicle, driver, route, the advances issued against it, the diesel, tolls and expenses incurred on the road, the consignments it carried, and the settlement that squares the driver and ends the trip. With Pentoggle, an operator can describe how trips actually run and settle and generate the starting application around it.
The trip is a useful operational cost object in a transport business. A large share of variable operating spend can be attributed to a trip, while fixed and fleet-level costs have to be allocated separately. Much of that trip spend goes as cash or transfer to a driver who is somewhere on a highway. Whether that money is accounted for depends entirely on a record that is created away from the office.
Many operators already run Tally for accounting and a GPS or telematics provider for vehicle data. Those stay where they are. What is often still managed outside them is the trip itself: what was advanced, what was spent, what is supported by a bill, and whether the driver has been squared up.
Key takeaways
- The trip has two endings. Physical completion is when the planned movement is completed and the vehicle is released for its next assignment. Commercial closure is when the settlement is done, and the gap between them is where money sits unaccounted.
- Advances arrive from several people through several channels, so the total is frequently not known by any one person until settlement forces the question.
- Expenses recorded on the road are usable. Expenses reconstructed in the office days later have lost the detail that made them checkable.
- A trip carries consignments, and charges that arise during the trip may need to be attributed to the relevant consignment to be billed, where the customer's contract permits recovery. Where the two records are separate, that transfer depends on somebody remembering.
- A useful number is trips completed but not settled, with the age of the oldest.
The spreadsheet is often not the problem
A trip register and a diary of advances is a working system, and for a small fleet with one person handling both it is a good one.
The trouble starts at identifiable points.
When advances come from more than one place
The office transfers one amount, the branch sends another, the owner hands over cash at a stop. Three entries in three places, and the driver knows the total better than the office does.
When the record is made after the trip
The driver returns and reports what he spent. The office writes it down. Both are working from memory about events spread across five days and several hundred kilometres.
When settlement waits
Trips complete faster than they settle. A handful of unsettled trips may be normal. A larger backlog represents outstanding advances, unreconciled expenses or other amounts that need to be quantified.
When trip costs and consignment charges are separate records
Detention at an unloading point is a trip fact. Billing it is a consignment action. Where the two live in different registers, the charge is billed only if somebody carries it across.
What trip sheet software holds
Trip header
Trip number, vehicle, driver, route, opening date and expected duration.
Consignments on the trip
The LRs loaded, their consignors and consignees, and the delivery points on the route.
Advances
Every advance with date, amount, mode, who issued it and where, building a running total for the trip.
Expenses
Diesel, tolls, loading and unloading, driver allowance, parking, repairs on the road and other expenses, each with amount, place and time.
Supporting bills
Photographs or scans attached to expenses where a bill exists, and a marker where one does not.
Odometer and distance
Start and end readings, and distance run loaded and empty.
Events on the trip
Detention, halts, breakdowns and deviations, with times, so charges and delays can be substantiated later.
Settlement
Advances against recorded expenses and approved allowances, with the resulting balance shown as recoverable from or payable to the driver, subject to the operator's settlement policy.
A trip has two endings
Operators generally track when a vehicle returns. Fewer track when the trip closes, and the difference matters more than it appears.
Physical completion is visible. The planned movement is complete, the vehicle is released for its next assignment, and the operations desk moves on.
Commercial closure is a separate event. The advances have been totalled, the expenses reviewed, any unsupported or disputed items handled according to the operator's settlement policy, the balance recovered or paid, and the trip marked closed. Until that happens, the trip's final cost and any unsettled driver balance remain unresolved, which can leave working capital tied up in advances or unreconciled amounts.
The gap between the two is where several problems accumulate at once. Money advanced against the trip is still outstanding. The final cost of the trip cannot be reported reliably from the settlement record, so vehicle-level profitability for the period may remain incomplete or provisional. The driver may be carrying an unsettled balance into his next trip, compounding the position. And charges that arose on the trip and were never recorded are becoming harder to reconstruct with every passing day.
None of this is visible if the only status a trip has is complete or not complete. Giving a trip an explicit closed state, with a date, makes the gap measurable and therefore manageable. The list that matters is short: trips completed but not settled, sorted by age.
Operations producing this list for the first time frequently find more on it than expected, and find the oldest items older than anyone would have guessed.
Advances are the hardest part to get right
The mechanics of an advance are simple and the record-keeping is where it fails.
A driver takes an amount before departure. On the road he asks for more, and it is sent by transfer or handed over at a stop by whoever is nearest. He may still be carrying an unsettled balance from a previous trip. Each of these is a legitimate transaction and each is entered, if at all, by a different person in a different place.
Three design decisions make the difference.
Every advance is entered by the person who issued it, at the time they issue it. This is the behaviour change that most of the rest depends on, and it works only if entry takes seconds on a phone. An advance recorded later by somebody else is an advance that may not be recorded.
Advances belong to the driver as well as to the trip. An unsettled balance carried forward from a previous trip is not a trip expense, and treating it as one distorts the trip cost. Holding the driver's running account separately, with trips drawing against it, keeps both figures honest. This is covered further in Driver Management Software.
The route's normal requirement is knowable. What a given route has typically needed in diesel and expenses is in your own history. An advance well above that is worth a question while the trip is running rather than at settlement, when the money is already spent.
The purpose of all three is not to police drivers. It is that a settlement conducted from a complete record is quick and uncontentious, while one conducted from two partial memories is neither.
Expenses have to be recorded where they happen
An expense entered at the pump, at the toll plaza or at the loading point carries information that the same expense entered three days later does not.
It has a time and a place. It can have a photograph of the bill attached. It sits next to the odometer reading that makes the diesel figure meaningful. And it is recorded while the driver still remembers which of the day's several payments it was.
Reconstructed in the office, the same expense is an amount and a category. It cannot be checked against anything, and both parties know it.
Two practical points decide whether road-side entry actually happens.
The first is that entry has to take seconds. A driver at a fuel pump with the engine running will photograph a bill and type an amount. He will not complete a form. Anything beyond amount, category and photograph should be optional or derived.
The second is that unsupported expenses need a policy rather than a negotiation. Some operational expenses may not produce a formal bill. The operator can define an internal settlement policy for which expenses may be accepted without supporting documentation and what amount or evidence is required for settlement. Set in advance, it is also fairer, because it applies to everyone equally rather than depending on who is settling or how an individual case is handled.
Where diesel is concerned, the odometer reading matters alongside the fuel quantity, because the distance between readings and the fuel consumed are what allow mileage to be calculated. This is the same field the fuel page depends on and it is worth capturing once, at the pump, for both purposes. See Fuel Management Software.
The trip carries consignments and charges travel between them
A trip is a cost object and a consignment is a revenue object, and the two are linked but not identical. One trip may carry several consignments for several customers. One customer's consignment may travel across two trips.
The link matters for a specific commercial reason. Charges that arise during a trip frequently belong to a consignment for billing purposes.
Detention at an unloading point arises on the trip and may be billable to the customer whose consignment was being unloaded, depending on the agreed free time and contract terms. A second delivery point added on the way arises on the trip and may be billable to whoever asked for it, again subject to the agreed terms. Extra loading or unloading labour, a diverted route at a customer's request, a wait at a plant gate: all of these are trip events with a consignment owner.
Where trip records and consignment records are separate systems, these charges reach the invoice only when a person notices and carries them across. That person is usually busy, the charge is usually small, and the failure is invisible because you cannot see an invoice line that was never raised.
Holding the consignments against the trip, and allowing an event recorded on the trip to be attributed to one of them, closes that gap at the point the event is recorded rather than at the point somebody remembers. The consignment side of this is covered in LR and Consignment Note Software.
Where trip settlement looks different by business type
- Transport Contractor and Fleet Owner Software, where trip settlement is the daily operational rhythm of the business.
- Truck Fleet Management Software, where trips run several days and settlement covers the whole run rather than each day.
- Bulk and Tanker Transport Software, where the trip record also carries loaded and delivered quantity.
- Container Transporter and CFS Software, where trips are short and the gate timings on them carry commercial weight.
- City Distribution Software, where the equivalent is a route-day reconciled at the depot each evening.
- Tempo and Small Commercial Vehicle Software, where the owner is frequently the driver and settlement is a personal accounting question.
Why operators choose Pentoggle for trip settlement
Advances entered at the point of issue
By whoever issues them, on a phone, in seconds, so the trip total is current rather than assembled later.
Expenses captured on the road
Amount, place, time and a photograph of the bill, entered while the driver is still there.
Trip and driver balances held apart
Balances carried forward do not distort trip cost, and both figures stay honest.
Consignments linked to the trip
Charges arising on the trip can be attributed to the consignment that should carry them.
Sits around your accounting
Tally and comparable systems continue handling accounting, invoicing and GST. Pentoggle adds the operational layer around trips, advances, expenses and settlement.
A useful number for trip settlement
Trips completed but not settled, with the age of the oldest.
The count tells you the size of the backlog. The age tells you whether it is a queue that clears or a set of trips that are quietly never going to be settled properly, which are different problems.
Watch the age rather than the count over time. A steady count with a low maximum age is a working process. A steady count where the oldest item keeps getting older means new trips are settling while a residue accumulates, and that residue is where amounts at risk of becoming difficult to recover or reconcile can accumulate.
Read it alongside total advance outstanding by driver. The two move together, and when they diverge it is informative: rising advances with stable unsettled trips usually means advances are being issued more freely rather than settled less often.
Ready to build trip sheet software?
You know which vehicles came back this week.
Whether the trips they ran have actually been closed is a different list, and it may be longer than you expect.
Describe how your trips open, what gets advanced and how you settle to Pentoggle in plain English and generate a working first version in hours, then refine it around your process.