Vendor Onboarding Checklist for India: GST, PAN, MSME and Bank Verification

Adding a new vendor should be a controlled business process—not a collection of emails, spreadsheets and unverified attachments.

However, many Indian finance and procurement teams begin working with suppliers before all the required documents have been collected and verified. GST certificates may remain unchecked, bank details may arrive through informal emails, MSME status may not be recorded, and vendor agreements may be stored separately from the vendor master.

These gaps usually become visible later, when an invoice is blocked, a payment is sent to an incorrect account, input tax credit documentation is incomplete, or an auditor asks for the complete vendor file.

A structured vendor onboarding checklist helps finance, procurement, legal and compliance teams verify every supplier before purchasing or payment activity begins.

What Is Vendor Onboarding?

Vendor onboarding is the process of collecting, verifying, approving and organising the information required to activate a supplier in a company's systems.

The process normally starts after a vendor is selected and ends when:

• The vendor's identity has been verified.
• Tax and MSME information has been recorded.
• Bank details have been independently checked.
• Commercial terms have been approved.
• Agreements have been executed.
• The vendor code has been created.
• The complete vendor file has been stored securely.

Vendor onboarding is different from vendor selection. Selection determines whether the supplier is commercially suitable. Onboarding determines whether the supplier is properly documented and ready to transact.

Why Finance Teams Need a Vendor Onboarding Checklist

An incomplete vendor file affects more than procurement.

Finance teams depend on reliable vendor information for invoice validation, tax treatment, payment processing, TDS decisions, MSME payment monitoring and audit preparation.

Without a defined checklist, organisations commonly experience:

• Duplicate vendor records.
• Incorrect legal names or GSTINs.
• Payments sent to outdated bank accounts.
• Missing agreements and approval records.
• Unrecorded MSME status.
• Delayed invoice processing.
• Difficulty producing vendor documentation during audits.
• Unclear ownership when vendor information changes.

A standard checklist creates one controlled process across procurement, finance, legal and business teams.

Complete Vendor Onboarding Checklist for India

1. Business Identity Documents

Begin by confirming that the supplier exists as a valid business entity.

Depending on the vendor's constitution, collect the applicable documents:

• Legal business name.
• Trade name, where different.
• PAN.
• Certificate of incorporation or registration.
• Partnership deed or LLP information.
• Registered office address.
• Operating or correspondence address.
• Authorised representative details.
• Contact email and telephone number.
• Nature of goods or services supplied.

The legal name should remain consistent across the PAN, GST registration, bank account, agreement and invoices.

Differences such as abbreviations, old business names or spelling variations should be resolved before the vendor is activated.

2. GST Registration and Tax Information

For GST-registered suppliers, collect the GST registration certificate and record:

• GSTIN.
• Legal business name.
• Trade name.
• Registration status.
• Principal place of business.
• State and jurisdiction.
• Taxpayer type.
• Effective registration date.

The GST Portal provides a taxpayer-search facility through which a business profile can be viewed using the GSTIN or UIN. Finance teams should verify the information instead of relying only on a certificate sent by the vendor.

The invoice details received later should also match the approved vendor master. CBIC invoice rules require prescribed information such as the supplier's name, address, GSTIN, invoice number and issue date.

Record whether the vendor is:

• Regularly registered.
• Under the composition scheme.
• Unregistered.
• Registered in multiple states.
• Required to issue e-invoices, where applicable.

This information helps the accounts team apply the correct validation process when invoices arrive.

For more information about the next stage of the process, link this section to Kleeto's invoice processing and archival solution.

3. MSME and Udyam Verification

Ask every vendor whether it is registered as a Micro, Small or Medium Enterprise.

Where applicable, collect:

• Udyam Registration Number.
• Udyam certificate.
• Enterprise classification.
• Major business activity.
• Registration date.
• Confirmation of whether the supplier qualifies as a Micro or Small Enterprise for delayed-payment provisions.

The official Udyam portal supports online verification of registration details. It also explains that registration is paperless, receives a permanent number and does not require renewal.

MSME classification should not remain buried in an attachment. It should be recorded as a structured field in the vendor master so that finance teams can identify applicable suppliers when monitoring payment timelines.

Under the MSMED Act, an agreed payment period for eligible Micro and Small Enterprise suppliers cannot exceed 45 days from acceptance or deemed acceptance.

Because classifications and business details can change, companies should define a periodic re-verification process instead of treating the certificate as a permanent, one-time check.

4. Bank Account Verification

Bank information is one of the most sensitive parts of the vendor onboarding process.

Collect:

• Account holder name.
• Bank name.
• Branch.
• Account number.
• IFSC.
• Account type.
• Cancelled cheque or bank-issued proof.
• Signed declaration, where required.

The account holder's name should match the vendor's legal or approved business name. Any difference should be documented and approved.

Bank details should never be changed solely on the basis of an email from a vendor contact. Use an independent verification process, such as:

• Receive the change request through an authorised channel.
• Compare the request with existing vendor information.
• Contact a previously verified representative.
• Obtain supporting bank proof.
• Route the change through maker-checker approval.
• Preserve the request and approval history.

The person who creates or modifies the vendor record should not be the only person approving the change.

5. Commercial and Contractual Documents

Before activation, confirm the commercial terms under which the vendor will operate.

The vendor file may include:

• Approved quotation.
• Purchase terms.
• Rate contract.
• Master services agreement.
• Statement of work.
• Non-disclosure agreement.
• Service-level agreement.
• Code of conduct acceptance.
• Data-protection obligations.
• Insurance certificates.
• Industry-specific licences.
• Payment terms.
• Credit period.
• Tax and TDS declarations.
• Renewal and termination dates.

