Case Study · NBFC, Gold Loan
How an NBFC Closed Its Collections Gap with a Custom Field Agent App
For a gold loan NBFC operating across 22 branches with 140 field collection agents, the core business challenge was not credit risk. It was paperwork. Agents collected repayments door to door, wrote receipts by hand, and returned to the branch at close of day. Branch staff then manually entered those receipts into accounting software. By the time head office had a clear picture of the day’s collections, two to three days had already passed. Partial payments slipped through, disputed receipts piled up, and write-offs climbed. This project replaced that paper chain with a mobile-first digital system built on Zoho Creator, connected in real time to Zoho CRM and Zoho Books.
Loan Book Size
₹80–120 Cr outstanding
Company Size
140 field agents, 22 branches
Tools Deployed
Creator, CRM, Books, Analytics
The Problem
The field collections process had three interconnected failure points. Each one independently created operational risk. Together, they produced a reconciliation backlog that made real-time portfolio visibility impossible.
Paper Receipt Backlog
Agents submitted handwritten receipts at the end of each day. Branch staff then re-keyed every entry manually, introducing transcription errors and a built-in delay of 24 to 72 hours before head office could act on the data.
No Real-Time Visibility
With a three-day reconciliation lag, collections managers could not identify overdue accounts or agent coverage gaps until it was too late to follow up in the same billing cycle. Portfolio-level decisions were made on stale numbers.
Disputed Payments and Write-offs
Partial payments collected in the field frequently went unrecorded or were misattributed to the wrong loan account. When customers disputed balances, the paper trail was incomplete. Write-offs from these untracked amounts reached ₹18 lakhs annually — a compliance and credit-risk exposure that RBI’s Fair Practices Code for NBFCs requires lenders to actively control.
The Solution Stack
Four Zoho products were configured to cover the full collections cycle: from the moment an agent arrives at a borrower’s door to the point a collections manager reviews branch performance at the end of the week.
Zoho
Creator
- GPS-verified check-in at each borrower visit, with timestamp and location logged automatically — enabled by Zoho Creator’s offline-capable mobile platform
- Digital receipt capture: agent selects loan account, enters amount collected, and marks payment type (full, partial, interest only)
- Offline mode with automatic sync when connectivity is restored, critical for low-signal areas
- Supervisor review queue for exceptions and disputed amounts before they reach accounting
Zoho
CRM
Zoho CRM Loan Account Records and Follow-up Pipeline
- Each loan account is a CRM record with outstanding balance, due date, and agent assignment
- Collection events from Creator update the CRM record in real time, including partial payment history
- Automated follow-up tasks triggered when an account is visited but no payment is collected
- Branch manager view of daily visit coverage by agent and outstanding account status
Zoho
Books
Zoho Books: Receipt Accounting and Daily Reconciliation
- Approved collections from the Creator supervisor queue post automatically as receipts in Zoho Books
- Loan account ledger updated without manual re-entry, eliminating transcription errors
- End-of-day branch reconciliation report generated automatically and emailed to collections managers
- Partial payment allocation logic configured to apply funds to interest first, then principal
Zoho
Analytics
Zoho Analytics Collections Dashboard and Portfolio Reporting
- Live collections dashboard showing same-day receipts by branch, agent, and loan category
- Overdue aging report segmented by days past due (30, 60, 90, 90+) updated daily
- Agent productivity metrics: visits per day, conversion rate (visit to collection), average collection value
- Branch performance comparison to identify high-performing territories and coverage gaps
Before vs. After
| Area |
Before Zoho |
After Zoho |
| Receipt submission method |
Handwritten paper slips submitted at branch end of day |
Digital entry in mobile app at point of collection |
| Reconciliation lag |
2 to 3 days from collection to books entry |
91% of receipts reconciled same day |
| Visit logging per agent per day |
4 to 6 visits recorded (paper, self-reported) |
3.2x more visits logged with GPS verification |
| Partial payment tracking |
Often missed or attributed to the wrong account |
Captured at loan account level with allocation logic in Books |
| Head office portfolio visibility |
Stale data, 2 to 3 days behind actual collections |
Live dashboard updated throughout the day |
| Disputed receipt resolution |
No audit trail, resolved by manual escalation |
GPS timestamp and digital record available for every visit |
| Annual write-offs from untracked payments |
₹18 lakhs per year |
Reduced to near zero in first 12 months |
Implementation Phases
The project ran across four phases over approximately 14 weeks. Priority was given to getting the Creator app into agents’ hands quickly, with accounting integration and analytics following once core data quality was confirmed.
1
Discovery and Data Architecture Weeks 1-2
- Mapped the existing paper receipt workflow across all 22 branches to identify variation in collection procedures
- Audited the Tally loan register to define the loan account data model for CRM migration
- Defined field data requirements: payment types, partial payment rules, GPS verification thresholds
- Agreed on the supervisor approval queue design to handle exceptions before they reached Books
2
Creator App and CRM Build Weeks 3-7
- Built the Zoho Creator mobile app with GPS check-in, loan account lookup, and digital receipt form
- Configured offline sync logic to queue submissions when agents operated in low-connectivity areas
- Imported and cleaned loan account data into Zoho CRM, including outstanding balances and due dates
- Set up CRM workflows to update loan records in real time as Creator collections were submitted and approved
3
Books Integration and Pilot Branch Weeks 8-11
- Connected the Creator supervisor approval queue to Zoho Books via webhook, auto-posting approved receipts
- Configured partial payment allocation rules in Books to match the NBFC’s internal accounting policy
- Ran a four-week parallel pilot at two branches: paper process and digital system operating simultaneously for audit comparison
- Validated that 97% of digital receipts posted to Books without manual correction before full rollout
4
Analytics, Full Rollout, and Training Weeks 12-14
- Built the Zoho Analytics collections dashboard, overdue aging report, and agent productivity views
- Rolled out the Creator app to all 140 field agents across 22 branches with two days of hands-on training per cluster
- Ran branch manager sessions on the daily reconciliation report and escalation procedures in CRM
- Decommissioned the paper receipt workflow at the end of week 14 after confirming reconciliation accuracy targets were met
Results
Measured outcomes at the 12-month mark after full rollout across all branches.
0%
Collections Reconciled Same Day
0×
More Field Visits Logged Daily
₹0L
Annual Write-off Reduction
KPI Comparison: Before vs. After (Key Operational Metrics)
Monthly Same-Day Reconciliation Rate (% of receipts reconciled same day)
The Core Lesson
For NBFCs running large field agent networks, the collections data problem is almost always a process problem dressed as a technology problem. Paper receipts are slow not because paper is slow, but because they require a human re-entry step that adds delay, error, and no audit trail. Removing that re-entry step, by capturing data at the point of collection and routing it directly into accounting, is what produced the reconciliation improvement here. The Zoho stack provided the infrastructure, but the outcome depended on designing the workflow correctly so agents could complete a digital receipt in under 60 seconds and move to the next visit. If your NBFC faces a similar collections gap, speak with our Zoho consultants to scope a solution.
Frequently Asked Questions
What happens when a field agent has no internet connectivity during a collection visit?
The Zoho Creator mobile app is configured with offline mode. When an agent is in a low-signal area, the digital receipt is saved locally on the device and queued for sync. As soon as the device reconnects, whether over mobile data or Wi-Fi at the branch, all queued entries are uploaded automatically. No agent action is required. The sync log is visible to supervisors so they can confirm all offline entries have been received before the end of the day reconciliation window closes.
How does the system handle partial payments, and are they tracked separately from full loan repayments?
Yes, partial payments are recorded as a distinct payment type in the Creator app. The agent selects whether the collection is a full repayment, an interest-only payment, or a partial principal payment. This classification is passed through to Zoho Books, where the allocation rule applies funds to interest first and then principal, in line with the NBFC’s accounting policy. The loan account record in Zoho CRM is updated with the precise amount collected and the payment type, so collections managers can see the true outstanding balance at any point rather than treating all collections as equivalent.
How long did it take for field agents to adopt the mobile app, and what was the training approach?
Agent adoption was designed around the constraint that most field agents are not heavy smartphone users and spend the majority of their day moving between visits. The Creator app was built with a minimal interface: the agent logs in once, selects a loan account from their assigned list, enters the amount, marks the payment type, and submits. The entire flow takes under 60 seconds. Training was delivered in branch clusters over two days per group, with a focus on the three most common scenarios: full collection, partial collection, and a visit where no payment is received. Within the first month, over 90% of agents were submitting digital receipts without supervisor assistance.
Can this approach work for an NBFC that currently uses a core banking system rather than Tally or Books for its loan ledger?
Yes, with some integration work. In this project, Zoho Books served as the collections accounting layer because the NBFC did not have a core banking system that supported API-level integration. For NBFCs using a core banking platform, the Creator app and CRM components remain the same. The difference is that the approved-collection webhook from Creator’s supervisor queue would post to the core banking system’s API rather than to Books. Zoho Analytics can then pull data from both sources for the reporting layer. The architecture is modular enough that the accounting destination can be swapped out without changing the agent-facing mobile app or the CRM loan account structure.
