01 · Project at a glance

At a village centre, one collection used to touch four tools. The new app needs one.

I’m designing the collections app for Piramal Finance’s microfinance loans. Relationship Managers (RMs) use it to visit a women’s group centre each month, take attendance and EMIs, count the cash and get it deposited. It replaces a paper demand sheet, a customer card, a cash-counting app and a hard-to-use app called Microsure.

Role
Design lead, Collections
Within the MFI project
Team
2 PMs, 6 engineers
With the other MFI designers
Platform
Mobile
Status
In development
Being built by 6 engineers
Users
Relationship Managers
They give the loan and collect on it
Loans
₹10,000 to ₹1 lakh
To women in groups, with no collateral
A collection day
6 or 7 centres
45 to 60 minutes at each
Research
4 days, 2 branches
Mandya and Mysuru
4 → 1tools to record one collection: sheet, card, counting app, Microsure
0paper sheets or cards to carry on collection day
Same daycash deposit, with every rupee carried tracked in the app
  • Mine: the design for collections, from the branch visits to the flows, screens and edge cases, now being handed to engineering. I lead design for collections within the MFI project.
  • Shared: scope and priorities, with two PMs. The other MFI designers work on other parts of the same project.
  • Fixed from the start: customers pay by cash, QR code or payment link, and cash still has to be counted, carried and deposited. The app can’t remove that, so it makes it visible.

02 · Context

In microfinance, collection is a visit the whole group is expecting.

Piramal Finance gives small loans to women in villages, with no collateral. A few women borrow together as a group, and several groups form a centre that meets in one place on a fixed day, often as early as 6am so people can get to work afterwards. The RM who gave the loan comes every month to collect the EMI and any overdue.

  • The same RM disburses and collects. There is no separate collections team. A branch has one or two Branch Managers (BMs), and each has three or four RMs, who usually stay with the same centres.
  • Groups stand behind each other. A few women from the same village borrow together and share responsibility for repayment. That takes the place of collateral.
  • Collection used to happen on just two fixed days a month. With the loan book growing fast that stopped working, so centres now have their own due dates, like the second Monday of the month.
  • The paper sheet ran the day. Microsure was where the data went afterwards, because its screens were hard to use and some features were missing. So the same collection was written down again once the centre was over.
What one collection touched, before and after
Before
Printed demand sheet Customer’s paper card Phone calls to customers Cash-counting app Microsure
After
MFI Collections appOne entry per collection
The centre demand sheet · Front and back
REPLACE: Photo of the demand sheet, both sidesBlur names, account numbers and signatures before using
The old Microsure app
REPLACE: Microsure screenshotsTwo or three screens that show why it was hard to use · blur any customer data
The sheet and the card
REPLACE: Demand sheet and customer cardBlur names, account numbers and signatures
Absent, and paid
REPLACE: Crop of a sheet row marked absent with an amount collectedBlur names and account numbers
Counting the cash
REPLACE: The old counting app, or the back of the sheet
How I researched it

I spent four days at two branches, Mandya and Mysuru, watching how an MFI loan is given, how groups and centres work and how collection runs once everyone is in the room. I hadn’t expected cash to be counted in a different app, or Microsure to be mostly where data went once the day was over.

From the field
REPLACE: Field photosCentre meetings and branch visits · only photos where people can’t be identified, or with permission
In their words
REPLACE: Quotes from RMs and BMsTwo or three short quotes, paraphrased is fine
Research artefacts
REPLACE: Journey map, notes, synthesisWhatever shows how the findings were pulled together
What shaped the design
  • Villages and early starts. RMs are at a centre as early as 6am, and customers are heading out to work. The app has to be quick enough to use mid-conversation, and it has to work when the network doesn’t.
  • Cash is still cash. It has to be counted, carried and deposited, so the app makes it easy to see.

03 · Goals

Say it once, at the centre, and follow the cash.

The app isn’t live yet, so these are design aims. I’ll measure them once it is in use.

One entry per collection.

A sheet, a card, a counting app and Microsure each held a piece. The RM should only have to say it once.

Less time at each centre.

An RM spends 45 to 60 minutes at a centre and visits 6 or 7 in a day. That is the number to beat.

Cash that can be followed.

From the centre to the bank, with a deposit receipt that Operations checks.

Quick, and works in a village.

Early starts, a customer waiting, and a network that comes and goes.


04 · The collection day

Go, count, collect, deposit.

The app already holds the centres due, so there is no sheet to pick up. These are the five parts of the day, in the order an RM lives them.

4.1 · Getting to the centre

The day’s centres are already in the app.

What I saw
The RM picked up a printed centre demand sheet from the BM the day before, then phoned customers to say when they were coming. Collection starts as early as 6am, because customers leave for work.
What I did
The centres due are already in the app, with customer numbers for the calls. One tap starts navigation, using the location captured when the loan was given.
4.2 · Attendance and who pays

Ask for attendance, then for money, one customer at a time.

