Co-Lending Partner Onboarding: A Go-Live Plan for Lenders
Last reviewed: November 2026
Co-lending partner onboarding is the work of connecting an originating lender with a partner bank or NBFC so both can fund the same loans under one agreement. When the integration is planned late, a signed partnership can sit idle for months while data formats, escrow flows and classification rules are argued over.
This guide is for CEOs, heads of co-lending and CTOs at NBFCs, housing finance companies and banks adding a new co-lending partner. It covers the regulatory points that shape the build, the most common go-live delays, a seven-step onboarding plan, and the metrics that show whether a partnership is ready to scale.
Key Takeaways
- RBI's co-lending framework sets hard system rules: a 10% minimum share, booking within 15 calendar days, escrow routing and next-working-day classification sharing.
- Most go-live delays come from data mapping and testing, not from legal negotiation.
- Run integration work in parallel with the agreement, and write technical timelines into the agreement itself.
- Go live with a capped pilot and a hypercare period, then scale volume once reconciliation is clean.
What Is Co-Lending Partner Onboarding?
Co-lending partner onboarding turns a commercial agreement into a working, joint lending operation. It has two halves: the agreement terms both lenders sign, and the technology that lets loans flow from sourcing to booking, collection and reporting on both sides.
The originating lender usually sources and services the borrower. The partner funds most of each loan and relies on the originator's data, so data quality decides how fast the partnership grows.
Which RBI Rules Shape the Integration?
Five RBI rules shape the integration most: minimum share, booking timelines, escrow routing, classification sharing and separate borrower accounts. RBI first issued them as the Co-Lending Arrangements Directions, 2025 (6 August 2025, effective 1 January 2026), and for NBFCs they now sit in the NBFC Transfer and Distribution of Credit Risk Directions, 2025 (28 November 2025).
| Rule | What the Directions Require | What the System Must Do |
|---|---|---|
| Minimum share | Each lender retains at least 10% of every loan | Enforce the split at loan level |
| Booking timeline | Shares reflected in both books within 15 calendar days of disbursement | Daily loan-level sync with ageing alerts |
| Escrow | Disbursements and repayments routed through a bank escrow account | Escrow-based payment flows and appropriation rules |
| Asset classification | Borrower-level SMA or NPA tags shared by the end of the next working day | Event-based classification feed |
| Borrower records | Each lender keeps the borrower's account for its own share | Mirrored loan accounts on both sides |
The Directions also require disclosure through the key facts statement (KFS), a website list of active partners and a named single point of customer interface. Our guide to the key fact statement for loans explains how those borrower disclosures are generated.
Why Does Co-Lending Partner Onboarding Take So Long?
Co-lending partner onboarding takes long for five reasons: late data mapping, mismatched credit rules, unclear escrow logic, untested classification sync and weak test plans. Each one has a simple prevention check.
| Cause | Effect | Prevention Check |
|---|---|---|
| Data fields mapped after signing | Weeks of rework on both sides | Start the field map with the term sheet |
| Partner's credit criteria held in documents, not rules | Loans offered that the partner rejects | Convert criteria into testable rules early |
| Escrow appropriation left vague | Disputes over who gets each rupee | Write the waterfall into the agreement |
| Classification feed built last | Missed next-working-day sharing | Build and test SMA and NPA events first |
| Only "happy path" testing | Failures on day one of live volume | Test rejections, reversals and part-payments |
The partner's loan selection rules deserve their own design work. This guide covers only how the integration carries them.
What Is the Right Co-Lending Partner Onboarding Plan?
The right co-lending partner onboarding plan has seven steps: agree terms, map data, connect APIs, set up escrow, sync booking and classification, test end to end, and go live in a capped pilot. Running steps two to four while lawyers finish step one saves the most time.
- Agree commercial and operating terms, including technical timelines.
- Map every data field both lenders need across the loan life cycle.
- Connect the APIs or files for each event.
- Set up escrow flows and the appropriation waterfall.
- Sync booking, classification and bureau reporting.
- Test end to end with realistic loans and failure cases.
- Go live in a capped pilot with daily hypercare.
Step 1: What Should the Co-Lending Agreement Fix Before Integration?
The co-lending agreement should fix borrower selection criteria, product lines, fees, roles, information-sharing timelines and grievance handling, because the Directions expect all of these in the agreement. Technology teams should add file and API timings, data formats, reconciliation cut-offs and exception owners.
Fees deserve care, because servicing and sourcing fees flow through the same escrow waterfall. Code fee logic exactly as the agreement states, and test it on real loan examples before signing.
Steps 2 and 3: How Should Data and APIs Be Mapped?
Data and APIs should be mapped event by event, from loan offer to closure. A shared field dictionary avoids the classic dispute where one lender's "disbursement date" is the other's "booking date".
| Event | Direction | Must Carry |
|---|---|---|
| Loan offer | Originator to partner | Borrower data, bureau data, eligibility result |
| Sanction decision | Partner to originator | Approve or reject, reason code |
| Disbursement | Originator to partner | Amount, share split, escrow reference, date |
| Repayment | Escrow to both | Amount, split by principal, interest and charges |
| Classification change | Either to the other | SMA or NPA tag, effective date |
| Closure | Originator to partner | Closure date, final settlement split |
A well-documented interface shortens this step a lot. Our guide to lending API documentation for partners covers versioning, sandboxes and error codes that a partner bank's technology team will ask for.
Step 4: How Should Escrow Flows Be Set Up?
Escrow flows should route every disbursement and every collection through the escrow account, with the appropriation waterfall written into both lenders' systems. If either side calculates the split differently, the month-end mismatch becomes a dispute.
Part-payments, bounced debits and reversals need named owners. Digiqt's payment reconciliation automation AI agent shows how unmatched payment entries can be flagged automatically.
Step 5: How Do You Keep Booking and Classification in Sync?
Keep booking and classification in sync with a daily loan-level feed and event-based alerts, not a monthly file. Each loan should show its age against the 15-calendar-day booking window, and any classification change should trigger a message the same day.
Each lender also reports its own share to credit information companies (CICs). Our guide to credit bureau integration architecture explains how to keep those reports consistent across systems.
Steps 6 and 7: How Should a New Co-Lending Partner Go Live?
A new co-lending partner should go live only after end-to-end tests pass on realistic loans, and then with a capped pilot. Tests must include rejected offers, cancelled disbursements, foreclosures, bounced EMIs and a classification downgrade.
During the pilot, cap daily volume and review breaks every day. Scale only after a month-end reconciliation closes without disputes.
How many weeks of your last partner launch went into rework that a field map would have avoided?
Talk to Our Lending Technology Specialists
Visit Digiqt to see how a custom lending platform can carry co-lending rules from day one.
How Much Does a Slow Co-Lending Go-Live Cost a Lender?
A slow co-lending go-live costs a lender the partner-funded book it could have built in the meantime. In this illustrative scenario, an NBFC plans to co-lend ₹30 crore a month, with the bank funding 80%, or ₹24 crore a month.
Assume the NBFC's net income on the bank-funded share, from fees and spread, is worth 2% a year. Each month's ₹24 crore tranche then adds ₹48 lakh of annual income.
| Measure | Go-Live in Month 2 | Go-Live in Month 6 |
|---|---|---|
| Months of co-lending in the first half-year | 4 | 0 |
| Bank-funded disbursement | ₹96 crore | ₹0 |
| Annual income on that book at 2% | ₹1.92 crore | ₹0 |
Breaks after go-live cost money too. If 3% of 400 loans a month miss the 15-day booking window, 12 loans averaging ₹7.5 lakh leave ₹72 lakh of the bank's intended share as exceptions to resolve every month.
The lesson for leadership: the integration plan, not the term sheet, decides when a co-lending partnership starts earning. Treat go-live as a product launch with a date, an owner and a test plan.
Where Does the Digiqt Lending Platform Fit in Co-Lending Partner Onboarding?
The Digiqt Lending Platform is a custom lending platform that Digiqt builds and launches "in a matter of weeks", covering onboarding, disbursement and repayments delivered through APIs. For NBFCs, the page describes APIs for onboarding, payments and other financial products.
Co-lending features would be specified as modules in a custom build, not bought off the shelf:
- Partner APIs for offers, sanction decisions, disbursement and repayment events.
- Share-split and escrow rules that apply the agreed split and appropriation waterfall.
- Booking-age and classification alerts against the 15-day and next-working-day rules.
- Partner-level dashboards for breaks, pending bookings and reconciliation status.
Digiqt's process runs from problem understanding and solution design to agile delivery, launch and ongoing optimisation. The same approach to launching a new loan product faster applies when the "product" is a new partner.
Should You Build Co-Lending Integration In-House or With a Partner?
Build in-house when you have spare engineering capacity and few partners, and work with a technology partner when you need speed or plan several partnerships. The right choice depends on your partner pipeline and current system.
| Lender Situation | Recommended Approach |
|---|---|
| One partner, strong in-house tech team | Build in-house with a shared field dictionary |
| Several partners planned within a year | Build a reusable partner API layer |
| Legacy loan system with no APIs | Add an integration layer or a custom platform |
| Bank partner with fixed file formats | Hybrid: APIs internally, files to the partner |
| Digital sourcing partners also involved | Align with digital lending rules as well |
Digital co-lending must also meet the rules in our guide to RBI digital lending guidelines compliance. Our guide to AI agents in co-lending shows where automation helps after go-live.
Which Metrics Show Co-Lending Partner Onboarding Is Working?
Five metrics show whether co-lending partner onboarding is working: time to first co-lent loan, first-pass test rate, on-time booking rate, classification sync lag and escrow break rate. Track them weekly during the pilot, then monthly.
| Metric | Formula | What a Weak Number Signals |
|---|---|---|
| Time to first co-lent loan | Days from agreement signing to first joint disbursement | Integration started too late |
| First-pass test rate | Test cases passed first time ÷ total test cases | Poor field mapping or unclear rules |
| On-time booking rate | Loans booked by both within 15 days ÷ loans disbursed | Slow data exchange or approvals |
| Classification sync lag | Average hours between a tag change and partner update | Batch feeds where events are needed |
| Escrow break rate | Unmatched escrow entries ÷ total escrow entries | Appropriation logic differs across systems |
Which Mistakes Delay Co-Lending Go-Live?
Four mistakes delay co-lending go-live, and all of them are planning choices.
- Starting integration after the agreement is signed. Legal and technical work should run side by side.
- Keeping the partner's credit rules in a PDF. Rules that are not coded cannot be tested.
- Testing only clean loans. Live volume always brings reversals, part-payments and downgrades.
- Scaling before month-end closes cleanly. One disputed reconciliation can stall the whole partnership.
Want your next co-lending partner live without a six-month integration project?
Talk to Our Lending Technology Specialists
Visit Digiqt to see how the Digiqt Lending Platform can be built around your partner APIs and escrow rules.



