Blog/Fintech & Lending

Co-Lending Reconciliation: Keep Your Books and Partner Bank Books Matched

Build a co-lending reconciliation routine that matches disbursals, collections and splits with your partner bank before differences grow into disputes.

By Sagar Makker · 7 min read · October 2026
Creditcard Money
In short
Co-lending breaks down at the loan level: disbursal dates, collection splits and charges drift between two systems.
Reconcile loan by loan, not just on totals, and agree a shared file format and cut-off with the partner.
Classify every break by cause and age, and settle them on a fixed calendar with named owners on both sides.
The problem

This is for finance controllers, co-lending desk heads and operations managers at NBFCs working with banks or other lenders under co-lending arrangements. When your loan book and the partner's records disagree, collections get mis-split, escrow balances look wrong and month-end becomes an argument. This post gives a loan-level reconciliation method, a break classification that speeds up settlement, and a monthly calendar both teams can follow without endless email chains.

The partner bank's monthly statement shows a principal outstanding several lakhs higher than your LMS for the same pool. Totals do not explain why. After a week of spreadsheets, the team finds a mix of loans foreclosed but not reported, part-payments split on different dates, and a handful of loans where the partner applied a different interest rate on its share.

Each side holds escrow inflows, bounce charges and penal charges in its own system with its own posting logic. Because reconciliation happens only on pool totals, small loan-level differences accumulate for months. When an audit or a partner review asks for proof, nobody can show a clean, loan-by-loan agreement for any recent month.

Why it happens
01Reconciliation done on pool totals rather than at individual loan level.
02No agreed data format, field definitions or cut-off time between partners.
03Part-payments, foreclosures and charges posted on different dates in each system.
04Escrow collections not mapped to loans before the split is computed.
05Breaks are not classified or aged, so old differences never get closed.
How to fix it
1
Agree a shared data template
The co-lending desk head agrees with the partner a loan-level file with fixed fields, definitions, date formats and a daily or monthly cut-off. Put the template in the operational agreement so neither side changes it unilaterally.
2
Map escrow inflows to loans
Treasury or ops maps every escrow credit to a loan account and instalment before the split runs. Unmapped credits go to a suspense list reviewed daily, so they do not distort principal and interest shares.
3
Reconcile loan by loan
Finance matches each loan on disbursed amount, principal outstanding, interest accrued, charges and status between your LMS and the partner file. Any field mismatch beyond a tolerance you define becomes a break record.
4
Classify and age every break
The reconciliation analyst tags each break by cause, such as timing, rate difference, unreported event or charge mismatch, and by age. Timing breaks should clear next cycle; others need a fix owner.
5
Settle on a fixed calendar
The finance controller runs a monthly settlement call with the partner on a fixed date, works through open breaks oldest first, and records the agreed fix and the system that will be corrected.
Worked example
An NBFC moves from totals to loan-level matching

An NBFC in Chennai co-lending MSME loans with a public sector bank was reconciling only pool balances. Differences kept rolling forward, and a partner review asked for loan-level evidence the team could not easily produce. The co-lending head agreed a shared file template and cut-off with the bank, mapped escrow credits to loans daily, and began matching each loan on five fields. Breaks were tagged by cause and age, and a fixed monthly call worked through them. Old differences were traced to unreported foreclosures and a rate mismatch, both fixed at source, and month-end close became predictable.

Common mistakes
×
Reconciling only on pool totals
Totals can match while individual loans are wrong in offsetting ways. Always reconcile at loan level, then roll up to confirm the pool position.
×
Fixing breaks only in spreadsheets
A spreadsheet fix leaves the source system wrong, so the break returns next month. Record which system needs correction and confirm the change before closing the break.
×
Leaving escrow credits unmapped
Unmapped collections skew the principal and interest split and hide bounce issues. Keep a suspense list and clear it daily with a named owner.
Where an AI agent helps
Input
Your LMS extract, partner bank loan file and escrow statement for the period
Agent does
Maps escrow credits, matches loans field by field, and tags breaks by cause and age
Human gate
Finance controller approves break classifications and any proposed correction entries
Outcome
Loan-level reconciliation report and an aged break list for the partner call
Checklist
Agree a loan-level data template and cut-off with each partner
Map every escrow credit to a loan before running the split
Match disbursal, outstanding, interest, charges and status
Tag every break by cause and age
Hold a fixed-date monthly settlement call with the partner
Correct the source system before closing any break
What to measure
Open breaks by age bucket
Loans matched on all fields per cycle
Unmapped escrow credits at day end
Days to close monthly co-lending books
Questions
How often should co-lending books be reconciled?

Escrow mapping should happen daily. Full loan-level reconciliation is commonly monthly, aligned to the partner's statement. High-volume pools may justify weekly matching. Check your co-lending agreement and current regulatory guidance with your compliance team.

Who should own co-lending reconciliation?

Finance usually owns the reconciliation and sign-off, with the co-lending desk owning partner communication and ops owning escrow mapping. Name a single accountable person so breaks do not fall between teams.

What tolerance should we use for small differences?

Set a small rupee tolerance per field for rounding, agreed with the partner and written down. Anything above it is a break. Keep the tolerance tight enough that genuine errors cannot hide inside it.

What if the partner will not change their file format?

Build a mapping layer on your side that converts their format into your template, and document every field mapping. Revisit the template at the next agreement review so the burden is shared.

Keep reading
All posts →
Calculator NumbersFintech & Lending
DSA Partner Management: Track Lead Quality, Payouts and Conduct Together
7 min readRead →
Calculator NumbersFintech & Lending
Keep Audit Trails and Compliance Evidence Ready for Lenders
5 min readRead →
Business OfficeFintech & Lending
Underwriting Document Checks That Catch Mismatches Before Credit Review
7 min readRead →
Next step

Want this fixed in your business?

Send the workflow. You get a scope and a fixed price within two working days — or a straight answer that it isn't a fit.

Secure by default · find → fix → verify · authorised scope only
Send a brief →enquiry@xdqlabs.com