What I saw
The old way took attendance for the whole centre first and collected from everyone afterwards. But a customer can be absent and still have paid. She hands her money to another member before leaving for work, and on the sheet she is marked absent with her EMI written in.
What I did
The app shows one customer. The RM asks for her and marks her present or absent. If she is there, it moves straight to her money. If she isn’t there, or doesn’t pay, it asks for a reason. When another member pays for her, the RM picks who, and the payment is recorded against the customer whose EMI it is.
What I gave up
Marking the whole centre first. One customer at a time is simpler, and it follows the way an RM already works through a room. I also tried collecting first and taking attendance after, with plenty of variations of the screens, before landing on this.
  1. Step 1Attendance

    One customer at a time, with a reason if she is absent.

  2. Step 2Who is paying

    The RM picks from the customers in the centre, with her group close at hand.

See iterations
4.3 · Taking the money

Take the money, and count it, in one place.

What I saw
RMs counted notes in a separate basic app, wrote the denominations on the back of the sheet, and entered the total again. Amounts went on the sheet by hand, and an online payment was noted as the word “online”. The customer’s paper card was ticked for each EMI.
What I did
Cash, QR code and payment link all sit in one flow, and overdue is collected in the same visit. Cash is counted on the same screen, so the total is entered once. The moment it’s done, the customer gets a receipt and her card update by SMS on her registered number.
4.4 · Closing the centre

Take the proof in the room.

What I saw
After the centre, the RM re-entered attendance and amounts in Microsure and uploaded a photo as proof.
What I did
The RM photographs the people present and the centre in the app, while everyone is still there. It replaces the photo uploaded afterwards, and everything is recorded as it happens.
4.5 · Cash to the bank

Keep the cash visible until it’s in the bank.

What I saw
By the end of the day the RM is carrying cash from several centres. It reaches the company’s bank account through a cash management agency (CMA).
What I did
The app keeps a running “cash carried” figure. The RM deposits the same day, or the day after with a good reason, and uploads the CMA’s receipt. That clears the cash and sends the receipt to the BM, then Operations, to check the amount. Almost every receipt covers a single day’s collection.

05 · When a day goes off plan

Not every centre meeting goes to plan.

A lot of real collections don’t go in a straight line, so these cases were designed up front rather than patched in later.

5.1 · Edge cases

Four cases I designed up front.

What I saw
Not every centre meeting goes in a straight line. A customer can be absent and still have paid, an RM may be collecting overdue, a village centre may have no network, and Operations may decline a deposit receipt.
  1. Case 1Absent, but paid

    Attendance and payment are recorded separately: a reason, and who handed over the money.

  2. Case 2Behind on EMIs

    Collected in the same visit. An RM may take two EMIs from one customer. Beyond two, the RM or a Collection Executive goes to her home.

  3. Case 3No network

    Everything is stored on the phone and sent when signal returns. The RM carries on.

  4. Case 4Deposit declined

    The request goes back to the RM, who uploads the receipt again.


06 · The full design

One collection day, in one place.

The central collection screen is where attendance and money are taken, one customer at a time. All names and amounts are made up.


07 · Delivery

Made with two PMs and the MFI design team.

I worked on collections as part of the larger MFI project, with two PMs and the other MFI designers.

  • Handed to six engineers. They are building it now, and I’m going through the flows and edge cases with them.
  • Collections first. After collections, one-time settlement and foreclosure are next for MFI.
What the app covers
  • Centres due already in the app, with one-tap navigation
  • Attendance, then money, one customer at a time
  • Cash, QR code and payment link, with cash counted inside the flow
  • Receipt and card update sent by SMS
  • Photos of the people present and the centre
  • Works offline, and sends when the network returns
  • “Cash carried” tracked until it’s deposited
  • Deposit receipt checked by the BM and Operations

08 · Results

Fewer tools, faster centres, and cash that can be followed.

The app hasn’t launched, so this is what the design is aiming at, not results.

4 → 1
tools to record one collection
Design aim

One entry per collection, recorded on the spot.

The same collection used to be written down again once the centre was over. Now the RM records it once.

0paper sheets or cards to carry, because the centres due are already in the app
45–60 min
at a centre today, the number to beat
Design aim

Less time at each centre.

Counting, recording and the receipt now happen in the flow, so I expect the time at each centre to come down.

Same day
cash deposit
Design aim

Cash that can be followed, from the centre to the bank.

The deposit receipt clears the cash carried, and Operations checks the amount. Absence and non-payment are recorded with a reason at the time, not remembered later.

What I learned

The biggest saving was removing the second pass.

The RM already knows what happened at the centre. Most of the design was making sure they only have to say it once, on the spot, instead of again from a sheet later.

The cash trail is what I’d watch first.

Once the app is live, I’d look at how often deposit receipts are declined, and why.


Get in touch

If this was interesting, I'd like to hear from you.

I'm happy to walk through the project or answer any questions.