It is the last Saturday of the month and the munshi has three files open. LR_Register_Oct.xlsx, Billing_Final_v3.xlsx and Hisab_Drivers.xlsx. The freight for LR 1187 says one figure in the register and a different one in the bill. The driver says he took a second advance. Tally is waiting, and the CA has asked twice. Nobody is careless here. The same trip simply lives in four places.
Our view: Excel is not the problem for a small transporter; typing the same LR four times is, and that is the point at which transport management software that books the LR once starts to earn its place. Until then, a well-kept sheet is a perfectly sensible way to run a fleet.
An Excel transport register works well up to a point
Plenty of Indian fleets start with a sheet, and they are right to. A lorry receipt format in Excel, a vehicle list, a rate column and a running outstanding column cover the basics. Everyone in the office can open it. Nobody needs training. A good munshi can make it do surprising things with filters and SUMIF.
The sheet also has one quiet strength: it is honest about its limits. When it breaks, you can see where. That is more than can be said for software nobody in the office understands. So we never tell a five-truck owner that Excel is wrong. We tell them to watch for the moment it starts costing more than it saves.
The trouble starts when one LR lives in four sheets
A consignment is not one row. It is an LR, then an e-way bill, then a trip, then a POD, then a bill, then a receipt, then a driver settlement, then a journal entry for the CA. In a spreadsheet office, each of those is typed again by a different person, usually from a photo or a paper copy of the step before.
Every retyping is a chance for the freight, the vehicle number or the date to drift. Nothing links the rows, so nothing flags the drift. The LR register says delivered, the billing sheet never heard about it, and the bill goes out a fortnight late. Our post on the true cost of an unbilled LR covers what that delay does to cash.
The e-way bill is the sharpest case. When the vehicle changes mid-route, Part-B must be updated. A sheet has no clock and no way to remind anyone. It is only as good as the person who remembers to check it.
Re-keying is where the hours and the errors go
Here is an illustrative fleet, not a customer. Say a transporter runs 15 trucks and each truck does 10 trips a month. That is 15 × 10 = 150 LRs a month.
Now count how often each LR is typed by hand: once in the LR register, once in the billing sheet, once in the driver hisab sheet and once into Tally. That is 4 entries per LR, so 150 × 4 = 600 entries a month. If each entry takes 2 minutes to find, check and type, that is 600 × 2 = 1,200 minutes, or 20 hours a month of pure re-keying.
Errors scale the same way. If 1 entry in 50 has a slip, that is 600 ÷ 50 = 12 wrong figures a month. Some are caught at billing. Some surface as a customer dispute. A few reach the books and wait there for the CA. Double the fleet to 30 trucks and every one of those numbers doubles too, while the office headcount usually does not.
A spreadsheet does not lose money. It just lets the same trip be four slightly different trips, and leaves you to find out which one is true.
Picture the other version of that Saturday. The LR is booked once, and the rate master fills the freight. The trip, the bill and the hisab are drafted from it, so the munshi reviews instead of retyping. Each financial document posts its own balanced journal entry when it is saved. The CA gets a Tally export, not a pile of sheets.
Five signs a small fleet has outgrown its spreadsheet
None of these is about fleet size alone. A ten-truck broker with many market vehicles can hit them before a forty-truck fleet with fixed contracts. Use this as a checklist:
- The same LR is typed more than twice. If freight, vehicle and date are keyed into separate files, the re-keying hours above are already yours.
- Bills wait for someone to notice a delivery. If nobody can list delivered but unbilled LRs in a minute, cash is sitting idle.
- E-way bill Part-B and expiry live in someone's head. A vehicle change or a slow route then becomes a check-post problem.
- Driver hisab is settled from memory and WhatsApp scrolls. Advances, diesel and FASTag that are not tied to the trip turn into arguments.
- You learn lane margin from the CA at year-end. A sheet rarely carries the empty return against the loaded trip that caused it.
Two or more of these, and the sheet is no longer the cheap option. It is just the familiar one.
The sheet cannot show which lane loses money
The last sign deserves its own section, because it is the one owners feel most. Lane margin needs the cost of the empty return, the diesel, the tolls and the driver advance spread back across the loaded consignments. In Excel, that means joining a trip sheet to an LR sheet to a fuel sheet by hand, every month, and trusting that the vehicle numbers were typed the same way in all three.
Most offices never do it, which is why the answer arrives at year-end. A system that splits each settlement's cost across its consignments by booking km gives every customer, lane and vehicle a margin you can defend. Our guide to lane profitability for transporters walks through the method, and it works on paper too if you want to test it first.
Excel is free, flexible and everyone knows it
This is the strongest case for staying, and it is a good one. A sheet costs nothing extra. It bends to any odd billing rule a customer insists on. When the office manager leaves, the next one can still open it. Software, by contrast, asks the team to change habits, and a badly chosen system can be slower than the sheet it replaced.
We agree with most of that. Our answer is that the choice is not Excel or software. Keep Excel for what it does well: one-off analysis, a quick what-if on a new lane, a customer's special report. Stop using it as the system of record for LRs, trips, bills and settlements, where linking matters more than flexibility. Good transport software should export to CSV for exactly that reason.
On the accounts side, the same logic applies to Tally. The CA can keep it. Our comparison of Tally and transport software explains why the books and the operations need different tools, joined by an export.
Moving off Excel starts with the masters, not the history
Owners often stall here because they imagine retyping five years of LRs. Nobody should. The order that works is short. First the masters: vehicles, drivers, customers, consignors and consignees, routes and the rate master, brought in from CSV. Then opening balances for customers and vendors. Then new LRs only, from an agreed date.
Old LR sheets stay where they are, as a read-only archive. In SCM for Transporter, every module takes CSV import and export, an import history keeps track of what came in, and automation starts switched off, so the team decides when drafts turn into finished documents.
What to do this week
- Pick one recent LR and count every file it was typed into, from booking to Tally.
- Multiply that count by last month's LRs to see your own re-keying load.
- List delivered but unbilled LRs and note how long it took to find them.
- Clean your vehicle, customer and rate lists in Excel, since they become your masters either way.
- Decide which reports must stay in Excel, so any system you test can export them.
A spreadsheet got your fleet this far, and there is no shame in that. The question now is whether the office spends its Saturdays typing or reviewing. More on running the office behind the trucks is in our guides for transport companies.