A weaver in Solapur applies for a ₹3 lakh personal loan at his cooperative bank’s local branch and gets it sanctioned in four days. His cousin, banking with the same cooperative society but at a branch forty kilometres away, applies for a near-identical amount against a similar income profile and waits three weeks before being turned down. Nothing changed about the applicant’s risk. What changed was which desk the file landed on. At Finezza, we’ve spent enough time inside cooperative bank lending workflows to recognise the pattern. It’s a structural gap, and it shows up in board meetings long before it shows up in an audit.
Key Takeaways
- Branch-level lending discretion is a legacy design that hasn’t caught up with today’s loan volumes and product mix.
- Two branches often reach different decisions because they don’t share the same credit bureau access, income verification method, or underwriting checklist.
- Core banking systems record a loan decision after it’s made. They were never built to standardise how that decision happens.
- RBI’s expanding regulatory attention on cooperative banks, including recent enforcement action and licensing reform, is turning branch-level inconsistency into a supervisory concern.
- Standardising the decision layer, not removing branch judgement, is what closes the gap.
Why Branch Managers Reach Different Conclusions on the Same File
Cooperative banks were built around a specific kind of lending. A branch manager who knew the applicant’s family, land holding, or shop turnover could sanction a loan on judgement that a centralised underwriter forty kilometres away simply didn’t have. Character-based lending is why cooperative banks reached borrowers that commercial banks found too small or too costly to underwrite.
The trouble starts when the product list grows faster than the rulebook. A branch that once handled agricultural loans and small personal loans now also processes vehicle loans, property loans, and MSME working capital, each with its own risk logic, and branch managers apply the same instinct-driven approach across categories they weren’t trained to read. Two credit officers looking at the same term loan and revolving credit application can reach different conclusions, not because either one is wrong, but because neither has a checklist translating credit policy into a repeatable decision.
The deeper problem is a missing common origination layer that would translate credit policy into a repeatable decision, regardless of individual competence. A well-designed loan origination system forces every application through the same sequence of checks regardless of which branch it enters from. Without one, judgement fills the gap, and judgement varies by person.
Why Credit Data Doesn’t Reach Every Branch the Same Way
Ask five branch managers at the same cooperative bank whether they pull a credit bureau report for every personal loan, and you’ll likely get five answers. Some treat it as routine, others reserve it for larger tickets to save on per-pull cost, or because the process runs through a separate portal outside daily workflow. That inconsistency alone can produce different outcomes for near-identical applicants, unrelated to actual creditworthiness.
Bank statement analysis has the same problem. Where one branch has a credit officer who reads three months of transactions and manually flags irregular deposits, another might rely on a passbook glance and the applicant’s own account of income. A structured read of credit bureau report data points catches patterns a manual scan misses, but only if every branch runs the same analysis, not just the branches with a sharper credit officer that week.
The deeper issue is that most cooperative banks still treat creditworthiness as a proxy for credit score, rather than a fuller picture built from income stability, cash flow, and existing exposure. Where the Account Aggregator framework is in use, branches can pull this data directly from the source instead of depending on what the applicant chooses to disclose, the kind of shift that lets lenders intervene before a loan turns into a Non-Performing Asset, or NPA, rather than after.
Why Core Banking Systems Can’t Standardise the Decision
Most cooperative banks run on a core banking system, or CBS, that’s good at what it was built for: ledgers, interest accrual, statutory reporting, and compliance filings. It was not built for underwriting. By the time a loan account gets created in the CBS, the actual decision (the bureau pull, the income check, the exposure screening) has already happened elsewhere, often on a separate portal or over a phone call to the branch manager. As we’ve written before, cooperative banks need more than core banking software alone, because a system built for post-sanction accounting can’t retroactively standardise a decision made outside it.
Moving to the cloud doesn’t fix this either. Without a common decision path, every branch keeps improvising its own version of due diligence, just on faster hardware.
What Changes as Cooperative Bank Branch Networks Expand
This problem is set to grow. Urban cooperative bank credit growth stayed healthy through FY26, with total advances rising 9.6 per cent year-on-year as of March 2026, even as asset quality across the sector improved, with gross NPAs down to 5.2 per cent and net NPAs to 1.0 per cent. Those improving numbers reflect loans already on the books, not the underwriting decisions being made today at a faster pace and often at a new branch. Growth on an inconsistent underwriting foundation compounds a risk that today’s clean numbers don’t yet show.
RBI has also let urban cooperative banks expand their branch network without prior approval for increases up to 10 per cent of existing branches or five branches, whichever is lower. More branches on the same manual underwriting model means more places where the same file gets read differently. Supervisory attention hasn’t loosened alongside this growth either: RBI enforcement action between December 2025 and May 2026 covered 99 regulated entities, 56 of them cooperative banks, with penalties totalling ₹8.96 crore. RBI is also drafting the first fresh licensing framework for urban cooperative banks since 2004, a sign of appetite for tighter governance standards sector-wide.
How to Standardise Loan Approvals Without Losing Local Judgement
The fix keeps branch managers’ authority intact. It gives every branch the same floor to stand on before local judgement gets applied on top: one rule engine encoding the bank’s actual credit policy, so a Go or No-Go decision is consistent and defensible regardless of which branch made it; bureau connectivity and AI-powered cash flow reading available by default rather than reserved for the branches with better internet; digital KYC checks pulling from DigiLocker, the CKYC, and GST data instead of whatever a branch collects on paper; and fraud detection flagging tampered or duplicate applications before they reach the credit team
This is the exact gap Bharat Fin Sahakar, Finezza’s cooperative-first lending platform, was built to close. A shared decision engine and bureau connectivity travel with every application, whichever loan management system or branch it originates from, so approvals hold up to the same standard from the first branch to the fiftieth. The same consistency carries downstream too: a cooperative bank that standardises origination usually needs fewer manual loan recovery interventions later, because the loans that got sanctioned were evaluated the same way to begin with.
Frequently Asked Questions
1. Why do two branches of the same cooperative bank take different lending decisions for similar borrowers?
Because most cooperative banks still rely on branch-level judgement rather than a shared rule engine. Without a common checklist, bureau access, and income verification method across branches, two credit officers can read the same file differently even when the underlying risk is identical.
2. Is inconsistent branch-level lending a compliance problem?
It can become one. RBI doesn’t mandate a single underwriting method, but inconsistent practices that lead to asset quality problems do attract supervisory attention, as recent enforcement actions against cooperative banks show.
3. Does standardising loan approvals mean removing branch managers’ authority?
No. Standardisation means giving every branch the same underwriting floor, bureau data, and rule engine, so local judgement gets applied on top of consistent information rather than in place of it.
4. How long does it typically take a cooperative bank to standardise underwriting across branches?
Timelines depend on the bank’s size and existing systems, but platforms built specifically for cooperative banks can bring branches onto a shared decision engine in as little as 45 days, well short of the months a custom build usually takes.
Conclusion: One Underwriting Floor for Every Branch
Two branches reading the same file differently was tolerable when cooperative banks were smaller and lending stayed local. It’s harder to justify at today’s loan volumes, and harder still as branch networks expand under relaxed approval norms. Every branch, regardless of size or staff tenure, should work from the same data and the same rules before local knowledge gets applied where it adds value.
Book a demo of Bharat Fin Sahakar to see how a shared decision engine brings every branch onto the same underwriting floor.
Leave a Reply