Rupit
Finance · by Oadbox
The complete platform for microfinance companies
Loans, savings, chitfunds and field collections for NBFCs, co-operative societies and microfinance institutions.
At a glance
- 9+ loan types
- Web + field app
- Per-org isolation
Built for
NBFCs, microfinance institutions and co-operative societies across India.
Live at
rupit.inThe problem
Used by field officers, branch managers and the risk desk.
Collections happen on a two-wheeler, in villages with no signal, on a phone at eighteen per cent — and the cash recorded there is the highest-risk transaction in the business.
Rupit digitises operations that still run on ledgers and receipt books. Nine-plus loan types, savings products, chitfunds and daily field collections all live in one multi-tenant platform with a matching mobile app.
Collections are the hard part, so they get the most attention: cash, UPI, bank transfer or cheque, receipted on the spot, reconciled centrally, visible in overdue reports the same day.
A day on Rupit
One collection day, first round to cash-up
Lending software gets demoed in the head office, but it earns its keep on the back of a two-wheeler, at a shop counter and in the branch cash box at close. This is where Rupit sits in a normal working day.
What we counted first
Rupit began the way every Oadbox product does — sitting in branch offices through a collection round, an auction day and a month-end close. Four numbers kept coming back:
5
Books behind one instalment
Collection sheet, receipt counterfoil, subscriber passbook, day book, ledger — the same ₹200 written five times before anyone called it received.
2.5 hrs
Branch cash-up after close
Agents drifted back from six onwards, and the branch could not lock up until every sheet was added by hand and matched against the cash box.
1 in 9
Passbooks that disagreed with ledger
We spot-checked pigmi passbooks against the branch ledger. Roughly one in nine carried a missed or duplicated entry that nobody had caught.
11 days
Month-end to overdue list
The ageing report existed, but only after eleven days of a clerk carrying balances forward — by which time the field had already moved on.
Counted across our own early branch visits, before Rupit existed. Every institution differs — your numbers are the first thing we ask about.
- 7:15 am
Before the round
The shutters are half up and four field agents are checking their phones before the two-wheelers leave. Each has the day's list already on it — which pigmi accounts, which daily-loan instalments, which three houses are behind — instead of a sheet ruled out by hand from last night's ledger.
- 9:40 am
A shop counter
A vegetable seller on the round pays ₹200 against her daily loan and ₹100 into pigmi, today by UPI from the phone in her apron. The agent captures it on the field app and the receipt is generated on the spot, so nothing waits to be copied into a passbook back at the branch that evening.
- 11:10 am
The gold loan counter
At the branch, a customer sits down at the counter with two bangles and her KYC papers. The loan goes onto one record — documents, disbursal, then an EMI schedule computed against the terms already on it, with penalties and foreclosure handled the same way — instead of a clerk building the schedule in a formula sheet.
- 1:00 pm
The auction hall
Chit Group C meets in the room behind the branch — thirty-eight subscribers, the monthly auction that has run the same way for years. Bids are entered as they are called out, and the prize amount, each subscriber's dividend and the foreman's commission come off the same record rather than a register written up after the hall empties.
- 3:15 pm
The savings desk
A pigmi subscriber comes in to see where his account stands before a wedding. The clerk pulls up the statement — every daily ₹100 the agent collected on the round, and the interest posted against it — rather than counting back through passbook pages that may or may not agree with the ledger.
- 5:40 pm
The branch cash-up
The agents come back in and the cash box comes out. What each of them collected is already on the system, so the manager is counting notes against a total that exists rather than adding four collection sheets together to find out what the total should have been. Cash, UPI, bank transfer and cheque all sit in the same day's figure.
- Month-end
The portfolio review
Overdue ageing, collection trends and portfolio health are on one screen on the first of the month, not the eleventh. Head office and the branch are reading the same figures, with the six access levels deciding who sees which branch — so the review opens with a decision instead of a week of compiling.
What quietly disappears
None of this is dramatic. It is the same collection day — minus the artefacts everyone assumed were permanent.
The carbon-copy receipt book in the agent's bag
The collection sheet ruled by hand each morning
The EMI schedule worked out on a formula sheet
The chit auction register written up after the hall empties
The overdue list retyped from the ledger at month-end
Key workflows
What it actually runs.
Loans of every shape
Personal, gold, vehicle, property, business, agriculture, education, daily and group loans on one engine.
Automated EMI scheduling
Schedules, interest computation, penalties and foreclosure handled by the system, not a formula sheet.
Savings products
Pigmi collections, recurring deposits and fixed deposits with maturity and interest posting.
Full chitfund lifecycle
Groups, auctions, dividend distribution, commission tracking and subscriber statements.
Field collections
Cash, UPI, bank transfer and cheque captured on mobile with auto-generated receipts.
Portfolio analytics
Portfolio health, overdue ageing and collection trends reported without a month-end scramble.
Six levels of access control
Granular role-based permissions from branch agent up to head office.
Multi-tenant by architecture
Per-organisation data isolation and custom branding on both web and app.
Why Oadbox
We know the industry
Rupit was designed inside finance operations, not adapted from a horizontal tool.
How finance worksIt runs on our core
Tenancy, permissions, statutory compliance, offline mobile and audit trails are inherited, not rebuilt for each product.
Inside the platformWe still operate it
The team that built Rupit runs it — monitoring, support, releases and the next version.
How we workMore from Oadbox
11 other products, same foundation.
Want to see Rupit on your own data? That is the only demo worth having.
Thirty minutes with someone from the product team — how you work today, and an honest answer on whether this fits.