LR and consignment note software covers the document that a transport business runs on: booking a consignment, generating the lorry receipt in your own format and series, recording consignor and consignee and goods and freight terms, tracking the copies as they move, attaching charges that arise during transit, holding the POD position, and closing the LR when it has been delivered, documented and billed. With Pentoggle, a transporter can describe how consignments are actually booked and closed and generate the starting application around it.
The LR goes by several names. Lorry receipt, consignment note, GC note, builty or bilty are terms used in different regions and businesses. These documents generally serve similar operational purposes: recording goods accepted for carriage, accompanying or documenting the movement, recording delivery acknowledgement, and supporting the transporter's billing and settlement processes.
Many transporters 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 LR itself: which are open, which have been delivered, which have PODs back, and which are ready to bill.
Key takeaways
- The LR is a document with a lifecycle rather than a form. It is issued, it travels, it is acknowledged, it returns, and it is billed, and the operation needs to know where each one is in that sequence.
- Freight terms help determine who is billed and how the freight is handled downstream, so they belong as a structured field rather than only as text on a form.
- Charges arising during transit have to be attached to the consignment while they are fresh, because an invoice line that was never raised is invisible afterwards.
- LR formats, series and copy structures differ by transporter and frequently by customer, so a fixed template is a poor fit for this document in particular.
- A useful number is open LRs by age, meaning LRs issued and not yet closed.
The spreadsheet is often not the problem
A carbon-copy LR book and a booking register work, and a great many Indian transport businesses run on exactly that with no obvious problem.
The trouble starts at identifiable points.
When you need to know which LRs are open
The register lists what was booked. Which of those have been delivered, which have PODs back, and which are still to be billed requires reading the register alongside two other records.
When the copies scatter
A consignor copy, a consignee copy, a driver copy and an office copy. Once issued, tracking which is where is a matter of asking people.
When charges arise after the LR is written
Detention, an extra delivery point, additional labour. The LR was written at booking and cannot be amended in a book without leaving a mess, so the charge lives in a phone call.
When billing has to assemble the month
The customer's monthly invoice means finding every LR for that customer, applying rates, adding charges and confirming PODs. Done by hand it takes days, and anything undocumented does not get billed.
What LR software holds
Booking
Consignor, consignee, origin and destination, goods description, quantity, weight and any declared value.
LR generation
Your own format, numbering series and branch prefix, with the copies your process requires.
Freight terms
Paid, to-pay, to-be-billed or your own variants, held as a field that drives who is billed and when.
Rate applied
The rate basis and amount from the customer's contract or the spot agreement, held against the consignment.
Trip and vehicle
The trip the consignment travelled on, the vehicle and the driver.
Charges during transit
Detention, extra delivery points, additional labour and other recoverable charges attached to the consignment as they arise.
POD position
Delivered date, receiver, condition, and whether the acknowledged copy has been received back.
LR closure
The LR's required operational and billing steps completed according to the operator's workflow, with delivery, POD and invoicing status recorded separately.
An LR is a lifecycle, not a form
A useful shift in thinking about this document is to stop treating it as paperwork produced at booking and start treating it as an object with states.
An LR is issued. It travels with the goods. It is acknowledged at delivery. The acknowledged copy comes back. The consignment is invoiced. The LR is then closed according to the operator's workflow, while collection is tracked separately through the credit process.
Each of those transitions is a fact worth holding, because the gaps between them are where the business loses time and money. An LR issued three weeks ago that is still not delivered is an operational question. One delivered eleven days ago with no POD back is a documentation question. One with POD back and no invoice raised is an internal process question, and usually the easiest of the three to fix.
Without states, none of these lists exists. The register can tell you what was booked and the accounts can tell you what was billed, and the difference between them is a reconciliation nobody performs weekly.
With states, the operation has a small number of working lists that between them describe the position: LRs in transit past their expected delivery, delivered without POD, and POD received but not billed. Each has an owner and each is short enough to act on. Collection after invoicing is tracked separately through your credit process.
This is the same structure described on Logistics Management Software at the level of the whole operation. The LR is where it becomes concrete.
Freight terms are a field, not a word
Paid, to-pay and to-be-billed look like a label on a document. They are actually instructions that determine several downstream behaviours, and holding them as structured data rather than as printed text is what allows the application to act on them.
Paid generally indicates that the freight is payable by the consignor or other designated party under the agreed freight terms, with the payment status recorded separately.
To-pay generally means the freight is payable by the consignee or other designated party, with collection timing determined by the transporter's agreed terms.
To-be-billed means neither party pays at the time and the freight goes onto a periodic invoice, typically to a contracted customer on credit terms.
Each of these produces a different downstream sequence. Who appears on the invoice. Whether a collection is due at the delivery point under the agreed terms, and has to be reconciled. When the amount becomes a receivable and against whom. Whether the delivery staff need to be told to collect anything.
Where the term is only printed on a form, the application cannot help with any of that, and the handling depends on people knowing. Where it is a field, the application can generate a collection list for consignments marked to-pay, according to the transporter's agreed terms, while to-be-billed consignments can accumulate against the customer's periodic invoice. None of that requires anyone to remember.
Variants matter too. Many transporters use additional terms for specific customers or specific goods. The field should hold your terms rather than a fixed set of three.
Charges have to be attached while they are fresh
An LR is written at booking, before anything has happened. Much of what makes a consignment more expensive than the base freight happens afterwards.
The vehicle waits eleven hours at a plant gate. A second delivery point is added at the customer's request. The consignee's dock is unavailable and the vehicle returns the next morning. Extra labour is engaged for unloading. The route is diverted.
Each of these may be recoverable where the customer's rate contract or agreed terms provide for it, and each is recorded, in the typical operation, in a phone call between a driver and a branch. By the time the monthly invoice is prepared, the charge is either remembered or it is not, and the person preparing the invoice was not on the call.
The failure mode is specific and it is worth naming: an invoice line that was never raised leaves no trace. An incorrect charge gets disputed and corrected. A missing charge is simply absent, and no report will show it, because reports are built from what was billed.
The fix is to make the charge attachable at the moment and place it arises, by the person who is there. A driver at a gate recording arrival time and unloading start time produces a detention record with times on it. A branch adding a second delivery point to the consignment records it as it is agreed. Both take seconds and both survive to the invoice.
This is where the trip record and the consignment record meet. The event happens on the trip; the charge belongs to the consignment. See Trip Sheet and Settlement Software.
Your format, your series
LR formats vary more than most documents in Indian logistics, and a template that cannot be changed is a poor fit.
Numbering series differ by branch and by transporter, sometimes with prefixes indicating branch, vehicle type or customer. Copy structures differ in how many copies are produced and who receives each. The charge heads printed on the document differ. Terms and conditions on the reverse differ. Some customers require their own reference numbers, purchase order numbers or plant codes on the face of the document. Some require particular declarations.
An application built around your document rather than a generic one matters here for a practical reason beyond preference. A document that does not match what your customers and your branches already recognise creates friction at every point it is handled, and the people handling it will go back to the book.
The same applies to the language on the document and to whether it is printed or handwritten in your operation. Some transporters will print LRs at the branch counter. Others will continue writing them and use the application to hold the record. Both are workable and the second is often the right starting point, because it changes nothing at the counter while making the position visible in the office.
Where LRs look different by business type
- Transport Contractor and Fleet Owner Software, where LRs accumulate into a monthly bill against a rate contract.
- Courier and Parcel Business Software, where the equivalent is a high volume of low-value docket numbers rather than individual LRs.
- Bulk and Tanker Transport Software, where the consignment carries loaded and delivered quantity and the variance between them.
- Container Transporter and CFS Software, where the movement runs against a delivery order alongside the consignment document.
- Packers and Movers Software, where the item inventory does much of the work an LR does elsewhere.
- City Distribution Software, where a day's route generates many small consignments to fixed outlets.
Why transporters choose Pentoggle for LR management
Your format and your series
LR layout, numbering, branch prefixes, charge heads and copy structure built around what your business and your customers already use.
Freight terms as a field
Paid, to-pay, to-be-billed and your own variants driving who is billed, when, and what is due for collection under your agreed terms.
Charges attached where they arise
Detention, extra points and additional labour recorded at the moment, by the person present, so they reach the invoice.
States, not just records
States such as in transit, delivered, POD received, invoiced and closed, defined to match your workflow, so the working lists exist without anybody assembling them.
Sits around your accounting
Tally and comparable systems continue handling accounting, invoicing and GST. Pentoggle adds the operational layer around the consignment and its documents.
A useful number for LR management
Open LRs by age, meaning LRs issued and not yet closed.
For this workflow, closed means the operational and billing steps defined by the operator have been completed, such as delivery, POD receipt and invoicing. Collection can be tracked separately according to the business's credit process. Anything short of closure is open, and its age is how long the consignment has been consuming attention without finishing.
Read it broken down by which state each LR is stuck in, because the states have different owners. Stuck in transit is operations. Stuck at POD is documentation and the delivery point. Stuck at invoicing is internal. A single ageing figure tells you there is a backlog; the breakdown tells you whose it is.
This is a segment of the consignment cycle time described on Logistics Management Software. If you are already tracking that at the operation level, use this as its detail view rather than as a separate measure.
Ready to build LR software?
Your booking register knows what you accepted.
Which of those consignments is still waiting on something is a harder question to answer quickly.
Describe your LR format, your freight terms and how consignments close to Pentoggle in plain English and generate a working first version in hours, then refine it around your process.