Managing freight across hundreds of trucks means handling hundreds of lorry receipts every week. When those receipts are tracked in spreadsheets and reconciled manually against vendor invoices, even a small volume of mismatches compounds into delayed payments, strained carrier relationships, and cash locked in dispute cycles. This aggregator engaged our Zoho services team to automate the reconciliation workflow end to end.
Lorry receipts arrived in multiple formats from dozens of carriers. Staff matched them to purchase orders by hand, producing a mismatch rate that consumed two full working days per billing cycle.
Disputed invoices sat unresolved because there was no audit trail linking delivery confirmation, LR numbers, and billed amounts. Carriers withheld future capacity until outstanding bills were settled.
Trucks waiting beyond agreed loading windows incurred detention fees that were neither tracked nor billed to clients on time. The leakage was discovered only during annual audits.
| Area | Before | After |
|---|---|---|
| LR matching method | Manual spreadsheet comparison, 2 days per cycle | Automated three-way match on submission, minutes |
| Invoice dispute rate | ~28% of carrier invoices raised a dispute | Under 8% dispute rate, flagged before payment |
| Average payment cycle | 42–48 days from delivery to payment | 12–16 days, weekly payment runs |
| Detention charge tracking | Not tracked in real time, recovered partially at year-end | Auto-generated detention record per incident, billed within 48 hours |
| Carrier visibility | No scorecard, disputes handled by phone | Per-carrier dispute and payment dashboard in Analytics |
| Finance team effort | 4 staff on reconciliation, recurring overtime | 2 staff managing exception queue only |
Key Operational KPIs — Before vs. After
Unreconciled Invoice Count — Monthly Trend
Beyond the headline numbers, the finance team’s workload composition changed materially. Staff who spent the majority of their time chasing mismatches now manage only the flagged exception queue.
Freight finance disputes are almost never about bad faith. They happen because the data that proves delivery occurred lives in a different system from the data that authorises payment. Connecting those systems with an automated match rule eliminates the gap where disputes grow.
Does Zoho Creator handle offline LR entry for yard staff without internet access?
Yes. The Creator mobile app can be configured to store form submissions locally and sync when connectivity is restored. The sync happens automatically once the device reconnects, and the detention timer is calculated from the logged timestamp rather than the sync time.
How does the three-way match work in Zoho Books for freight invoices?
A purchase order is raised in Books against each confirmed LR number before the carrier submits an invoice. When the invoice arrives, Books compares the billed amount and quantity against the PO and the delivery confirmation record. If all three align within the configured tolerance, the invoice moves to the payment queue automatically.
Can detention charges be billed directly to clients from the same setup?
Yes. Once a detention record is generated in Creator, a workflow posts it to Books as a line item on the relevant client’s account.
How long does implementation typically take for a freight aggregator of this size?
For a fleet of 180 to 220 trucks with 30 to 40 carrier partners, a nine-week timeline is typical when carrier contract data is available from the start.
We've helped 50+ businesses implement Zoho and NetSuite. Let's talk about yours.