Why RBI's 2025 Rules Change What Your Software Needs to Do

The regulatory ground under microfinance lending has shifted twice in the last few years, and both changes affect what your software needs to track. The foundation is the Master Direction – Reserve Bank of India (Regulatory Framework for Microfinance Loans) Directions, 2022, effective April 1, 2022, which applies uniformly to commercial banks, cooperative banks, and NBFCs offering microfinance loans.

In March 2022, the RBI moved to a common regulatory framework for microfinance loans across banks, small finance banks, and NBFCs, removing interest-rate caps in favour of a board-approved pricing policy and setting a household income-based structure with a fixed household indebtedness ceiling. The revised guidelines also dropped the old rural-versus-urban distinction and set a uniform annual household income limit of ₹3 lakh for defining a microfinance loan nationwide, along with a 50% cap on total monthly debt-servicing obligations relative to household income. That change means your software's underwriting module needs household-level income and exposure tracking built in, not bolted on later.

The qualifying-asset threshold has also moved. A June 2025 RBI notification revised the qualifying-asset criteria for NBFC-MFIs so that at least 60% of total assets (excluding intangible assets) must be qualifying assets on an ongoing basis, down from the earlier 75% requirement. Miss that threshold for four consecutive quarters and the NBFC-MFI has to submit a remediation plan to the RBI. Separately, the threshold governing how much of a general-purpose NBFC's book can consist of microloans without triggering NBFC-MFI registration has also been revised upward in recent cycles — confirm the current figure against RBI's live Master Direction page before treating any percentage as fixed.

More recently, the RBI notified the Non-Banking Financial Companies – Microfinance Institution (NBFC-MFI) Directions, 2025, which consolidate the regulatory framework for microfinance-focused NBFCs under scale-based regulation, covering governance, prudential norms, capital adequacy, asset classification, and credit bureau reporting.

On data, RBI's digital lending guidelines require borrower data collected through a digital lending process to be stored only in India, with explicit consent, and not shared with third parties without that consent. The Digital Personal Data Protection Act, 2023 adds further obligations on top of this, and existing sectoral rules generally apply over and above the DPDP Act where they prescribe a higher degree of protection. The exact scope can differ by an institution's regulatory category and business model, so confirm applicability to your specific entity type rather than assuming a blanket rule.

What this means practically: your software has to compute qualifying-asset ratios automatically, flag household indebtedness before disbursement, maintain an auditable pricing policy trail, keep borrower data hosted in India, and push data to credit bureaus in the format regulators expect. A generic loan management tool that wasn't built around these specifics will need heavy customisation to get there, or it won't get there at all.

Verify live: RBI Master Directions are amended periodically. Confirm the current in-force version and any subsequent circulars before finalising software requirements for your institution.

Who This Is Built For

This kind of platform fits organisations that lend at volume through structured group or individual microfinance models:

If your institution fits more than one row, that's normal — this is one platform, not six separate tools stitched together.

If your lending book is small (a handful of branches, a few hundred active borrowers) and mostly individual loans, a lighter loan management tool may cover you for now. The case for dedicated microfinance software gets stronger once you're running group liability models, multi-branch collections, or credit bureau reporting obligations.

Core Modules You Need

Complete Feature List

Onboarding & Identity

• Digital KYC with Aadhaar and PAN verification
• Video KYC for remote onboarding
• Biometric registration for field-verified members
• OCR-based document capture, reducing manual data entry from photographed documents
• eSign for loan agreements and consent forms
• eMandate / NACH setup for recurring EMI debits

Collection

• Field collection app with offline capture and controlled sync once connectivity returns
• WhatsApp-based repayment reminders and collection confirmations
• Delinquency alerts and automated follow-up reminders

Customer Experience

• Borrower self-service portal (loan status, repayment schedule, statements)
• Mobile app for members alongside the field officer app
• SMS and WhatsApp notification engine for disbursement, EMI due dates, and receipts

Feature availability can vary by plan tier. Confirm the exact feature set for your selected plan during the demo.

Modules Beyond Lending

A lending institution runs on more than loan data. The platform can extend into the operational modules branches actually need day to day:

Confirm which modules are included in your plan versus available as an add-on.

API & Integrations

Buyers evaluating microfinance software almost always ask the same question: can it talk to the systems we already run. The honest answer depends on the integration:

• REST API for connecting external systems to core loan data
• Webhooks for real-time event notifications (disbursement, repayment, status change)
• Accounting API for syncing with external books-of-account software
• Credit bureau APIs: CIBIL, CRIF High Mark, Equifax, Experian
• Payment gateway and UPI integration for digital collection
• NACH for automated recurring debits
• SMS and WhatsApp Business API for notifications

Ask for a live API demonstration rather than a features list. A working webhook that fires on a real disbursement event tells you more than a bullet point ever will.

Technical Specifications

This table reflects the general architecture buyers should expect from a cloud-first platform. Confirm exact specifications, including current iOS app status and backup SLAs, directly before finalising a purchase decision, since these details change as the product evolves.

Security

• Role-based access control (RBAC) by user type and branch
• Two-factor authentication (2FA) for login
• Continuous audit trail on every transaction and record change
• Encryption in transit (SSL/TLS) and at rest
• Automated backups and disaster recovery planning for business continuity
• India-based hosting aligned with RBI data localization requirements

