For small lenders and NBFCs
Move the loan book beyond spreadsheets
For books under ₹100 crore, Lokta brings schedules, receipts and days past due onto one loan record after approval. Your team can trace the account without depending on one person’s spreadsheet.
- No minimum book size
- Tally stays for your books
- Hosted for you, no servers
Built by the team that helped create Apache Fineract, the open-source lending core, and later built and scaled a commercial lending platform on it.
Where Excel stops
Each new loan adds rows that someone has to check by hand
The spreadsheet does not fail on one day. It gets slower to open, the copies multiply, and the checking lands on the one person who already carries the RBI relationship.
01 Repayment schedules
In the spreadsheet
A part-prepayment, a moratorium or a broken first period means rebuilding the schedule by hand, and checking it again before the borrower sees it.
On the loan record
The engine computes each schedule to the paise from the product you configure, broken periods and moratoria included, and recomputes it when the loan changes.
02 Interest and charges
In the spreadsheet
Daily interest, penal charges and waivers live in formulas that one person wrote and one person understands.
On the loan record
Interest method, day-count and charges are product settings. Penal-charge rules follow the RBI 2024 directions as configuration, so the same inputs give the same numbers every time.
03 EMI working and receipts
In the spreadsheet
Each receipt is matched to a borrower and split across principal, interest and charges by hand. A late or short payment breaks the row below it.
On the loan record
Receipts apply to the loan through the appropriation order you set. Unmatched money goes to a suspense queue with an owner, where you can see it.
04 DPD and the bucket view
In the spreadsheet
Days past due is a column someone updates. A bucket-wise analysis for the board is a weekend with pivot tables.
On the loan record
DPD is derived from the loan record, SMA and NPA classification runs on the RBI IRAC rules, and the book segments into DPD buckets without a pivot table.
05 What the RBI asks for
In the spreadsheet
When an inspection or a return needs loan-level figures, you assemble them from the file and hope the copy you opened is the current one.
On the loan record
Balances, DPD, classification and accounting entries come from one ledger, with maker-checker and an audit trail on every change from the first loan.
How the move works
Three steps from the spreadsheet to one record
Apply and show us the file
Send your product terms and the layout of the spreadsheet you run today. The demo runs on loans like yours.
Move the book and check it
Lokta configures your products and moves the existing loans across. Someone who knows the book checks the migrated schedules against the spreadsheet before you switch.
Run the book from one record
Schedules, receipts and DPD come from the loan record. Accounting entries export to Tally, so your accountant keeps the books where they are.
Plan for the checking time as well as the setup. How we work sets out each step from the first call to go-live.
What moves and what stays
Lokta takes the loan after approval. The decisions stay with you.
You still run the book. Lokta covers the record it runs on: a deterministic core computes the schedule and posts every event, and a named person in your team approves the changes your policy says need approval.
Moves onto Lokta
- The loan record from disbursal: schedule, receipts, interest, charges and closure
- DPD, SMA and NPA classification, and collections follow-up on the loan itself
- Accounting entries for every loan event, exported to Tally for your books
- Regulatory and investor reporting, portfolio dashboards and early warning
- Credit bureau reporting, roles, maker-checker and the audit trail
Stays with your NBFC
- Sourcing, underwriting and the credit decision, in your LOS or your partner lender’s
- Your credit and collections policy, and who approves an exception
- Your general ledger in Tally, if that is where your accountant keeps it
- Your RBI filings and the accountability that goes with them
What lenders said
Smaller lenders on what they saw in the demo.
At the end of the demo
“You have covered all the pain points of the smaller NBFC.”
On why Lokta starts after sanction
“The post-sanction area is the one which still today remains a grey area.”
After the portfolio dashboards
“This kind of concise and clear dashboard I never saw.”
On the partner and payout view
“Traditional systems never had something like this.”
On seeing bucket roll-back and roll-forward at account level
“My team takes half a day today just to get this data out manually.”
Asked when he wanted servicing automated
“At this point, I can start within a month.”
The Starter tier, Lokta Next 100
Built for books under ₹100 crore
Starter is the tier for lenders below the ceiling, including a fresh licence with no loans yet. It includes credit bureau reporting and email and phone support. The current fees and terms are published on the pricing page.
Three ways forward
Pick the path you can defend to your board and to the RBI
Keep the spreadsheet
No new cost today. The checking grows with every loan, and it stays with one person.
The one we built for
Move the book onto Starter
Schedules and DPD from one record, Tally export for your accounts. You give time to checking the first schedules, and pay migration if you bring a book.
Hire another person to check the file
More hands on the same spreadsheet. The book still has no single record when the RBI asks for one.
Questions from small lenders and NBFCs
Book size, cost, Tally, support, RBI returns, growth past the ceiling and origination.
Is a book of a few dozen loans too small to move off Excel?
No. Starter has no minimum book size, and a newly licensed NBFC with no loans yet can start on it. A small book is also the quickest one to migrate, because there are fewer schedules to check against the spreadsheet before you switch.
What does it cost?
Starter is the tier for books under the ceiling, and its current fees, including any one-time migration or bank integration fee, are published on the pricing page. The fees are set there so this page never shows a stale figure.
Do we have to stop using Tally?
No. Tally can stay where your accountant keeps the general ledger. Lokta holds the loan-level record and generates the accounting entry for each loan event, and those entries export to Tally. What changes is that the entries come from the loan record instead of being typed in from a spreadsheet.
We have no IT team. Who keeps the system running?
Lokta is hosted in-region on AWS, so there are no servers for you to buy or patch. Email and phone support are included in Starter. Your team works in the application; Lokta looks after the platform underneath it.
Does Lokta prepare our RBI returns on CIMS?
Lokta keeps the loan-level figures that the returns draw on: balances, DPD, SMA and NPA classification, and the accounting entries behind them, all from one ledger. Your NBFC still prepares, reviews and files each return, and stays accountable for it.
What happens when our book grows past ₹100 crore?
Nothing moves. The book stays on the same platform and the same ledger, and billing moves to the published rate for the next tier. The pricing page sets out when that starts.
Our partner lender sources and approves the loans. Does that work?
Yes. Lokta takes each loan after approval. Your partner lender’s system, or your own LOS, hands the approved loan over through an API, and servicing starts from there. Loan Origination is on the roadmap and is not available now. No release date is published.
Who owns the loan data once it is on Lokta?
You do. The data is exportable, and it is never used to train models for anyone else.
Does Lokta report to the credit bureaus for us?
Yes. Credit bureau reporting is included in the Starter tier, alongside email and phone support.