Use Case · Procurement · Vendor Onboarding
Vendor Onboarding Legal Verification (2026)
Onboarding a vendor adds a supplier to your systems, your payment runs and your supply chain. Legal verification at that gate confirms the vendor is a real, active, authorised entity that is not carrying legal trouble you would not want to inherit. It is broader than a litigation search alone: it starts with whether the entity even exists and can contract, and ends with the disputes and insolvency risk behind it. Done as a repeatable step, it keeps problem vendors out of the master before they become a payment or supply problem. This page sets out, for Indian procurement and risk teams, what vendor onboarding legal verification should cover, the source for each check, and how to run it at volume. Last verified October 2026.
- Four layers: existence at MCA, GST identity, signing authority, and litigation and insolvency, plus a people screen.
- More than litigation: the first risk is often a dormant, struck-off or unauthorised vendor, not a lawsuit.
- Run it as a gate: verify at source before the vendor enters the master, risk-tier the depth, keep a dated record.
- Honesty: clean means nothing found in the sources checked on that date, namesake hits need confirming, and it is not a credit score.
01The short answer
Vendor onboarding legal verification has four parts. Confirm the entity is real and active at the Ministry of Corporate Affairs and that its GST registration is valid. Confirm the person contracting can bind the vendor, using the director list and Director Identification Numbers. Check the vendor and its directors for litigation and insolvency across courts, the NCLT and tribunals. Screen the directors for disqualification and economic-offence matters. Do it as a standard step before the vendor enters the master, keep a dated record of what was checked, and refresh it for vendors that carry real exposure. A clean result means nothing found in the sources checked on that date, not a guarantee.
02Why verification is more than a litigation search
A litigation search is one part of the picture. Vendor verification starts earlier and reaches wider, because the first risk is often not a lawsuit but a vendor that is not what it claims:
- The entity may not be valid. A dormant, misdescribed or struck-off company cannot lawfully contract, and paying such a vendor creates its own problems.
- The signatory may lack authority. A contract signed by someone who cannot bind the vendor is weak when you need to enforce it.
- The legal exposure may be hidden. Litigation, recovery actions and insolvency sit behind the entity and its directors, and need their own searches.
For the litigation-only screen built into onboarding, see a litigation check before onboarding a vendor, and for the litigation angle tied to signing the contract, see a litigation check before signing a vendor contract. This page is the broader verification that wraps around them.
03What to verify
A complete onboarding verification covers four layers:
| Layer | Check | Source |
|---|---|---|
| Existence | Active, not under liquidation, not struck off under Section 248 | MCA master data |
| Tax identity | Valid GST registration, trade name match | GST portal taxpayer search |
| Authority | Signatory is a current director or authorised signatory | MCA director list and DIN |
| Litigation and insolvency | Disputes, recovery actions, insolvency petitions | eCourts, NCLT, NCLAT, tribunals |
| People | Director disqualification and economic-offence matters | MCA disqualified-director list, courts |
For the document-and-compliance side of a vendor file, see a vendor due diligence checklist.
04How to run it as a step
Verification works when it is a standard gate, not an occasional favour:
- Collect the basics up front. The registered name, Corporate Identification Number, GSTIN, directors and signatory details, as part of the onboarding form.
- Verify at source. Confirm existence and status at MCA, GST registration at the GST portal, and authority from the director list, rather than from the vendor paperwork alone.
- Search litigation by name. Search the vendor and its directors across the forums at once, and confirm each hit belongs to the vendor. See how to verify a vendor has no litigation and how to add litigation screening to vendor onboarding.
- Risk-tier the depth. A critical or high-value vendor gets a deeper check than a one-off low-value supplier.
05Keeping it current
A check at onboarding speaks for that day. A vendor that was sound when added can slide into disputes or insolvency while it is still on your books and being paid. For vendors that carry real exposure, verification becomes a watch: the same names are monitored, and a fresh suit, a recovery action or an insolvency filing raises an alert so you can hold payments, ask for security or line up an alternative supplier. Running this by hand across several portals for a large vendor base does not scale, which is why most teams use a service that scans and alerts.
06Reading the result honestly
Read the verification with its limits in view:
- Clean is not a guarantee. It means nothing was found in the sources checked, on the date checked, under the names checked. A recent filing or an uncovered forum can still exist.
- Namesake risk. Confirm each hit belongs to the vendor before you act.
- Pending is an allegation. A case in progress is not a finding, and the vendor may be the complainant.
- Not a credit score. Legal verification shows corporate and court records; it does not rate creditworthiness and is not legal advice.
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 litigation and criminal-risk intelligence service, and it does the litigation, insolvency and people layers of vendor verification in one request. Name the vendor, its directors and its group companies, and ClawScore searches across 9,102 courts, benches and forums in seconds, including insolvency at the NCLT and NCLAT, and returns one scored, dated Excel workbook: a Summary risk band (Clean, Low, Moderate or High), a Matters sheet of what was found, a Related parties sheet covering directors, promoters and group entities, and a Coverage sheet showing what was searched, with a match confidence on every finding so a common-name hit is flagged for a human to confirm. You still confirm existence, GST registration and signing authority at MCA and the GST portal, but ClawScore clears the legal-exposure picture in a single pass. Constant Monitoring then watches the active vendor base and reports New filings, Changed movement and Closed disposals on daily, weekly or monthly scans with alerts, so a vendor that slides into trouble after onboarding is caught early. Results return in under 5 seconds, judgment search spans 30 crore+ judgments with Supreme Court decisions from 1950 and High Court decisions from 1990, and Claw does not use your searched names or documents to train its AI models. A ClawScore search starts from Rs 500, and Constant Monitoring is Rs 300, Rs 600 or Rs 3,000 per entity per month by scan frequency and depth. A clean result means nothing was found in the forums covered on the date searched under the names resolved, not a guarantee that nothing exists, and the workbook is a verification input, not a regulated credit score and not legal advice.
To verify a vendor litigation and insolvency at onboarding, run a case search across Indian courts by name across every forum at once.
08Sources and further reading
- Ministry of Corporate Affairs (company and director master data): mca.gov.in
- GST portal (taxpayer search): gst.gov.in
- eCourts (court case status by party): ecourts.gov.in
- National Company Law Tribunal (insolvency): nclt.gov.in
- Claw: clawlaw.in
This page is general information for an Indian B2B audience, not legal advice. Vendor onboarding verification supports a procurement decision and does not replace counsel.
09Frequently asked questions
What does vendor onboarding legal verification cover?
Four layers: confirming the entity is real and active at MCA and not struck off under Section 248; verifying its GST registration on the GST portal; confirming the signatory can bind the vendor using the director list and Director Identification Numbers; and checking the vendor and its directors for litigation and insolvency across courts, the NCLT and tribunals, including a disqualification screen.
How is this different from a vendor litigation check?
A litigation check is one layer. Verification starts earlier, with whether the entity exists and can contract, and whether the signatory has authority, then adds the litigation and insolvency searches on top. The first vendor risk is often a dormant, misdescribed or struck-off company, not a lawsuit, so verification wraps around the litigation check rather than replacing it.
How do I run it without slowing procurement down?
Make it a standard gate. Collect the registered name, Corporate Identification Number, GSTIN and signatory details on the onboarding form, verify existence and status at MCA, GST at the GST portal and authority from the director list, and run the litigation search by name across the forums at once. Risk-tier the depth so critical vendors get more scrutiny than one-off low-value suppliers.
Should verification be repeated after onboarding?
For vendors that carry real exposure, yes. A vendor sound at onboarding can slide into disputes or insolvency while it is still being paid. Those names are worth monitoring, with an alert on a fresh suit, recovery action or insolvency filing, so you can hold payments, ask for security or line up an alternative supplier in time.
Is a clean verification a guarantee the vendor is safe?
No. A clean result means nothing was found in the sources checked, on the date checked, under the names checked. A recent filing, a matter under a group company, or something in a forum outside the search can still exist. Confirm every hit belongs to the vendor, treat pending cases as allegations, and remember it is a verification input, not a credit score or legal advice.