Case Study · Surface Freight Aggregation
How a Freight Aggregator Cut Billing Cycles by 68% with Digital POD
Revenue Band
₹40-80 Cr ARR
Fleet Coverage
300+ FTL/LTL Routes
Billing Cycle Before
~60 Days DSO
Billing Cycle After
Under 20 Days DSO
For a freight aggregator managing hundreds of FTL and LTL lanes, the proof of delivery document is the starting pistol for every invoice. When that document traveled by courier van instead of data pipe, billing waited. This engagement replaced a paper-based POD process with a Zoho Creator mobile app, automating GST invoice generation the moment a consignee signs on screen. The result: a billing cycle compressed from 60 days to under 20, and ₹18 lakh in previously locked working capital returned to operations.
The Problem
Paper POD Bottleneck
Drivers collected physical signed PODs at delivery and couriered them back to the billing team. On long-haul FTL runs, that transit added 5 to 12 days before a single invoice could be raised, stalling every downstream payment cycle.
Manual Billing Keying
Once PODs arrived, billing staff re-keyed consignee details, freight rates, and GST components into spreadsheets. Transcription errors triggered dispute cycles with consignees, adding days of back-and-forth to an already slow process.
Working Capital Drain
A 60-day average DSO locked ₹18 lakh or more in receivables at any given point. The aggregator funded carrier payouts from its own cash before consignee payments cleared, compressing already-thin freight margins on every lane.
The Solution Stack
On-screen POD capture replaces courier transit
- Driver opens mobile form linked to trip ID; scans consignee e-way bill QR to pre-fill shipment details automatically
- Consignee signs on screen; photo of goods condition attached at point of delivery
- POD status syncs to operations dashboard within seconds, triggering billing workflow without manual handoff
- Offline capture supported; record syncs automatically when connectivity is restored
GST invoice generated on POD approval, zero keystrokes
- Creator pulls contracted freight rate and computes IGST or CGST plus SGST based on origin-destination state pair
- Invoice PDF generated and emailed to consignee without any manual step
- Credit note and short-delivery workflows handle exceptions inside the same app
Structured dispute resolution with enforced SLAs
- Invoice emails include a “Raise a Query” link that opens a pre-filled Desk ticket, replacing unstructured phone and email chains
- SLA rules auto-escalate unresolved disputes after 48 hours to the assigned account manager
- Resolution notes and credit approvals feed back into Creator billing record for reconciliation
Live DSO and POD turnaround dashboards
- Analytics pulls live data from Creator to surface per-consignee DSO, overdue invoice aging, and trip-level POD turnaround times
- Finance team views cash flow projections based on pending POD approvals and invoice due dates
- Weekly SLA report surfaces routes where delivery confirmation lags, enabling proactive driver follow-up
This stack was configured end-to-end as part of our Zoho implementation services for logistics clients — covering app build, integration, and go-live support.
Before vs. After
| Area |
Before |
After |
| POD Collection |
Physical document couriered from delivery point to billing office |
On-screen signature via Creator mobile app at point of delivery |
| Delivery to POD in System |
5 to 12 days transit per trip |
Under 10 minutes, synced on approval |
| Invoice Generation |
Manual spreadsheet keying with frequent transcription errors |
Auto-generated on POD approval, no manual input |
| Average Billing Cycle (DSO) |
~60 days |
Under 20 days |
| Dispute Handling |
Unstructured email and phone, no tracking or escalation |
Zoho Desk tickets with 48-hour SLA and auto-escalation |
| Delivery SLA Visibility |
Weekly manual Excel compiled from driver check-ins |
Live Zoho Analytics dashboard per route and per consignee |
Implementation Phases
1
Discovery and Data Mapping Weeks 1-2
- Audited all rate-card spreadsheets across active lanes and identified 14 distinct freight billing scenarios
- Mapped consignee master data, GST registration types, and state-pair tax rules into a structured data model
- Documented exception flows: short deliveries, rejections, partial unloads, and credit note triggers
2
Creator App Build and Pilot Weeks 3-5
- Built mobile POD form with e-way bill QR parsing, photo upload for goods condition, and digital signature widget
- Configured billing engine logic covering all 14 scenarios with automated IGST/CGST+SGST computation
- Piloted with 12 drivers across 3 high-volume lanes before full fleet rollout
3
Desk Integration and SLA Configuration Weeks 6-7
- Connected Zoho Desk to Creator billing via webhook so invoice queries auto-create pre-filled tickets
- Configured 48-hour SLA rules with escalation paths mapped to account managers by consignee segment
- Tested end-to-end dispute flow from invoice email through ticket resolution and credit note issuance
4
Analytics Dashboard and Handover Week 8
- Built live dashboards in Zoho Analytics: DSO by consignee, aging buckets, POD turnaround by route
- Configured cash flow projection view based on pending POD approvals and expected payment dates
- Conducted finance and operations team training; handed over admin controls and documentation
Results
0%
Reduction in Billing Cycle Time
0%
On-Time Delivery SLA Achieved
₹0L
Annual Working Capital Freed
DSO Reduction Over 6 Months Post-Implementation (Days)
Key Operational Metrics — Before vs. After
What This Means for Surface Freight Aggregators
The billing bottleneck in freight aggregation is almost never the invoice itself. It is the physical document that has to arrive before the invoice can be raised. Moving POD capture to the point of delivery collapses a 5-to-12-day courier lag into seconds, and every downstream process accelerates with it. When the billing trigger is digital, the billing cycle becomes a configuration problem, not a logistics one.
Frequently Asked Questions
Does a digital POD captured via a mobile app hold up for GST audit purposes?
Yes, provided the record includes the required elements: consignee acknowledgment, timestamp, delivery location, and linkage to the e-way bill. The Creator app stores all four against the trip ID, and the generated invoice references the digital POD record directly. The GST framework does not mandate paper for proof of delivery. It requires a valid tax invoice and evidence that the supply occurred. The digital POD satisfies that evidentiary requirement, and the immutable Creator record is available for audit export at any point.
What happens when a driver has no internet connectivity at a remote delivery point?
Zoho Creator mobile apps support offline data entry. The driver completes the POD form, including the consignee’s on-screen signature and goods photo, while offline. The record is queued locally on the device and syncs automatically once connectivity is restored, whether that is at the next highway stop or back at the depot. The billing workflow triggers only after the sync completes and the POD is approved in the system, so the offline capture delays the sync by the duration of the connectivity gap rather than by courier transit time.
How does the system handle short deliveries or partial unloads where the consignee disputes the quantity?
The Creator app includes a short-delivery workflow built into the POD form. If the delivered quantity does not match the consignment note, the driver records the variance and the consignee countersigns the exception. This triggers a credit note workflow inside Creator rather than the standard invoice path. The Zoho Desk integration also captures the dispute as a ticket at the moment of invoice delivery, so finance and account management teams have full visibility of contested amounts before the payment due date arrives.
Can the billing engine handle both IGST and CGST-plus-SGST computation automatically across different state pairs?
The billing engine in Creator uses the origin and destination state codes from the e-way bill scan to determine whether the movement is inter-state or intra-state. Inter-state routes apply IGST at the contracted rate; intra-state routes split the tax into CGST and SGST components. The state-pair logic is maintained in a lookup table inside Creator, so adding a new lane or adjusting a rate card requires a table update rather than a code change. All 14 freight billing scenarios identified during the discovery phase are covered by the engine.
