For LSPs, co-lenders and channel partners
Multi-lender servicing, reconciled loan by loan
Track receipts, partner shares, amounts owed and days past due on one loan record after approval. Each lender’s view comes from the same postings, so your team can reconcile loan by loan.
- Lender tagged on every loan
- API or statement upload
- One DPD for you and the lender
- Partner lender A
- Partner lender B
- Co-lender C, your share
The money flows, lender by lender
Four movements decide whether your month-end ties out
Each of them reads the lender off the loan.
Collections land with the lender, and you post them.
Under RBI's digital lending rules a borrower repays into the lender's own bank account, with no pool account held by the LSP in between (Chapter III, paragraph 10(2)). Co-lent loans move through an escrow account instead (Co-Lending Directions, paragraph 26). You never hold the money, so your job is to see it. Where the partner offers an API, receipts post through it. Where it does not, you upload the partner's statement and each line posts against that lender's loan.
What each lender is owed, at any date.
Because every posting carries the lender, the question you answer in Excel today (how much has come in for each NBFC, and how much is still due to it) is a filter on the record. For a co-lent loan each event is split by share, since each lender keeps the borrower's account for its own part (Co-Lending Directions, paragraph 25).
Your share and the DSA payouts.
What a lender owes its LSP is paid by the lender and never collected from the borrower (Chapter III, paragraph 10(4)). Your share is agreed with each partner. The payouts you make onward to DSAs and sourcing partners are computed from the loan record: disbursal, per-loan, trail or collection fee models, with gross, tax and net on each invoice and maker-checker approval before payment.
The DLG position on the due date.
A default loss guarantee, often called FLDG in partner contracts, covers a fixed set of loans up to 5% of the amount disbursed from it. The lender invokes it within 120 days overdue, invoking it leaves the borrower's dues unchanged, and an invoked amount is never reinstated. Days past due come from the same postings for you and for the lender, so the count you hold against that 120-day limit is the count the lender holds too.
The partner, terms and fee trail behind each payout are covered on sourcing partner management. How a receipt is traced from bank line to a single posting is set out in loan reconciliation in an LMS.
Built by the team that helped create Apache Fineract, the open-source lending core, and later scaled a commercial lending platform on it.
One book, more than one lender
The tag on each loan decides whose numbers it counts toward
As an LSP the loans are off your book; as a co-lender you hold only your share. Either way you service someone else's balance sheet. In Lokta the loans you service sit on one set of ledgers, and a new partner's loans carry its tag from the first posting.
Every loan carries its lender.
The loan is punched once, with the NBFC or bank that funds it on the record. The sourcing partner that brought it sits on the same loan, and a co-lent loan carries each lender's share.
One partner's loans stay off the next partner's file.
Receipts, overdues and payouts are counted against the lender on the loan. When a partner sends its statement, the lines are matched against the loans tagged to that partner.
Each lender gets its own slice of the book.
Filter the record by lender and you have that partner's loans, collections, days past due and classification, with nothing from the other lenders you service in it.
The borrower-facing side of the same split, with each partner's queue, knowledge base and audit log held apart, is on AI Loan Servicing for LSPs. If the terms LSP, LOS and LMS blur together, start with LOS vs LMS vs LSP.
The quarterly partner audit
When both sides read the same postings, a gap points to its line
Every three months the partner's auditor compares the DPD and classification you reported with what the lender's books say. A gap usually traces to a receipt posted late, a reversal one side missed, or a statement keyed in twice.
Agents can prepare much of this, such as pulling the receipts behind a disputed DPD into one file. An agent's output is a proposal. It changes a loan only through the core, after the lender's policy check and any approval that policy requires, and the change stays on the record with who approved it and when.
- Days past due on each loan, as you reported it and as the lender's books show it
- SMA and NPA classification, which co-lenders must share by the end of the next working day
- Receipts against the lender's bank or escrow statement, line by line
- Each lender's share of a co-lent loan, as reported to the credit bureaus
- DLG invocations, and recoveries shared after them
- Sourcing-partner payouts, traced to the loans they were paid on
What stays with the partner lender
Servicing for a lender is a different job from lending
These four stay with the lender whoever does the servicing, and the record has to show them as the lender's.
Underwriting and the credit decision.
The partner lender decides who gets a loan, on its own LOS or on yours. The approved loan reaches Lokta by API. Loan Origination in Lokta is on the roadmap.
The loan agreement and the borrower's terms.
The contract, the Key Fact Statement and the rate are the lender's. For a co-lent loan the borrower pays a blended rate weighted by each lender's funding share (Co-Lending Directions, paragraph 17).
Bureau reporting duties, where the rules put them.
Every digital loan is reported to the credit bureaus by the lender (Chapter III, paragraph 17), and each co-lender reports its own share (Co-Lending Directions, paragraph 31). Credit-bureau filing is available in Lokta for the lender that holds the loan.
Accountability for the book.
An LSP agreement does not dilute the lender's obligations, and the lender stays fully responsible for what its LSP does (Chapter III, paragraph 6(7)). The lender runs the book. That is why the auditor comes to your office, and why your record has to match theirs.
The co-lending rules once a loan is live, including the 10% minimum share per loan and the 15-day booking window, are in RBI Co-Lending Directions 2025. The LSP and DLG rules are in RBI digital lending rules for NBFCs.
Partner lenders that will not open an integration
Statement upload posts repayments where no API exists
A partner lender rarely opens its systems to an LSP, and asking it to is slow. You do not need them to. Upload the statement the lender already sends, and each line is matched to a loan tagged to that lender. A partner that later offers an API can switch to it without changing how its loans sit on the record.
What lenders said
Lenders on partner and payout tracking.
On the partner and payout view
“Traditional systems never had something like this.”
On why Lokta starts after sanction
“The post-sanction area is the one which still today remains a grey area.”
After the portfolio dashboards
“This kind of concise and clear dashboard I never saw.”
On seeing bucket roll-back and roll-forward at account level
“My team takes half a day today just to get this data out manually.”
Asked when he wanted servicing automated
“At this point, I can start within a month.”
At the end of the demo
“You have covered all the pain points of the smaller NBFC.”
Three ways forward
Be the LSP whose numbers match every partner's
Keep the spreadsheet
Nothing changes today. Each month-end recon, and each audit, still depends on one person rebuilding every lender's numbers by hand.
The one we built for
Put every loan, and its lender, on one record
Receipts, payouts, DPD and classification come out split by partner, by API or by statement upload. Each partner's loans have to be mapped and tied out before cut-over.
Integrate with each lender's own system
Every partner becomes its own project, on its own timeline, and the lenders that will not open their systems stay in Excel.
Bring one partner's book and its last statement, and we will show you how it would sit on the record. Plans are on pricing.
Questions on multi-lender servicing
Repayments, partner integrations, pool accounts, payouts, DLG, audits and origination.
What is multi-lender servicing?
Multi-lender servicing is the post-disbursal work an LSP, co-lender or channel partner does on loans funded by more than one lender: posting repayments, tracking overdues, computing partner payouts and reporting to each lender. The hard part is keeping every loan tied to the lender that funds it, so each partner's receipts, days past due and classification can be produced on their own without a month-end spreadsheet.
How does a repayment reach the right lender's loan in Lokta?
Each loan carries the lender it belongs to. A receipt posts against that loan through the partner's API where one exists, or from the partner's statement when you upload it. Either way the posting lands on a loan whose lender is already on the record, so collections roll up by lender without a separate recon sheet.
Do my partner lenders have to build an integration with Lokta?
No. Statement upload posts repayments where a partner offers no API, so a lender that will not open its systems can still be serviced on the same record as one that does. Where a partner does expose an API, receipts can post through it instead.
Can an LSP collect repayments into its own account and pass them on?
Not for digital loans from an NBFC. Chapter III of RBI's NBFC Credit Facilities Directions, 2025 sends each repayment straight to the NBFC's bank account and bars a pass-through or pool account held by any third party, including the LSP. Co-lent loans follow the co-lending rules, which route money through an escrow account with a bank. The LSP's servicing record has to reflect money that landed in the lender's account, which is why posting from the lender's statement matters.
How are DSA and sourcing-partner payouts worked out?
From the loans themselves. Each loan stores the sourcing partner and the commercial arrangement in force on its booking date, and the fee is computed from those booked terms under a disbursal, per-loan, trail or collection model. Invoices show gross, tax and net, and each stage goes through maker-checker approval. The sourcing partner page covers the module in full.
What does a default loss guarantee change in servicing?
It adds a deadline and a ceiling to a fixed set of loans. RBI caps DLG at 5% of the amount disbursed from the covered portfolio, requires the lender to invoke it within 120 days overdue, and keeps the borrower's dues unchanged when it is invoked. Classification and provisioning on those loans follow the normal NPA rules, guarantee or not. In co-lending, a guarantee from the originating lender is capped at 5% of the loans outstanding under the arrangement.
How does one record help with the partner's quarterly audit?
The auditor compares the days past due and classification you report with what the lender's books show. When both come from the same postings, a gap points to a specific receipt or reversal you can open, rather than to two spreadsheets that drifted. Co-lent loans sit inside both lenders' internal and statutory audit scope, so the same record is read by more than one set of auditors.
Does Lokta underwrite or originate the loans I service?
No. Underwriting stays with the lender, and Loan Origination in Lokta is on the roadmap. The partner lender's LOS, or your own, approves the loan and hands it to Lokta by API. Loan Management and AI Loan Servicing, the parts that cover the book after approval, are available now.
Sources
Paragraph references are to the RBI texts below as cited in the two Lokta posts linked above. This page describes servicing work and is not legal advice; the terms of a specific arrangement belong with your counsel and your partner lender.
- Reserve Bank of India (Non-Banking Financial Companies - Credit Facilities) Directions, 2025, updated as on 15 July 2026. Chapter III, paragraphs 6(7), 10(2), 10(4), 17 and 19 to 29.
- Reserve Bank of India (Co-Lending Arrangements) Directions, 2025, 6 August 2025, effective 1 January 2026. Paragraphs 17, 25 to 27, 31 to 33.