Transportation ERP Consultant, India

From booking to freight bill: the Indian trip cycle

A typical trip for an Indian fleet owner begins with a booking from a consignor or a contract customer, sometimes through a branch, sometimes through a broker. A vehicle is placed and loaded, and the lorry receipt (LR, also called a bilty or consignment note) is issued. The truck travels with the goods invoice and e-way bill, unloads, and the POD comes back, often late and on paper. Only then is the freight bill raised, and payment follows on the customer's credit terms.

Along the way, money goes out constantly: an advance to the driver, diesel at a pump on credit, FASTag deductions, loading and unloading charges, parking and other incidentals, and detention when a customer holds the vehicle. If these are written in a trip book and entered in Tally weeks later as totals, profit per trip cannot be known.

I map this cycle branch by branch, then define one trip record that carries the LR, vehicle, driver, costs and freight bill. This is separate from ERP for Indian forwarders, customs brokers and 3PLs, who mostly book other people's trucks. The general fleet model is on my transportation ERP page.

Own trucks and market vehicles on the same trip book

Growing Indian transport companies typically run a mix: their own trucks, attached vehicles from other owners, and market vehicles hired for a single trip through a broker or directly. The customer sees one service, but the economics are completely different. On an own truck the business carries diesel, driver, tires, EMI and maintenance. On a market vehicle it pays a lorry hire, usually an advance at loading and the balance after POD, less any deductions for shortage, damage or delay.

If the system cannot separate these, the owner cannot tell whether the fleet is earning or the brokerage margin is carrying it. I design each trip to record who supplied the vehicle, the customer freight and the hire cost, and to track the market vehicle balance as a payable that clears only when the POD is received. Broker commissions are recorded separately from hire.

Payments to transporters and market vehicle owners also raise TDS questions, where the treatment can depend on declarations and on the size of the owner's fleet. Your CA should confirm the rules; the ERP should hold the documents and apply the agreed treatment vendor by vendor.

GST on goods transport and e-way bills

GST on road freight in India depends on who provides the service and who receives it. A goods transport agency that issues a consignment note may charge GST under forward charge, or the tax may be paid by certain recipients under reverse charge, depending on the options chosen and the type of recipient. Hiring out a vehicle without issuing a consignment note can be treated differently again. These choices affect the freight bill format, the tax codes and how customers account for your invoices.

I do not decide the treatment. I list your customer types and service patterns and ask your CA to confirm each, then configure the ERP so the customer and service carry the right treatment and the freight bill shows the required declarations. Whether e-invoicing applies to your business should also be checked with your CA.

E-way bills are usually generated by the consignor or recipient, with the transporter updating vehicle details, especially when goods move to another vehicle mid-route or are transshipped at a branch. The ERP should store the e-way bill number against the LR and trip, and flag trips where the vehicle number has changed, so the update is not forgotten on the road.

Diesel, FASTag, tires and driver advances

Diesel is the largest variable cost for most Indian fleets, and it leaks in small ways: fills at a pump on credit that are not matched to a trip, cash fills on the road without bills, and consumption that drifts above the route standard with nobody noticing. I design diesel capture from pump statements, fuel card data and approved cash bills, each tied to a vehicle and trip, with an expected average per route and vehicle type so exceptions are reviewed every week.

FASTag statements show toll deductions by vehicle and plaza. Matched to trip dates, they confirm the route taken and become a trip cost, which also helps when customers question detention or route charges.

Tires deserve their own record. Tracking each tire by serial number through fitment, rotation, retreading and scrap, with the vehicle and kilometers at each step, shows which brands and which drivers get the best life. Driver advances need the same discipline: an advance against a trip, settled with bills at trip close, with open balances per driver visible to the branch and head office.

Moving from Tally and choosing a platform

Indian transport businesses often keep accounts in Tally, with separate transport software for LRs and trips, or with trip data in spreadsheets. A move can go several ways: a transport ERP with accounting included, a general ERP with trip functions added, or a transport application connected to Tally while the accounts stay where the CA is comfortable.

I run selection with scripted Indian scenarios: a full truckload trip with an advance and diesel on credit, a market vehicle hired through a broker with a shortage deduction, a freight bill under the GST treatment your CA has confirmed, and a tire replaced mid-trip. Vendors demonstrate those, including the driver or branch mobile app, and your team scores them.

Migration covers vehicles and their documents (RC, insurance, permit, fitness and PUC expiry), parties, open LRs, unpaid freight bills and open advances. It is planned within data migration and coordinate testing remotely through video sessions. For wider Indian ERP context, see my India ERP consulting page and the India hub.