Your credit manager flags a loan application during morning review. The borrower has been with you for three years, maintains 100% repayment consistency across two existing loans totalling ₹80 lakh, and now needs ₹2 crore for warehouse expansion. Your exposure limit for this borrower: ₹1.5 crore.
Walking away means handing a relationship you built to a competitor. Approving ₹2 crore means breaching your single-borrower exposure norms and inviting regulatory scrutiny. Offering only ₹1.5 crore means the client goes elsewhere anyway because they need the full amount.
This isn’t a credit decision problem. This is a capital constraint problem that co-lending was designed to solve.
Why Exposure Limits Bind NBFCs
RBI’s exposure norms cap single-borrower lending at 25% of Tier I capital for NBFCs, with a 25% ceiling for infrastructure finance companies. These limits exist to prevent concentration risk in loan portfolios. If one large borrower defaults, the NBFC’s capital base shouldn’t be severely impaired.
For an NBFC with ₹100 crore in Tier I capital, the single-borrower exposure limit sits at ₹25 crore. That sounds substantial until you consider that growing MSMEs routinely need ₹5-10 crore tickets for expansion, equipment purchases, or working capital. Service multiple such clients, and you hit aggregate exposure constraints quickly.
Why Traditional Workarounds Don’t Solve the Capital Constraint Problem
Referring the client to a partner bank seems straightforward until you lose origination fees, servicing revenue, and relationship control. The client remembers that you couldn’t meet their needs at a critical growth moment. Future, smaller requirements might still go to the bank that stepped in during expansion.
Structuring the requirement as multiple smaller loans with creative documentation invites regulatory issues around evergreening and exposure norm violations. Examiners specifically watch for such arrangements during inspections.
These workarounds either damage relationships or create compliance exposure because they don’t address the fundamental capital constraint.
This is why co-lending workflows require system architecture specifically designed for multi-lender structures rather than retrofitted workarounds in traditional LMS platforms.
How Co-Lending Addresses Capital Constraints
Co-lending partnerships between NBFCs and banks allow you to originate loans beyond your exposure limits while sharing risk and funding with a banking partner. RBI’s November 2020 guidelines (updated periodically) established the framework for these arrangements.
Here’s the operational flow. You originate the ₹2 crore MSME loan using your existing underwriting models, credit assessment frameworks, and customer relationships. The bank contributes 80% of the loan amount (₹1.6 crore) while you contribute 20% (₹40 lakh). Both entities maintain their portions on their respective books.
The borrower sees one loan with one repayment schedule. Your LMS generates the collection schedule, processes repayments, and distributes funds to both lenders according to the agreed ratio. You continue servicing the relationship, handling queries, managing documentation, and maintaining the primary client interface.
The bank gains MSME access without building origination infrastructure. You maintain the client relationship while deploying only ₹40 lakh instead of ₹1.5 crore.
You don’t breach exposure limits because your on-book exposure stays at ₹40 lakh. The client receives their full ₹2 crore requirement. The bank deploys capital into pre-assessed MSME loans.
Implementation Requirements for Co-Lending Operations
Co-lending creates specific operational requirements because two lenders must maintain synchronised loan records while operating independent systems.
1. Disbursement Coordination
When the ₹2 crore loan gets approved, your LMS must trigger simultaneous disbursements from both lenders’ accounts. If your share disburses on Day 1 but the bank’s share disburses on Day 3, the borrower experiences a funding gap and your relationship suffers.
2. Repayment Reconciliation
The borrower makes one EMI payment to one collection account. Your system must split that payment proportionally, route 80% to the bank’s account and retain 20%, then update both loan records to reflect the payment. Any lag in this reconciliation creates discrepancies between your LMS showing one outstanding balance and the bank’s CBS (Core Banking System) showing another.
3. Bureau Reporting
Both lenders must report their respective portions to credit bureaus with identical data points for Days Past Due (DPD), outstanding amounts, and payment status. If your system reports the loan as current but the bank reports it as 30 DPD, bureau records become ambiguous.
4. NPA Classification
When a co-lending loan becomes delinquent, both lenders must follow synchronised Non-Performing Asset (NPA) classification timelines. Your 90-day NPA recognition policy must align with the bank’s classification schedule, even if your internal policies differ for other loan categories.
5. Documentation Management
Loan agreements, hypothecation documents, and security creation involve both lenders. Any amendments, restructuring, or settlement discussions require coordination. If the borrower requests a tenure extension, both entities must approve the modification and update their respective systems simultaneously.
System Architecture for Co-Lending Workflows
Managing co-lending relationships requires your LMS to handle multi-lender loan structures as a native capability rather than through manual workarounds.
Event-driven architecture becomes essential. When a repayment hits your collection account, the system must automatically trigger fund transfers to partner banks, update both internal records and generate reconciliation reports, all within the same processing cycle.
API integration with partner banks’ systems allows real-time data synchronisation. When your LMS marks a loan as 30 DPD, the bank’s CBS should reflect the same status without manual file uploads or email confirmations.
Finezza’s Loan Management System handles co-lending workflows through a multi-ledger architecture where each lender’s share is maintained as a separate sub-loan entity within a unified master loan structure.
When a borrower makes a single ₹2 lakh EMI payment, the system automatically splits ₹1.6 lakh to the bank partner’s account and retains ₹40,000, then updates both entities’ loan records and generates synchronised bureau submission files in the same processing cycle.
Operations teams see one borrower interface while maintaining separate compliance trails for each lender.
Beyond Capital Constraints
Co-lending solves the immediate problem of serving clients beyond your exposure limits. The broader impact comes from transforming your lending capacity without proportional capital raises.
If your ₹100 crore capital base limits you to ₹25 crore per borrower, ten large MSME clients at ₹25 crore each would require ₹250 crore in deployment capacity.
With co-lending at 20% participation, those same ten clients require only ₹50 crore of your capital, freeing up ₹200 crore for additional origination.
That ₹2 crore warehouse expansion your client needs? You approve it, structure it with your banking partner, maintain the relationship, and deploy only ₹40 lakh of your capital. The alternative was losing the client entirely.
Finezza’s co-lending module addresses these requirements through configurable partnership templates that define ratio splits, disbursement sequencing, and automated reconciliation rules.
When you structure your first bank partnership for MSME lending, the system captures the 80/20 split, triggers simultaneous disbursements from both accounts, and maintains synchronised DPD tracking across your LMS and the partner bank’s CBS. Scale that to three banking partnerships across different loan products, and the unified dashboard shows you consolidated portfolio analytics while maintaining separate compliance reporting for each partnership.
Book a demo to see how your NBFC can scale lending capacity without proportional capital raises.
Leave a Reply