A borrower submits one application through an NBFC’s digital platform. The NBFC’s Loan Origination System (LOS) approves based on bureau data and bank statement analysis. The partner bank’s credit system rejects the same applicant using different underwriting parameters. Neither institution knows about the mismatch until the borrower calls three weeks later.
This repeats across co-lending partnerships because banks and NBFCs run separate technology stacks with different data definitions, approval workflows, and servicing protocols. When these systems don’t synchronise in real time, the entire lending lifecycle fragments into disconnected stages where decisions in one system contradict actions in another.
What is the Lending Lifecycle in Co-Lending Models
The lending lifecycle in co-lending arrangements spans six stages: origination, underwriting, disbursement, servicing, collections, and regulatory reporting.
In traditional single-lender models, one institution controls all stages through integrated systems. Co-lending splits this control between partners. The NBFC manages customer-facing operations, whilst the bank handles backend functions like funds provision and regulatory reporting. Both institutions share credit risk and maintain independent records of the same loan portfolio.
This creates synchronisation requirements that didn’t exist before. When the NBFC updates a borrower’s contact details, the bank’s system must reflect the change. When the bank restructures a repayment schedule, the NBFC’s collection system needs immediate notification. Without continuous data alignment, operational decisions are made on outdated information.
Why Workflow Synchronisation Determines Co-Lending Success
Workflow misalignment creates compliance risk, operational overhead, and customer experience failures that undermine co-lending’s core value proposition.
Consider bureau reporting obligations. Both the bank and NBFC must be consistent and reconcilable, with documented rules so both report accurately for their respective share. When the NBFC’s system marks an account as current whilst the bank’s batch processing shows 30 Days Past Due from last week, both institutions risk regulatory action for reporting inconsistencies.
A mid-sized NBFC managing 50,000 co-lending accounts with three banking partners faces 150,000 potential sync points monthly. Manual reconciliation consumes operational capacity that should focus on origination and customer service.
Borrowers experience these sync failures as contradictory communications. The NBFC sends an approval confirmation. The bank’s system triggers an additional document request. These breakdowns damage trust in digital lending precisely when adoption is accelerating across Tier-II and Tier-III cities.
4 Critical Synchronisation Points Across Lending Lifecycle Stages
Each stage of the lending lifecycle presents specific synchronisation challenges where bank and NBFC systems must align data, decisions, and workflows to prevent operational breakdowns and compliance failures.
1. Origination and Underwriting: Application Data Conflicts
Application data captured by the NBFC’s digital platform must flow to the bank’s LOS without transformation errors.NBFC pulls bank statements via Account Aggregator (AA) framework; bank policy still requires ITRs (or additional docs), neither institution can approve until both data sets exist in both systems.
Eligibility calculators create another sync point. The NBFC shows a maximum eligible amount as ₹5 lakh based on debt-to-income ratios. The bank’s risk parameters cap the same applicant at ₹3.5 lakh. The borrower applies for ₹4.5 lakh, triggering an approval-rejection conflict requiring manual intervention.
Credit assessment through bank statement analysis often differs between institutions. The NBFC’s automated analysis flags healthy cash flows whilst the bank’s manual review identifies irregular deposits, delaying approvals.
2. Disbursement: Funds Flow and Documentation Gaps
Disbursement requires synchronisation between the bank’s Core Banking System (CBS), the NBFC’s Loan Management System (LMS), and payment gateways. The bank initiates National Electronic Funds Transfer (NEFT) from its CBS at 2 PM. The NBFC’s LMS updates at 4 PM through batch processing. For those two hours, customer service teams have contradictory information.
Platforms like Finezza eliminate these timing gaps by synchronising disbursement events across both institutions’ systems in real time. When the bank initiates funds transfer, Finezza’s LMS updates the NBFC’s servicing module instantly, ensuring both institutions maintain identical portfolio views.
3. Servicing and Collections: Repayment Reconciliation Failures
Repayment reconciliation becomes complex when borrowers make payments through multiple channels. A borrower pays ₹25,000 through the NBFC’s app using Unified Payments Interface (UPI). The NBFC’s system updates instantly. The bank’s CBS receives notification through batch upload at end-of-day, creating temporary mismatches.
Days Past Due (DPD) calculations must align exactly between institutions. When the NBFC counts DPD from the original due date, whilst the bank counts from the grace period expiry date, the same loan gets classified differently. Bureau reporting requires one classification, forcing manual reconciliation.
Collection strategies also need synchronisation. The NBFC’s collections team offers a settlement at 85% of outstanding principal, whilst the bank’s recovery system sends a legal notice demanding full repayment, undermining collection effectiveness.
4. Reporting: Bureau Submissions and Regulatory Compliance
Both institutions must submit identical data to credit bureaus and regulators. When the NBFC reports a loan as restructured, whilst the bank’s submission shows it as standard, regulators flag the inconsistency. Credit Information Companies (CIC) regulations mandate accurate reporting, making these mismatches compliance violations.
RBI reporting requirements for Non-Performing Assets (NPA) classification add another layer. If NPA classifications differ due to data sync lags, both institutions face regulatory scrutiny.
Technical Architecture Gaps That Prevent Synchronisation
Most sync failures trace back to three architectural limitations:
- Batch processing instead of real-time event streaming: Traditional systems exchange data through scheduled batch uploads. When the NBFC processes a payment at 10 AM, and the bank receives the update at midnight, that 14-hour lag creates reconciliation issues.
- Inconsistent data schemas: The NBFC’s LMS stores loan amounts as integers (500000 for ₹5 lakh). The bank’s CBS stores the same field as decimal with currency code (5,00,000.00 INR). Middleware translating between these formats introduces transformation errors that accumulate across thousands of transactions.
- Unidirectional data flows: Many partnerships use one-way data transfer. When the bank restructures a loan or updates contact details, the NBFC’s system never receives the changes. Both institutions diverge further with each update.
How Finezza Enables Synchronised Workflows
Platforms designed for co-lending workflows solve synchronisation through bidirectional APIs, unified data models, and event-driven architecture.
Unified data models standardise how both institutions define loan parameters, reducing transformation errors. Event-driven workflows replace batch uploads with instant triggers that simultaneously update the NBFC’s LMS, the bank’s CBS, and collections systems.
Finezza’s loan management platform maintains synchronised loan records across partner institutions. When the NBFC originates an application, Finezza’s LOS captures the data once and makes it available to the bank’s underwriting system through APIs. Repayment events flow bidirectionally, ensuring both institutions maintain identical portfolio views. This synchronisation extends to regulatory reporting, with bureau submissions generated from a single source of truth rather than reconciling between two systems.
The result is co-lending partnerships that scale operationally without multiplying reconciliation overhead. As portfolio size grows from 10,000 to 100,000 loans, synchronised workflows prevent the linear increase in manual reconciliation that makes co-lending uneconomical at scale.
Ready to eliminate workflow synchronisation gaps in your co-lending partnerships?
Book a demo to see how Finezza’s lending lifecycle management platform maintains real-time data consistency across bank and NBFC systems.
Leave a Reply