Pre-Sanction Borrower Litigation Screening for Lenders

Lending & Credit Risk · Litigation Screening

Updated for 2026 · Claw Editorial

Before a bank or NBFC sanctions a loan, its credit team needs to know one thing that a credit score alone will not tell it: is this borrower, or the company behind it, already fighting or facing a court case that could affect repayment. That question, pre-sanction borrower litigation screening, sits between KYC and final credit approval, and getting it wrong either slows down good loans or lets a risky one through. This guide explains what the check should cover, why it is harder in India than it looks, and how lending teams are building it into the sanction process.

01What pre-sanction borrower litigation screening is

Pre-sanction borrower litigation screening is the practice of checking whether a prospective borrower, whether an individual, a proprietorship, or a company and its promoters, has any pending or past litigation that could be relevant to the loan being considered. It sits alongside KYC, financial statement analysis, and credit bureau checks, but it answers a different question. A clean credit score tells you how someone has repaid debt in the past. It does not tell you that the same borrower is currently a defendant in a recovery suit, has cheques bounced under Section 138, is facing a SARFAESI action from another lender, or has a group company under insolvency proceedings at the NCLT.

For a bank or NBFC, this matters because pending litigation is a forward-looking risk signal that a backward-looking credit history simply cannot capture. A borrower can have a good repayment record on paper and still be a poor credit risk because of a live dispute, a pending SARFAESI notice from another bank, or an ongoing insolvency proceeding involving a related entity.

02Why litigation screening is hard to do well in India

In principle this sounds like a simple background check. In practice, doing it properly across India is genuinely difficult, for a few reasons.

Court records are fragmented, not unified

There is no single, complete database that covers every civil suit, cheque bounce case, tribunal matter, and consumer complaint pending against a given name, anywhere in India. Records sit across the Supreme Court, 25 High Courts, thousands of district courts, and specialised tribunals such as the DRT (Debts Recovery Tribunal), NCLT (National Company Law Tribunal), consumer forums, and RERA authorities, each with its own filing system. A credit team that checks only one source will miss cases that live in another.

Name matching is a real problem

Indian names repeat often, transliteration from regional languages produces spelling variants, and companies change names or operate through group entities and related parties. A litigation search that matches only on exact spelling will both miss genuine hits (a case filed under a slightly different spelling) and throw up false positives (a different person who happens to share a common name). Either failure mode has a real cost: a missed case that later becomes a bad loan, or a good borrower delayed by a false match that has to be manually cleared.

Group structures create blind spots

For corporate and MSME lending, the borrower entity itself may be clean while a promoter, a guarantor, or a group company is under litigation, insolvency, or a SARFAESI action. A check that only screens the exact legal name on the loan application, and not the wider promoter and guarantor group, misses exactly the risk that matters most in many defaults.

Time pressure works against thoroughness

Sanction timelines are a competitive factor. A credit team that has to manually search multiple court websites, tribunal portals, and news sources for every application is under pressure to either cut corners or slow down the whole pipeline. This is the practical tension at the centre of the problem: screening has to be both fast and complete, and manual processes struggle to be either at scale.

03What a proper litigation check should cover

A pre-sanction litigation check that is actually useful to a credit team needs to look across several kinds of proceedings, not just one. The table below sets out the main categories and why each one matters to a sanction decision.

No single database in India holds all eight of these categories with full district and tribunal depth, which is exactly why lending teams often combine more than one source, rather than relying on one search.

04How lenders run this check today

Most lending teams use a mix of three approaches, often in combination.

Manual court website searches. Analysts search individual High Court, district court, and tribunal e-filing portals by borrower name. This is thorough only if every relevant court is checked and every name variant is tried, which is slow and hard to guarantee at loan volume.

Specialist verification vendors. A number of BFSI-focused verification providers offer litigation search reports built specifically for lending underwriting. Perfios, for example, offers a legal search / litigation report product aimed at banks and NBFCs that draws on a large network of courts and tribunals across India, and is often paired with FIR and criminal record checks as part of a broader borrower risk report. Vendors like this exist because building and maintaining multi-court, multi-tribunal coverage in-house is a significant undertaking on its own.

AI-based case search tools. Newer legaltech platforms use AI and semantic search to search a borrower’s name across large volumes of judgment and case data, returning results in seconds instead of hours. This is faster than manual search and can catch name variants that a simple keyword search would miss, though the coverage still depends on which courts and tribunals the tool actually indexes.

A credit score tells you how a borrower repaid debt in the past. Litigation screening tells you what is happening to them right now, which is the part a bureau report cannot see.

05Building litigation screening into the sanction process

A few practical points help a lending team make litigation screening a reliable, repeatable part of underwriting rather than an occasional manual step.

• Screen the full group, not just the applicant name. Include promoters, directors, guarantors, and known group entities, since risk often sits one level away from the exact borrower name on the application.
• Search before sanction, and again before disbursement. A gap of a few weeks between approval and disbursement is enough for a new case to be filed. A second, quick check before money moves catches this.
• Treat name matches as leads, not verdicts. Given how common Indian names are, every hit needs a human to confirm it is actually the same person or entity before it affects a decision.
• Combine sources rather than relying on one. Because no single database has full depth across every court and tribunal, larger lenders typically pair a specialist verification report with their own case search capability, rather than treating either as complete on its own.
• Keep a record for audit. Regulators and internal audit expect evidence that a litigation check was actually run and reviewed, so the search results and the underwriter’s conclusion should be part of the credit file.

These are process decisions, not tooling decisions, and they matter regardless of which search product a lender ends up using.

06Where Claw fits

Claw is an all-in-one legaltech platform for Indian advocates, law firms, and corporate legal teams, combining AI-based case search, an AI legal assistant (Legal GPT), case management, and compliance automation across all Indian courts and tribunals.

For pre-sanction litigation screening, the relevant piece of Claw is its case search: an AI-based, semantic search across 30 crore plus judgements from all 25 High Courts (1980 to 2026) and the Supreme Court (1950 to 2026), designed to be name-tolerant so that spelling variants and proximity matches surface rather than get missed, with results returned in under 5 seconds and verified, court-ready citations attached to every hit. For a credit team, that means a borrower or promoter name can be checked against a large, current body of High Court and Supreme Court litigation quickly, as one input into the sanction decision, rather than a manual, court-by-court search.

It is worth being precise about scope. Claw’s case search covers the Supreme Court and High Courts; it is not a dedicated search across every district court, DRT, NCLT bench, RERA authority, or consumer forum by name. For that tribunal and district-level depth, which specialist BFSI verification vendors are built specifically to cover, a lending team may still want a dedicated litigation search report alongside Claw’s case search, rather than in place of it. Claw’s separate case tracking capability does cover 8,200 plus courts including tribunals and district courts, but that is for monitoring cases once they are known, not for a name-based litigation search across all of them.

On data handling, a point that BFSI compliance teams often ask about directly: Claw does not use customer case documents to train AI models, which matters when a lender is running borrower and promoter names through a legal search tool as part of a regulated underwriting process.

07Sources and further reading

References used in this guide:

• Perfios legal search / litigation report for lenders: perfios.ai/legal-search-report
• Claw: clawlaw.in
• Reserve Bank of India (SARFAESI and credit risk framework references): rbi.org.in
• eCourts India (official court case status portal): ecourts.gov.in

This is not an exhaustive list of verification vendors. Coverage and pricing details should be confirmed directly with each provider before relying on them for a live underwriting process.

08Frequently asked questions