REPLACE: Hero product screenshotOTS dashboard or request tracker · 16:9
01 · Project at a glance
Settling a bad loan used to take three days and four different systems.
We built the One-Time Settlement (OTS) flow inside Collection Central, Piramal Finance’s collections tool. A request is now raised, approved and paid in one place, and it takes less than a day.
Role
Product Designer
Research to UAT
Team
2 PMs, 7 engineers
I was the only designer
Platform
Web
Inside Collection Central
Status
Shipped
Users
ARMs and approvers
ARMs raise requests, a chain of approvers signs off
Settlements
₹15–20 Cr a month
Now run through this flow
<24 hrsto process a request, down from 2–3 days
4 → 1systems, now just one
100%of requests with a full audit trail, up from none
Mine: how a request is raised, how it is approved and how the payment is tracked, from the first sessions with ARMs to the last screen. I was the only designer.
Shared: scope, with both PMs. We started before there was a spec, and a lot of our early flows went into the PRD. I went through edge cases with the engineers during the build.
Fixed from the start: Collection Central’s design system, the existing OAS and LMS, and the documents that audit and NBFC rules require at every step.
02 · Context
Four tools, and nobody had the full picture.
A One-Time Settlement is how the company closes a loan that won’t be repaid in full. A field collector negotiates a reduced amount with the customer, that amount goes up a chain of approvers, and once it is approved the customer pays.
Requests went by email, approvals went somewhere else. An Area Relationship Manager (ARM) emailed the request in, and it was approved in a separate Online Approval System (OAS).
Payment and tracking lived in two more places. Payment information sat in the Loan Management System (LMS), and someone kept an Excel sheet of the open requests.
Nobody could see the whole. To find out where a request was stuck, whether the customer had defaulted on a settlement before, or where the audit papers were, you asked around. It took 2 to 3 days.
How a settlement moved, before and after
Before · 2–3 days
Email threadsExcel trackerOnline Approval SystemLoan Management System
↓
After · under 24 hours
Collection CentralOne OTS workflow
As-Is Process Map
REPLACE: Discovery artifactFigJam as-is map or workshop photo
How I researched it
Before opening Figma, I followed real requests from start to end, and what actually happened was very different from the written process. I sat with 5 to 6 ARMs who raise the requests, with the GRMs and BRMs who approve them, and with the collections business team. Then, with product, engineering and audit, we listed every approval, document and rule that had to move online.
What I couldn’t change
The look. Collection Central already had a design system, and a new look was not needed.
The other systems. OAS and LMS weren’t going anywhere, so whatever we made had to work with them.
Audit. Internal audit and NBFC rules meant specific documents, records and approval evidence had to exist at every step.
03 · Goals
Make the whole process visible, then make it faster.
People said settlements were slow. But nobody could see the whole process, so nobody took charge of it. The goals are about seeing it and following it through, as well as speed.
Under a day, not 2 to 3.
A request should move without email threads and chasing.
Anyone can see where it is.
Who has the request now, who is next, and whether this customer has settled before.
Approved means paid.
A settlement shouldn’t fall through between approval and payment.
Audit finds it all in one place.
Documents, approvals and payments sit on one record, at every step.
04 · The flow
One request, from the first step to approval.
Three parts of the flow do most of the work: raising the request, finding the approvers, and following an approval.
4.1 · Raising a request
Raise a request one step at a time.
What I saw
ARMs raise several of these a day, often while still on the phone with the customer. My first version showed the customer’s whole context on one screen. I watched ARMs try it, and it made them slower.
What I did
The request is now a flow of steps: loan details, OTS history, settlement details, tranches. Each step shows only what it needs. The required documents are checked as the request is raised, so it can’t reach the first approver without them.
What I gave up
The full picture on one screen. A dense screen felt helpful, but it slowed people down.
Step 3 of 5OTS details
Only what this step needs.
REPLACE: Document checklist UIRequired documents, checked before the first approver
DocumentsRequired documents
Checked before it goes to the first approver.
See iterations →
REPLACE: Iteration comparisonV1 dense screen beside final stepper
4.2 · Finding the approvers
Type in the amount, and the system finds the approvers.
What I saw
Every OTS is approved according to a Waiver Authority Matrix. The ARM had to work out the right approvers, enter each one in OAS by hand and chase them over email. Get the matrix wrong and the request came back.
What I did
The ARM enters the OTS amount. The system works out the waiver percentage, picks the final approver and routes the request through everyone who needs to recommend it on the way. The ARM doesn’t look anything up.
ARM→GRM→ZRM→NRM→Head of Collections→CEO
Approval chainWho the final approver can be
It depends on how much is waived and how much is outstanding.
4.3 · Following an approval
See where a request is, and send it back on the same screen.
What I saw
Nobody could see where a request was stuck, so people asked around.
What I did
Every request shows who has it now and who is next. Any approver can send it back with a comment. The ARM fixes it in the same request, and the whole back and forth stays on the record.
REPLACE: Approval trackerChain view with current position
TrackingWhere it is
Who has it now, and who is next.
REPLACE: Send-back with comments UIAn approver sends the request back with a comment
ReworkSend back with a comment
The fix happens on the same request.
05 · What research changed
Three things I didn’t know going in.
I followed real requests instead of the process document. These findings changed what we built, and one of them added payments to the project.
5.1 · Month-end expiry
Expire requests that go stale at month end.
What I saw
The amount a customer owes is recalculated on the first of every month. A request raised on the 28th could be based on the wrong numbers by the 1st, and nothing stopped it from going through approvals.
What I did
We decided the system should expire those requests on its own. The ARM raises a fresh one with the current numbers and a new agreement from the customer.
What I gave up
A little of the ARM’s time. Starting again is annoying, but it is much better than approving the wrong amount.
REPLACE: Expiry state / notice UIWhat the ARM sees when a request expires
StateExpired at month end
The ARM raises a fresh request.
5.2 · Payment in tranches
Give every tranche its own payment link.
What I saw
Some settlements got all the way through approval and still weren’t paid. The amount was over the standard UPI transaction limit, so customers tried to split it themselves, and some gave up.
What I did
So we added payments to the project. A settlement can be split into tranches, and the system makes a payment link for each one, under the limit, so the customer pays in one go. Every tranche has its own status and its own entry on the record.
REPLACE: Payment links screenTranche list with link generation
PaymentsA link for each tranche
Each one sized to what can be paid in one transaction.
REPLACE: Payment link generation UIWhere the links are made
LinksGenerating the links
Made as soon as the settlement is approved.
REPLACE: Multi-tranche schedule UIA settlement split into tranches
TranchesA settlement split in parts
Each part has its own status and record.
5.3 · Settlement history
Show earlier dishonoured settlements before anyone decides.
What I saw
A customer could accept a settlement, not pay, and come back a few months later asking for another one. The approver had no easy way of knowing.
What I did
The system checks the history automatically and shows any dishonoured settlement right on the approval screen. Every request also keeps its full record, so audit doesn’t have to chase anything.
REPLACE: History flag in approval viewDishonour History Check
The request view is where a settlement can be followed from the first step to the last payment, with its approval progress alongside.
REPLACE: Main solution screenshotFull request view with approval progress
07 · Delivery
We started before the PRD.
I worked with both PMs from the start, before there was a spec.
Rough flows first. We used FigJam sketches, later cleaned up in Figma, to talk things through, and a lot of it went into the PRD.
Edge cases with engineering. During the build, I went through them with the seven engineers.
Checked before UAT. I reviewed each screen before UAT, so the final product matched the plan.
What shipped
Step-by-step request creation, with the mandatory documents uploaded in the flow
Approvers found automatically from the Waiver Authority Matrix
Live approval tracking, and send back with comments
Month-end expiry for requests that have gone stale
A payment link for every tranche, with payment status as it happens
Earlier dishonoured settlements shown on the approval screen, and a complete history on every settlement
08 · Results
Requests move in a day, and nobody is chasing them over email anymore.
<24h
to process a request
Before2–3d
Now<24h
Requests now take under a day, down from 2 to 3 days.
Email threads and manual chasing are gone, so a request keeps moving.
₹15–20 Crof settlements a month, through one process that audit can follow
4 → 1
systems for one settlement
EmailExcelOASLMS→Collection Central
One workflow instead of four tools stitched together by hand.
A settlement now starts, gets approved and gets paid without leaving Collection Central.
100%
requests with a full audit trail
Before
Now
Audit has what it needs, on every request.
Documents are attached before the first approver sees a request, and approvers see earlier dishonoured settlements before they approve, not after.
What I learned
Fixing one team’s part doesn’t fix the whole process.
Collections is now digital from request to payment. But once the customer pays, Operations still reconciles that payment by hand. Next, I would make a payment land in LMS and the settlement close itself in Collection Central, with no spreadsheet in between.
The rules were most of the job.
I spent more time understanding how a settlement gets approved than drawing screens for it. Approval rules, month-end numbers and UPI limits were where the problems were. Once those were clear, the screens could be simple.
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.