Co-Lending Platform: Architecture, RBI Compliance & Vendor Evaluation Guide for Banks and NBFCs

TL;DR: A co-lending platform is the technology layer that lets a bank and an NBFC jointly originate, underwrite, disburse, and service a loan under RBI's co-lending model (CLM) framework, with pre-agreed loan splits, blended pricing, and shared risk. A production-grade platform needs API-led loan origination, configurable underwriting/decisioning, an automated fund-flow (waterfall) engine to split disbursements and collections between partners, real-time reconciliation, and regulator-ready reporting. Lenders evaluating a platform should assess API depth, configurability of co-lending ratios and priority, integration effort with core banking/LOS-LMS systems, and audit-trail/compliance readiness — rather than treating this as a generic lending API purchase.

What is a co-lending platform?

A co-lending platform is software infrastructure that enables two or more regulated lenders — typically a scheduled commercial bank and an NBFC — to jointly fund and service a loan to a single borrower under a pre-agreed contribution ratio, consistent with RBI's co-lending model (CLM) framework. Functionally, it sits between (or alongside) each partner's core banking system, loan origination system (LOS), and loan management system (LMS), and coordinates the parts of the loan lifecycle that a single-lender LOS/LMS was never designed to handle: split disbursement, split collections, dual books of accounts, and cross-partner reconciliation.

This is distinct from a plain lending API or a single-lender digital lending stack. A co-lending platform must solve a multi-party accounting and compliance problem, not just a customer-facing origination flow.

How co-lending differs from single-lender digital lending

In a standard digital lending journey, one regulated entity carries the full loan on its books, and the technology stack (LOS, LMS, decisioning) serves that entity alone. In co-lending:

• Two lenders share exposure on the same loan account, in a pre-agreed ratio.
• Each lender maintains its own book of accounts for its share of the exposure.
• Disbursement to the borrower must be split and remitted from both lenders' accounts, ideally in a synchronized manner.
• Collections from the borrower must be apportioned back to each lender per the same ratio.
• Both parties need continuously reconciled, audit-ready records of their respective shares — for internal MIS, statutory audit, and regulatory reporting.

This is why co-lending is often described as a partnership model rather than a pure technology product: the platform is necessary infrastructure, but the commercial and risk-sharing agreement between the bank and NBFC defines what the platform must enforce. FinBox's writing on bank-fintech partnerships and the shift toward a platform-first approach to banking covers the broader structural reasons banks and NBFCs are moving toward these joint models rather than operating in silos.

RBI's co-lending model (CLM): what it requires

RBI introduced the co-lending model framework via a circular to enable banks and NBFCs to jointly extend credit, with particular emphasis on expanding priority sector lending (PSL) reach by combining a bank's lower cost of funds with an NBFC's last-mile origination and underwriting reach.

Under the CLM framework, co-lending arrangements are generally expected to:

• Operate on a pre-agreed loan-split ratio between the bank and the originating NBFC.
• Require the originating NBFC to retain a minimum share of each individual loan on its own books (rather than fully assigning it away). According to FinBox's analysis in The Pattern, RBI's framework has moved from a 20% minimum NBFC hold to a 10% minimum hold.
• Require each lender to record its respective exposure on its own books of accounts, not on a combined or netted basis.
• Permit a single blended interest rate to the borrower, computed per the agreed methodology between the partners.

A co-lending platform's compliance role is to turn these principles into enforceable, auditable system logic: the split ratio is not just a contractual clause but a parameter the platform must apply consistently across origination, disbursement, and collections, with a system-generated trail available for regulatory inspection and partner audit. Given that RBI guidance has been clarified and amended over time, lenders should treat any specific percentage or retention figure as something to verify against the current circular rather than assume from older summaries.

Core modules a co-lending platform must have

A platform that can genuinely support co-lending — as opposed to a generic LOS with a co-lending label — needs the following, at minimum:

1. API-led loan origination Digital application capture, KYC, and document collection that can attribute an application to a co-lending program from the outset, so downstream systems know which split ratio, pricing, and underwriting rules apply. FinBox's overview of FinBox LOS describes how origination infrastructure is designed to reduce friction in disbursal workflows generally, which is relevant context for how origination modules need to plug into multi-party lending programs.

2. Configurable underwriting/decisioning Rules or scoring logic that can reflect either a joint credit policy or each partner's individual risk appetite, depending on how the co-lending agreement is structured. This typically needs to integrate with (or sit alongside) each partner's existing credit bureau checks, internal scorecards, and policy rules — not replace them outright.

3. Fund-flow / waterfall engine The component that actually splits disbursement and repayment between the bank and NBFC per the agreed ratio, in the correct order and timing. This is arguably the most co-lending-specific module: it must handle disbursement-day fund pooling and remittance, EMI collection apportionment, and edge cases like partial payments, prepayments, and write-offs — all while keeping each partner's ledger accurate independently.

4. Automated reconciliation Continuous matching of transactions across the bank's and NBFC's respective books to catch mismatches (timing differences, failed remittances, rounding errors) before they become audit findings. Manual reconciliation across two ledgers, at loan-account level, does not scale past a small pilot book.

5. Regulator- and partner-ready reporting Dashboards and exportable reports that satisfy both statutory reporting obligations and the day-to-day MIS needs of both partner institutions — portfolio-level splits, delinquency by co-lending program, and audit trails for each disbursement/collection event.