For enterprise buyers who need to see formal certification (ISO 27001, SOC 2) or recent VAPT/penetration-test reports, ask the vendor directly for current documentation rather than relying on marketing claims from any vendor, including this page.

Compliance Documentation the Software Must Support

The software itself doesn't file paperwork with the RBI, but it needs to generate and retain records your compliance team will be asked for:

• KYC records and digital consent trails for every borrower and group member
• Household income and indebtedness worksheets — enforcing the ₹3 lakh annual household income cap and the 50% repayment-obligation cap at the point of underwriting, not after
• Board-approved interest rate and pricing policy documentation, version-controlled
• Qualifying-asset ratio calculations, tracked quarterly
• NPA classification and provisioning records
• Credit bureau submission logs (CIBIL, CRIF High Mark, Equifax, Experian, as applicable)
• Audit trail exports for RBI or statutory audit requests
• Data-localization and consent records showing borrower data was collected, stored, and shared in line with RBI's digital lending guidelines and the DPDP Act

Ask any vendor to show these checks running live against a sample loan rather than describing them in a slide.

Verify live: exact document retention periods and formats should be confirmed against the current RBI Master Direction and your auditor's requirements, since these are periodically updated.

How Implementation Works

1. Requirement mapping. Document your current loan products, group structures, branch count, and approval hierarchy before configuration starts.
2. Data migration. Existing borrower, group, and loan data is cleaned and imported from your current system (Excel, legacy software, or paper records), validated against a sample reconciliation before full migration.
3. Configuration. Loan products, interest structures, approval workflows, report formats, and user roles are set up to match how your institution actually runs, not a generic template.
4. Bureau and API integration. Credit bureau connections, payment gateway, NACH, and any core banking or accounting integrations are wired in.
5. User training. Separate tracks for field officers, branch staff, and head office, typically including the mobile app.
6. Parallel run. At least one full collection cycle running alongside your existing process before full cutover, to catch data or workflow gaps early.
7. Go-live and support. Full cutover, with responsive support through the first month, when real-world edge cases surface.
8. Ongoing. AMC, continued training for new staff, and a defined support and warranty window post-launch. Confirm AMC terms and support-response SLAs directly before signing.

Pricing

Pricing for microfinance software in India is typically driven by a combination of active loan accounts, branch count, and user seats, along with which modules you need — credit bureau integration and mobile apps for field staff are usually priced separately from the core platform. Plans are generally structured across three tiers:

Confirm current rates with LegalDev directly for your branch and borrower volume; we're not listing a fixed number here because it varies enough by deployment size that a generic figure would be misleading. GST applies additionally on software services per standard rules.

Implementation Timeline

Smaller single-branch deployments can move faster, sometimes in a few weeks; large multi-state rollouts with heavy legacy data cleanup will run longer, sometimes a few months. Treat any vendor quote of "go-live in 3 days" with scepticism unless your data is already clean and your product structure is simple.

Manual Systems vs. Purpose-Built Software

Purpose-Built vs. Generic Loan Software vs. Core Banking

Core banking platforms aren't a bad choice for a large bank. They're usually the wrong tool for a microfinance-specific lender, since group lending, center meetings, and field-first collection aren't what they're built around.

Common Mistakes MFIs Make When Choosing Software

• Buying on feature-list length instead of workflow fit. A long feature list means nothing if the group-lending workflow doesn't match how your SHGs actually operate.
• Skipping the data migration conversation until after signing. Migration complexity is often where timelines and costs blow up; ask about it before you commit, not after.
• Not confirming credit bureau integration is live and tested, rather than "available on request."
• Underestimating field staff training time. A system that's intuitive to a branch manager can still be unfamiliar to a loan officer who's used paper registers for years.
• Ignoring offline capability for branches in low-connectivity areas, then discovering field data doesn't sync reliably.
• Treating add-ons as an afterthought. Payment gateway integration, bureau charges, and mobile apps are frequently priced and timed separately; get all of it in writing upfront.

Pro Tips Before You Sign a Contract

• Ask for a reference client running a similar branch count and loan mix, not just a generic case study.
• Request a sandbox or demo environment configured with your actual loan products, not a stock demo.
• Get the qualifying-asset ratio calculation logic explained in plain terms; this is the single most consequential compliance number in your portfolio right now.
• Ask for a live demonstration of the household income cap and repayment-obligation cap checks running against a sample loan, not a slide describing them.
• Confirm data ownership, export terms, and where borrower data is physically hosted in writing before migration begins, not after you're locked in.
• Check what happens to your data and access if you switch vendors later; export formats and lock-in terms vary widely.

Why Work With LegalDev

LegalDev works with Indian businesses on registration, compliance documentation, and structured operational setup, which puts us in a position to align your microfinance software requirements with what RBI compliance actually demands, rather than treating the two as separate projects. We can help scope requirements, review vendor proposals against current RBI directions, and support the compliance documentation side of implementation.

• Cloud-based, hosted to align with RBI data localization requirements
• RBI-ready compliance checks built into the origination workflow
• Mobile app for field officers and members
• Multi-branch architecture from day one, not bolted on later
• Custom modules for institutions that don't fit a generic template
• API access for institutions that need to connect existing systems
• PAN-India support model

Explore LegalDev's compliance services →

Frequently Asked Questions