Glossary · Industry vocabulary

Co-lending

Co-lending is an arrangement where two or more lenders fund the same loan in a fixed ratio, sharing risk and return on a per-loan basis.

  1. One borrower receipt
  2. Allocate under the agreement
  3. Separate partner ledgers
Illustrative example

A ten lakh rupee loan funded 70:30 by a bank and an NBFC, a ratio chosen for the example rather than set by any rule. An EMI of 25,000 rupees lands in the escrow account. The platform allocates it to interest and principal on the blended schedule, splits each component 70:30 into the two lenders' ledgers, applies each lender's own rate to its own share, and writes one settlement entry against the escrow account. If the borrower later turns SMA-1 on the NBFC's book, the bank's share carries the same status the next working day. The MIS both partners read is a report over those postings, not a reconciliation of them.

The model is most prominent in India, where the Reserve Bank of India's Co-Lending Arrangements Directions, 2025 replaced the 2020 priority-sector framework from 1 January 2026. Each co-lender keeps at least 10 per cent of every individual loan on its own books. Disbursements and repayments run through an escrow account with a bank. Classification is borrower-level within the arrangement: a default in the co-lent exposure that makes one lender classify it SMA or NPA carries the same status onto the other lender's share, and the information passes between them by the end of the next working day at the latest. What the 2025 Directions change after disbursal covers the servicing work this creates. Each lender reports its own share to the credit bureaus. The Directions now sit inside RBI's consolidated NBFC directions on transfer and distribution of credit risk. Outside India the closest equivalents are loan participations and forward-flow arrangements, where one lender originates and another holds part or all of the exposure.

Operationally, co-lending is a servicing problem more than an origination one. Every repayment has to be split in the agreed ratio, interest accrues at two rates on two books, charges and waivers need a rule for who bears them, and the partner MIS has to reconcile to each lender's ledger at month end. A lender running co-lending on a single-tenant LMS spends its reporting cycle in spreadsheets. A platform that models the partnership as a first-class entity in its data model does the split at posting time instead. See co-lending in the embedded finance stack for how that looks in practice.

What is the difference between co-lending and a loan participation?

In co-lending both lenders are party to the loan from the start, each holds its share on its own books, and the borrower usually sees one blended rate and one repayment. In a loan participation the lead lender originates and holds the loan, then sells an interest in it to a participant, who typically has no direct relationship with the borrower. The economics can look similar. The servicing does not: co-lending needs a per-loan split on every event, a participation needs a periodic remittance.

Who services a co-lent loan?

Whichever lender the agreement names, and it has to name one. Where an NBFC originates the loan and faces the borrower, servicing and collections usually sit with it, and the bank relies on the NBFC’s records. That makes the NBFC’s loan management system a bank-side risk, especially now that classification has to be shared by the next working day, which is why agreements spend so much space on data access and audit rights.

Why is co-lending hard for a legacy LMS?

Because a legacy system was built around one lender and one loan. Modelling a second owner means either two loan accounts that have to be kept in step by hand, or a custom split layer bolted on beside the ledger. Both push the reconciliation into spreadsheets, and both break the moment a waiver, a part-prepayment or a write-off has to be shared in a ratio the system never expected.

Founder-led adoption

Adopt the agentic loan servicing platform.

Lokta is built for enterprise deployment, VPC or single-tenant cloud, with an audit trail in every state change. We work with a select group of institutions through a founder-led model: deep adoption, deliberate scope, a delivery window the team commits to in writing.