Signed contracts should be linked directly to the vendor record rather than stored in an unrelated legal folder.

Kleeto's e-contract software supports vendor-agreement templates, Aadhaar eSign or DSC, e-stamping workflows, version history, searchable archival and renewal reminders.

6. Internal Risk and Approval Checks

Document collection is not the same as approval.

Every organisation should define who reviews and approves each area of the vendor file.

A typical approval flow may involve:

• Procurement: commercial selection and category validation.
• Requesting department: business need and scope.
• Finance: tax, bank and payment information.
• Legal: agreement and liability terms.
• Information security: technology or data-access risk.
• Compliance: sanctions, conflicts or regulatory checks.
• Management: high-value or high-risk vendors.

Approval limits should vary by vendor category, contract value, service type and risk.

For example, a stationery supplier should not require the same review process as a technology provider receiving customer data or a contractor working at multiple company locations.

7. Vendor Master Creation

Create the vendor record only after the required checks are complete.

The vendor master should include structured fields such as:

• Unique vendor code.
• Legal name.
• Trade name.
• PAN.
• GSTIN and state registrations.
• Udyam status.
• Vendor category.
• Payment terms.
• TDS category.
• Bank information.
• Contract owner.
• Agreement validity.
• Business owner.
• Risk classification.
• Last verification date.
• Next review date.
• Active, blocked or inactive status.

Avoid creating separate records for spelling variations, branch names or different contact persons unless there is a genuine legal or accounting reason.

8. Secure Vendor Document Storage

Vendor documents contain tax identifiers, addresses, bank details, signatures, contracts and personal contact information. These files should not remain spread across employee inboxes and shared folders.

Use a controlled document management system for Indian businesses that can provide:

• Centralised vendor files.
• Metadata-based search.
• Role-based access.
• Version control.
• Approval workflows.
• Complete activity logs.
• Retention policies.
• Expiry and renewal reminders.
• Controlled document sharing.
• Integration with ERP or procurement systems.

Kleeto's DMS supports document-level controls, workflow automation, retention rules, audit-ready archival and searchable metadata.

Recommended Vendor Onboarding Workflow

A practical supplier onboarding process can follow these eight stages.

Step 1: Initiate the Request

The requesting department submits the business reason, proposed supplier, category, expected value and required start date.

Step 2: Send One Document Request

Send the vendor a complete checklist rather than requesting documents through multiple email exchanges.

Step 3: Collect Documents Through a Controlled Channel

Use an onboarding portal or secure upload link instead of asking vendors to send sensitive documents through informal messaging applications.

Step 4: Verify the Information

Check GSTIN, Udyam status, legal name, bank proof and applicable licences against approved sources.

Step 5: Resolve Exceptions

Return incomplete or inconsistent submissions to the responsible person. Do not activate a vendor merely because a purchase is urgent.

Step 6: Route for Approval

Send the complete vendor file to the appropriate finance, procurement, legal and compliance approvers.

Step 7: Create the Vendor Master

Create a unique vendor code and connect it with the approved documents and agreements.

Step 8: Schedule Re-Verification

Create alerts for expiring licences, agreements, insurance, bank updates and periodic vendor reviews.

Common Vendor Onboarding Mistakes

Collecting Documents Without Verifying Them

A submitted GST or Udyam certificate should not automatically be treated as current and accurate.

Accepting Bank Changes Through Email Alone

Payment-redirection fraud often depends on creating urgency around a bank-account change. Independent verification and dual approval are essential controls.

Failing to Record MSME Status

When Udyam information is stored only as an attachment, the accounts team may not know that a vendor requires specific payment monitoring.

Creating Vendors Before Approval

Temporary or urgent vendor records often become permanent records with incomplete documentation.

Keeping Agreements Separate from Finance Records

The finance team needs access to payment terms, tax clauses, milestones and commercial conditions when processing invoices.

Never Reviewing Existing Vendors

Vendor information can become outdated. Bank accounts, GST registrations, addresses, ownership, licences and contracts may change.

How Vendor Onboarding Improves Invoice Processing

A clean vendor master improves every later financial transaction.

When an invoice arrives, the system can compare it with approved information such as:

• Legal vendor name.
• GSTIN.
• Purchase order.
• Payment terms.
• Bank account.
• Contract.
• Tax treatment.
• MSME status.
• Approval authority.

This reduces exceptions, duplicate records and manual follow-ups.

Read Kleeto's guide to invoice automation for finance teams in India for the next stage of the accounts-payable workflow.

How Kleeto Supports Vendor Document Management

Kleeto helps businesses manage vendor onboarding as a connected document workflow rather than a collection of emails and spreadsheets.

Finance and procurement teams can use Kleeto to:

• Collect vendor documents securely.
• Index files by vendor code, PAN, GSTIN and category.
• Route submissions for approval.
• Track missing documents.
• Execute vendor agreements digitally.
• Maintain versions and activity logs.
• Set expiry and renewal reminders.
• Link vendor documents with invoices and supporting records.
• Retrieve complete vendor files during audits.

Explore Kleeto's finance document management solution to understand how vendor, invoice and audit records can be organised within one controlled system.

Conclusion

A reliable vendor relationship begins before the first purchase order or invoice.

By following a structured vendor onboarding checklist for India, businesses can verify tax information, protect vendor payments, record MSME status, maintain signed agreements and create a complete audit-ready vendor file.

The objective is not simply to collect more documents. It is to ensure that every approved vendor is identifiable, verified, authorised and connected to a controlled financial workflow.

When vendor onboarding, contracts, invoice processing and document management work together, finance teams spend less time resolving preventable exceptions and more time managing cash flow, compliance and supplier performance.