The complete guide to microfinance field collection in India (2026)

Field collection is the operational backbone of every microfinance business in India. Loan disbursement is the marketing spend; field collection is what turns it into a business. And yet most branches still run collection on paper, WhatsApp, and trust — with no verifiable evidence that any given visit happened.

This is a full playbook: what good field collection looks like in 2026, the four fraud patterns to defend against, the documentation the RBI expects, and how to pick the software that actually works in Tier 2–3 India.

The five-stage collection workflow

Every well-run microfinance branch runs some version of this pipeline. The names change; the stages do not.

1. Route planning

Field officers get assigned borrower groups by area. A good route plan is:

• Geographic — one contiguous cluster per officer, not a scatter plot
• Balanced — every officer has roughly the same borrower count and expected daily collection
• Rotational — routes change every 3–6 months so no officer "owns" a borrower relationship permanently (fraud prevention)

2. Daily brief

The officer starts the day knowing:

• Who is due today
• Who is overdue and by how much
• Which borrowers need supervisor follow-up
• Which routes have not been visited in >30 days (retention signal)

3. Field visit with verification

Every visit produces evidence:

• GPS coordinates at check-in (accuracy < 50m)
• Selfie of the officer at the location
• Timestamp (server-side, not device)
• Amount collected + payment method
• Optional receipt photo

Skip any of these and the visit is unverifiable. See our post on GPS-verified field visits for the technical stack.

4. End-of-day reconciliation

Cash collected in the field must reconcile with:

• Individual receipts issued
• Branch cash deposit at end of day
• Bank credit within T+1

Any variance triggers a supervisor review the next morning.

5. Monthly audit and rotation

Once a month:

• Random borrower call-back sample (5% or higher)
• Officer rotation review
• Overdue portfolio aging analysis
• Fraud pattern check (see next section)

The four fraud patterns to defend against

Field collection fraud in Indian MFIs falls into four archetypes. If you defend against these four, you catch 95%+ of what actually happens.

1. Ghost visits

Pattern: Officer marks a visit that never happened. Borrower says nobody came. Money the officer claims to have collected is missing.

Defence: Mandatory GPS + selfie at check-in. Random 5% callback sample every month. Cross-reference officer route with borrower geo-coordinates.

2. Skimming

Pattern: Officer collects ₹1000 but reports ₹800. Pockets the difference.

Defence: Every payment issues a printed or SMS receipt to the borrower with the exact amount. Random borrower callback confirms amount actually paid.

3. Ghost borrowers

Pattern: Loan approved to a person who does not exist, disbursed to officer's own accomplice, "repaid" from other borrowers' collections (Ponzi-style).

Defence: Independent KYC verification (not by the field officer). Random field verification by supervisor. Portfolio concentration alerts if one officer's borrower list is unusually clustered.

4. Group collusion

Pattern: In JLG loans, the whole group agrees to skip a member's payment because "she is having a bad month" — but never tells the branch. Reported as "collected" from group pool.

Defence: Individual receipt per group member, not per group. Digital ledger visible to every member. Monthly branch reconciliation of member-level dues.

What the RBI expects

Under current RBI microfinance guidelines (Master Direction – Regulatory Framework for Microfinance Loans, 2022), your field collection process must produce:

• Auditable record of every collection interaction
• Household income assessment before further lending
• No harassment — clear documentation of contact timing and behaviour
• Fair Practices Code compliance in every interaction

The practical read: your collection process needs to be documented, not just executed. A verbal handshake will not survive an RBI inspection or a customer complaint escalation.

Signs your current process is broken

Any of these are red flags:

• Reported visits > actual borrowers × 1 (some officers are marking multiple visits per borrower)
• Officer productivity outliers (top performer at 3x average — investigate before you promote)
• Cash-in-hand lags cash-collected by more than 1 day
• Portfolio-at-risk (PAR) is stable but reported visits are up (you are collecting from the same borrowers, ignoring the delinquent ones)

How to pick software that works

For a branch-level MFI or an NBFC's collection team, the buying criteria are:

• Works offline — village network coverage is unreliable; the app cannot stall the officer's day
• Anti-cheat by default — mock GPS detection, selfie verification, proximity checks
• Multi-language — officers work in their comfort language; mistakes drop 30%+
• Fast onboarding — a new officer should be usable within a day, not a week
• Auditable — every check-in, payment, and change tracked with timestamp and location

CollectRoute is built specifically for this. See the microfinance vertical page for how it maps to the workflow above, or start a free trial.

What to do this week

If you take one thing from this guide, do this on Monday:

1. Pick 20 random borrowers from last week's officer reports
2. Call them
3. Ask if the officer visited and what amount was collected
4. Compare to the officer's report

You will find a variance. The variance is your starting point.