The bilty book is on a truck. The POD is in a driver's bag for three days. The invoice waits on both - and your payment cycle stretches to 45 days. An engineer sits in your back office with your finance person, not on a call. Working demo by day 7, live on your trips by week 3, a measured payment-cycle number by week 8 - on top of your Tally, nothing installed on your trucks.
Every delivered trip should become an invoice the day it's delivered. Instead the lorry receipt arrives in one of a dozen carrier formats, the POD comes back days later (if it comes back clean at all), and your finance person matches it all by hand in Tally. Disputes sit unresolved because nothing links the delivery confirmation, the LR number and the billed amount. So carriers withhold capacity, customers stretch payment, and the cash you already earned sits in a bag on a truck.
A surface-freight aggregator's team spent two full working days every billing cycle just matching lorry receipts by hand; ~28% of carrier invoices raised a dispute and the average payment cycle ran 42-48 days. After a three-way match (contracted freight × delivery confirmation × billed amount, with a ₹500 / 2% tolerance), disputes fell to under 8% and the cycle to 12-16 days. The math is the same everywhere: there is no audit trail linking the POD to the bill.
| LR no. · Lane | Vehicle | Contract ₹ | Billed ₹ | Δ | POD | Status | Days o/s |
|---|---|---|---|---|---|---|---|
| SBR/24-25/0377 Bengaluru → Hosur → Chennai |
KA-01-AB-1234 | 38,000 | 38,000 | 0 | Received | Matched ✓ | 3 |
| SBR/24-25/0392 Bengaluru → Tumakuru → Hubballi |
KA-05-CJ-7781 | 29,400 | 33,300 | +3,900 | Aged 4d | Rate ₹42 vs ₹47/qtl | 11 |
| SBR/24-25/0401 Chennai → Krishnagiri → Bengaluru |
TN-22-DK-5590 | 41,500 | 37,200 | −4,300 | Received | Short-billed ₹4,300 | 8 |
| SBR/24-25/0418 Hosur → Salem → Madurai |
KA-51-MH-2207 | 52,000 | - | - | Missing | No POD · 9d | 9 |
| SBR/24-25/0423 Bengaluru → Hosur → Chennai |
KA-01-AB-1234 | 38,000 | 40,100 | +2,100 | Received | Over-billed ₹2,100 · detention | 6 |
| SBR/24-25/0431 Chennai → Vellore → Bengaluru |
TN-09-BR-4412 | 44,200 | 44,200 | 0 | Received | Matched ✓ · auto-invoiced | 1 |
Every delivered, POD-clean, matched trip becomes an invoice the same day - only the four exceptions reach a person.
You hire trucks trip-by-trip - you can't bolt a GPS onto a vehicle you'll give back tomorrow, and 75%+ of Indian truck owners run ≤5 trucks, so fixed hardware on a variable business never pencils out. We track location off the driver's own phone: a WhatsApp link, the truck on the map in under two minutes, nothing installed. Owned trucks can take a cheap retrofit sensor where you want deeper telemetry. The customer gets a login-free tracking link; you stop personally answering "where's my truck."
Traffic, toll queues, a weighbridge wait - the EWB lapses while the truck is still moving, FASTag data flags it, and Section 129 lets an officer levy 200% of the tax payable on the consignment. The watchdog ties each EWB's validity to the trip's live ETA and warns dispatch and the driver before expiry, inside the 4-hour extension window. It pre-validates vehicle no., PIN and amount against the invoice, and flags the Rule 138E freeze - EWB generation auto-blocks if GSTR-3B is pending two consecutive periods - before you dispatch.
| EWB no. · Vehicle | Valid till | vs ETA | |
|---|---|---|---|
| 3318 4471 0029 KA-51-MH-2207 |
17/06 · 23:59 | ETA 01:10 ⚠ | |
| 3318 4470 8814 TN-22-DK-5590 |
18/06 · 14:00 | 6h margin | |
| 3318 4472 1190 KA-01-AB-1234 |
19/06 · 23:59 | safe |
Run two-to-five courier partners and each sends its own remittance format on its own schedule - finance burns 3-5 working days a month matching AWB to order to remittance to deductions, and 2-8% of COD revenue goes missing or short-paid. We ingest each courier's remittance CSV against your order export, auto-match on AWB and amount, and flag every gap - MISSING · SHORT-PAID · OVERDUE · RTO-ANOMALY - tied back to the GPS-linked ePOD so a "delivered, no cash" fake gets caught.
| AWB | Order ₹ | Remitted ₹ | Status |
|---|---|---|---|
| DL-88421907 | 1,499 | 1,470 | Short −₹29 fee |
| BD-55190234 | 1,299 | - | Missing · 9d |
| DL-88419772 | 2,250 | 2,050 | Short −₹200 |
| BD-55188110 | 899 | 899 | Settled ✓ |
| DL-88420065 | 1,750 | 0 | RTO anomaly · agent K-12 |
Our Machine Monitor puts running/idle/off telemetry on 20-year-old machines with no PLC and no retrofit to the controller - clamp-on sensing, today, in production. No-retrofit tracking on old and hired trucks is that exact principle pointed at a different asset: work with what's already there, install nothing, get the signal anyway. That's why we're confident we can demo it in week one - we've done the hard part before.
You've read one problem in full. These are the next ones we hear most from transporters running 5-80 trucks on Tally, Excel, WhatsApp and a paper LR book. Each is a real ask with a real number behind it - not a capability we're padding the page with.
Photo + e-signature + geo-tag + seal number at the door, invoice raised in under 48 hours instead of the 15 days a paper POD takes to walk back to the office.
Free-time starts at gate-in, not reporting time; auto-builds a dispute-proof evidence pack and pushes a detention line straight into reconciliation. Detention quietly eats margin every day it's untracked.
Auto-allocate loads by lane and carrier score, confirm the driver over WhatsApp - no portal for the transporter, because they won't log in. Manual dispatch leaves trucks 2-4 hrs late at ~75% utilization.
One shared view across Bengaluru · Hosur · Chennai branches replacing per-branch Excel + WhatsApp groups - 40-50% of small fleets still run paper or spreadsheet dispatch.
A retrofit tank sensor - Machine Monitor on a diesel tank - flags receipt-vs-sensor gaps and unauthorised-stop drains. Operators report losing 10-20% of fuel spend to pilferage.
Per-bill RCM vs forward-charge tagging, transporter-ledger handling and an "input at risk" flag - so you stop losing GST input on freight that wasn't recorded right.
We won't blur the line, because in a trust business blurring it once poisons everything. So here it is, first-class: what's live on real assets today, and what's a concept we built to show our reasoning before you've signed a thing.
Running / idle / off telemetry on 20-year-old machines - no PLC, no controller retrofit, clamp-on sensing - plus a clinic operations product in daily use. Real users, real assets. The no-retrofit truck tracking on this page is that same play.
The reconciliation board, the track-and-trace map, the EWB watchdog, the COD grid - concepts, and we'd rather say so. That we can spec your solution this precisely before signing is the point: it's our opening move, not our ceiling. Your week-one demo would be real, on your seed data.
This page shows four. Your operation has its own worst one - a lane that always disputes, a customer that always detains, a courier that always short-pays. Bring it. We'll have a working demo in seven days, on your Tally, nothing installed on your trucks.