Use Case · KYC and KYB · Litigation Risk

Litigation Check for KYC and KYB Refresh

Updated for 2026 · Claw Editorial

KYC and KYB confirm who the customer or counterparty is. Periodic refresh exists because the answer changes over time, and the part that changes fastest is risk. A customer who was clean at onboarding can, by the next refresh cycle, be a defendant in a fraud complaint, a respondent in an insolvency petition, or the subject of recovery action. A litigation check turns a periodic refresh from a document-updation exercise into a genuine re-assessment of risk, and monitoring fills the long gap between one refresh cycle and the next. This page explains why the litigation picture drifts between cycles, what to search at a refresh, where the check belongs in the updation workflow, and how to run it across a large customer base without doing it by hand. Last verified October 2026.

01Why a refresh is a risk re-assessment, not a document update

Periodic updation is often treated as an administrative task: confirm the address, re-collect the identity documents, re-verify the beneficial owners. That keeps the record current, but it misses the point of a refresh, which is to ask whether the customer or counterparty is still the risk you signed up for.

Risk is where the biggest change usually sits. Between one refresh and the next, a counterparty can acquire litigation that materially changes its profile:

• Fresh criminal or fraud matters against the entity, its directors or its beneficial owners.
• Insolvency and recovery action that signals financial distress and prior creditor claims.
• Regulatory and economic-offence matters that change the reputational and compliance picture.

Adding a litigation check to the refresh is what makes the exercise a real re-assessment rather than a re-filing.

02What changes between KYC cycles

The whole case for a litigation check at refresh is that the picture drifts. A clean onboarding result has a shelf life, and it is often shorter than the refresh cycle itself.

A clean result at onboarding describes the customer on the day you checked. By the next refresh cycle, which can be years later, it may describe no one.

The drift matters most for the customers and counterparties you interact with least, because those are exactly the files you are least likely to look at between cycles. A long-dormant corporate account, a supplier you renew automatically, or a channel partner you rarely review can all accumulate litigation quietly. The refresh is your scheduled chance to catch it, and monitoring is how you catch it sooner.

03What to search at a refresh

At a refresh the search should cover the entity and the people behind it, with weight on matters that change the risk rating:

For KYB in particular the search must reach the beneficial owners and directors, not only the registered entity, because control and risk often sit with the people. For continuous coverage of a counterparty between refreshes, see ongoing counterparty monitoring.

04Where the check sits in the updation workflow

The litigation check slots into the refresh at two points:

• At the scheduled refresh itself. When a customer or counterparty comes up for periodic updation, the entity, its directors and its beneficial owners are re-searched alongside the document re-verification, and any new matter is read into the risk rating.
• Between refreshes, through monitoring. Because refresh cycles can be long, a watchlist of higher-risk relationships is scanned on a schedule so a fresh filing surfaces as an alert rather than waiting for the next cycle.

An event-driven trigger can sit on top: if monitoring flags a serious new matter against a customer, that customer is pulled forward for an off-cycle review rather than left to the calendar.

05Running it across the customer base

A regulated entity may carry lakhs of customer and counterparty files, each coming up for refresh on its own schedule. Searching each one by hand at refresh, and watching the higher-risk ones in between, is not feasible manually. The practical approach is to feed the names due for refresh into a search that runs across courts and tribunals at once and returns a structured, scored result, and to keep a monitored watchlist of the relationships that carry the most risk.

This also helps the refresh prioritise: a scored result lets the team spend review time on the files where the risk rating actually moved, rather than reading every file equally. For the broader monitoring view, see litigation monitoring at scale.

06Reading the result honestly

A litigation result at refresh is a risk input, not a verdict on the customer. Read it with the usual caveats:

• "Nothing on record" is not a clean chit. It means no matter was found in the registries searched, on the date searched, under the names searched. A different spelling or an uncovered forum can still hide a case.
• A hit on a common name is not proof. Customers and beneficial owners frequently share names, so every finding needs a match-confidence flag and a human check before it changes a risk rating or drives an exit.

Read this way, the search supports your KYC and KYB risk rating and your internal policy. It is not legal advice on any customer or counterparty.

07Where 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.

ClawScore (at clawscore.clawlaw.in) is Claw's litigation and criminal-risk intelligence service, and it fits the KYC and KYB refresh directly. Name a customer, counterparty, director or beneficial owner, and ClawScore returns every matter it finds across 9,102 courts, benches and forums in one scored Excel workbook: a Summary with a ClawScore risk band (Clean, Low, Moderate or High), a Matters sheet, a Related parties sheet covering directors and beneficial owners, and a Coverage sheet showing what was searched. Every finding carries a match confidence, which matters on a large base full of common names. Constant Monitoring watches a watchlist between refresh cycles and reports New filings, Changed movement and Closed disposals on daily, weekly or monthly scans, so a serious new matter can trigger an off-cycle review. Searches start from Rs 500 per search with monitoring, results return in under 5 seconds, and Claw does not use your searched names or documents to train its AI models. ClawScore is a litigation and criminal-risk input to your KYC and KYB risk rating, not a verdict, and "nothing on record" means nothing was found in these registries on the date searched under the names searched.

To add a litigation layer to your next refresh cycle, you can create a FREE Claw account and run a case search across Indian courts by party name across every forum at once.

08Sources and further reading

• eCourts (district and High Court case status): ecourts.gov.in
• National Judicial Data Grid (official pendency data): njdg.ecourts.gov.in
• Reserve Bank of India (KYC Master Direction and periodic updation): rbi.org.in
• Insolvency and Bankruptcy Board of India: ibbi.gov.in
• Claw: clawlaw.in

This page is general information for an Indian B2B audience, not legal advice. A litigation search supports a KYC or KYB risk rating; it does not replace counsel or your internal compliance policy on any specific customer.

09Frequently asked questions