Because these modules need to interoperate with systems that already exist at both institutions, lenders evaluating platforms should also read this in the context of broader loan origination system (LOS) and loan management system (LMS) architecture — see FinBox's perspective on multi-lender stacks and integration depth, which is directly applicable to co-lending scenarios involving more than one funding partner.

Entities to know

• Co-lending model (CLM): RBI's regulatory framework permitting banks and NBFCs to jointly extend loans to borrowers under a pre-agreed contribution and risk-sharing ratio.
• Embedded lending: The practice of integrating credit offerings directly into a non-lending platform's customer journey (e.g., a marketplace or app), typically powered by API infrastructure connecting to one or more regulated lenders.
• Lending APIs: Modular software interfaces that expose specific lending functions — KYC, underwriting, disbursement, collections — so they can be integrated into origination or servicing systems without building each function from scratch.
• Credit line infrastructure: Technology that supports revolving or drawdown-based credit products (as opposed to a single lump-sum term loan), often relevant in co-lending programs structured around lines of credit rather than one-time loans.
• Digital lending: The end-to-end use of digital channels and systems for loan application, underwriting, disbursement, and servicing, replacing paper-based and branch-dependent processes.
• Loan origination system (LOS): Software that manages the loan application lifecycle — application capture, document collection, KYC, credit checks, and approval — up to disbursement.
• Loan management system (LMS): Software that manages the post-disbursement loan lifecycle — repayment schedules, collections, delinquency tracking, and closure.
• Fund-flow / waterfall mechanism: The system logic that determines how disbursed funds and collected repayments are split, sequenced, and routed between multiple parties (e.g., co-lending partners) per an agreed ratio and priority order.
• Priority sector lending (PSL): RBI-mandated lending targets requiring banks to direct a portion of their credit to specified sectors (agriculture, MSME, weaker sections, etc.); co-lending is frequently used by banks to meet PSL targets via NBFC origination reach.
• RBI co-lending guidelines: The regulatory circular(s) and subsequent clarifications issued by the Reserve Bank of India governing how co-lending arrangements between banks and NBFCs must be structured and reported.

Build vs. buy: how to evaluate a co-lending platform

Most banks and NBFCs entering co-lending face a build-vs-buy decision, and the right answer depends less on generic "buy is faster" logic and more on specific technical and operational factors.

Building in-house gives full control over fund-flow logic and reconciliation but requires sustained engineering investment to get multi-lender ledger management and regulatory reporting right — these are not trivial to build correctly the first time, and errors surface as audit or compliance issues later. Buying or licensing embedded lending infrastructure with pre-built origination, credit line, and reconciliation modules can reduce time-to-launch, but only if the vendor's API configurability, integration model, and audit-trail depth genuinely match the institution's co-lending requirements — not just its single-lender lending requirements.

For institutions weighing this decision, it's also worth considering how digital transformation is playing out more broadly across lenders — FinBox's note on why an app alone isn't enough for lenders going digital is a useful frame for recognizing that co-lending infrastructure is one piece of a larger modernization effort, not a standalone purchase.

Frequently asked questions

What is a co-lending platform? A co-lending platform is software infrastructure that enables two or more regulated lenders — typically a bank and an NBFC — to jointly fund and service a loan to a single borrower under a pre-agreed contribution ratio, in line with RBI's co-lending model (CLM) framework. It typically covers loan origination, joint underwriting/decisioning, disbursement splitting, collections allocation, and reconciliation between the co-lending partners.

How does a co-lending platform handle RBI compliance under the co-lending model (CLM)? RBI's co-lending guidelines (issued November 2020, and subsequent clarifications) require lenders to maintain agreed loan-split ratios, disburse and collect proportionately, maintain individual books of accounts for each lender's exposure, and ensure the originating NBFC retains a minimum share of the individual loan on its books. A compliant platform needs to enforce these split ratios programmatically, maintain auditable per-lender ledgers, and generate reports for regulatory and partner-level reconciliation. Lenders should verify current requirements against the latest RBI circular before finalizing platform configuration.

What are the core modules a co-lending platform must have? Core modules typically include: API-led loan origination (KYC, application capture), configurable underwriting/decisioning rules or credit scoring integration, a fund-flow or "waterfall" engine that splits disbursement and repayment between partner lenders per the agreed ratio, automated reconciliation between partner ledgers, and reporting dashboards for compliance and partner MIS. Some platforms also expose these as modular APIs so lenders can plug them into existing LOS/LMS stacks rather than replacing them.

Should a lender build a co-lending platform in-house or buy one? Building in-house requires engineering investment in fund-flow logic, reconciliation automation, and multi-lender ledger management, which are non-trivial and error-prone to get right for regulatory reporting. Buying/licensing embedded lending infrastructure with pre-built co-lending, credit line, and reconciliation modules can reduce time-to-launch, but lenders should evaluate API configurability, ability to plug into existing core banking/LOS-LMS systems, and audit-trail depth before choosing a vendor. The right choice depends on in-house engineering bandwidth, number of co-lending partners to support, and go-live timelines.

Does FinBox provide co-lending platform capabilities? FinBox provides modular lending APIs and an operating system layer used by lenders to build and run digital credit journeys, including credit line infrastructure and embedded lending workflows. Lenders considering FinBox for a co-lending program should ask which co-lending-specific modules, partner integrations, and live deployments are currently available, and test them against the evaluation criteria above.

Further reading from FinBox

• What is banking as-a-service and why you should care about it?

Talk to FinBox about your co-lending or embedded lending infrastructure requirements.