Vendor Onboarding: PAN, GST, Bank and Conflict Checks

The purpose is to turn an operational issue into a measurable exposure, reconciled evidence, an accountable owner and a dated closure.

What management should understand

• Cross-check that the legal name, PAN and GSTIN on the vendor record match the name on the bank account the payment will actually reach - not just the invoice letterhead.
• Look up the GSTIN directly on the GST portal rather than trusting a certificate copy the vendor supplies.
• Flag any vendor address, bank account or director that matches an employee’s own details, and route those through a second, independent approver.
• Treat every bank-account-change request as suspicious by default until verified through a channel OTHER than the email that raised it - a callback to a known number, for instance.
• Keep the person who can CREATE or EDIT a vendor record separate from the person who can RELEASE a payment to that vendor.

Use the Finin2min GST Services Rate Master to apply these points to your figures or facts.

The five-point control review

Practical example

Implementation workflow

1. Define the transaction and the decision

State precisely what is being measured or approved: a month-end balance, customer order, product cost, purchase, tax credit, payroll run, bank payment, investment or export document. Set the period, legal entity, business owner, reviewer and materiality. A control cannot work when the team is reviewing different transactions or dates.

2. Lock the source evidence

Collect the signed contract, approved master data, invoice, receipt, timesheet, inventory record, payroll file, portal statement, bank transaction or system log. Preserve the original version and document subsequent amendments. Official portals are important external records, but they do not replace the underlying commercial evidence or the books.

3. Reconcile value, quantity, date and identity

Match legal names, PAN or GSTIN where relevant, document numbers, quantity, amount, tax, due date, payment account and approval. Separate timing differences from errors and suspected fraud. An unexplained difference should remain open with an owner; it should not be forced into a suspense or miscellaneous account merely to complete the close.

4. Assess tax, payroll, cyber and contract boundaries

GST registration thresholds are not one universal number: the threshold for suppliers of goods can differ from services, and specified States can have lower limits. Compulsory-registration provisions, e-invoice history, e-way-bill rules, EPF or ESIC coverage and contract terms require separate analysis. Where insurance, guarantees or cyber cover are involved, the actual policy wording or instrument terms control the outcome.

5. Quantify the cash effect

Show the immediate payment or receipt, working-capital days, tax timing, finance cost and downside exposure. A transaction can be profitable in the accounts and still create a cash deficit. Use a base case and at least one stress case before accepting a large order, changing price, buying equipment or releasing a disputed payment.

6. Approve, execute and verify

The preparer should not be the only approver where master data, payment or statutory exposure is involved. Record the decision, exception reason and expiry. After execution, verify the live result in the bank, GST portal, payroll return, vendor master, inventory record or management report. A submitted request is not completion.

Action checklist

• Collect verified identity and tax records.
• Validate bank independently.
• Perform conflict declaration.
• Approve vendor master.
• Review inactive and changed vendors.

Evidence to keep

• PAN/GST verification
• Cancelled cheque or bank proof
• Contract and address
• Conflict declaration
• Vendor-master audit trail

Warning signs

Finin2min takeaway