Vendor Lifecycle &
Compliance Management
Part of the procurement governance chain — structured onboarding, compliance document tracking, performance scoring, and debit notes
The Challenge
Vendor records are scattered across POs, emails, and paper files. There is no single view of a vendor's status, compliance documents, or transaction history.
Expired GST registrations, lapsed MSME certificates, and outdated bank details are caught only during statutory audit — not when the PO is raised.
Without structured data on delivery timelines, rejection rates, and debit notes, vendor performance evaluation relies on memory and informal feedback.
How We Address This
Vendor Lifecycle
Vendors progress through defined states: DRAFT, PENDING, ACTIVE, SUSPENDED, BLACKLISTED, DEACTIVATED. Every status change is logged with timestamp and user. Approval workflows gate vendor activation.
Compliance Tracking
GSTIN, PAN, MSME classification, TDS section applicability, and credit limits are maintained per vendor. Document expiry alerts trigger 90 days before lapse. Expired documents are flagged on vendor records and PO creation screens.
Vendor Details
Multiple addresses, bank accounts with IFSC validation, contact persons, and commodity classifications. All stored in a structured format with full edit history.
Performance Scoring
Computed from PO, GRN, and VDN history. Factors include delivery timeline adherence, acceptance rate, rejection count, and debit note frequency. Objective, data-driven vendor evaluation.
Vendor Debit Notes
Five types: REJECTION, UNDER_RECEIVED, DAMAGE, PRICE_EXCESS, and SHORT_LANDED (short-landing recovery on imports, with foreign-currency vendor or insurer routing). Each VDN generates a GST-compliant PDF with line-level detail and posts the corresponding accounting entry to Tally automatically. See vendor debit notes for the full type-by-type breakdown.
Submission Workflow
Vendors progress through a governed submission cycle. The creator submits a draft for approval — the system validates that at least one address exists and TDS details are complete before accepting the submission. Once submitted, all vendor fields and subsidiary records (addresses, bank accounts, documents, contacts) are locked to read-only. The creator can recall a submission back to draft. Administrators can return a submission with a comment for corrections. Timestamps and actors are recorded at every transition.
Compliance Report
Generate a vendor compliance report with a configurable lookahead window (1 to 365 days). Filter by vendor status, category, or include procurement spend data. The report surfaces vendors with expiring documents, missing statutory details, or lapsed registrations — before they become audit findings.
Bulk Upload
Import vendor records via CSV or XLSX with row-level error reporting. Validation errors are returned per row — fix and re-upload only the failed entries.
Multi-currency vendors
For organisations that purchase from foreign suppliers, every vendor carries a billing currency code on the vendor master record. The supported currencies are: INR, USD, EUR, GBP, CNY, JPY, SGD, AED. The default is INR; the field is required and is part of the vendor master, not a per-transaction override.
The vendor master is the single source of truth for currency. When the vendor ledger is created in Tally, it is created in the vendor's billing currency. Every PO, GRN and VDN posting against that vendor carries the foreign amount and the exchange rate inline, so Tally handles the forex math, settlement gain or loss on payment, and period-end revaluation natively — using its built-in workflow.
One vendor record holds one currency. If a supplier bills you in both INR and USD, you maintain two vendor records (one per currency). This mirrors a constraint Tally enforces on its own ledger: a single ledger holds a single currency for its lifetime.
The vendor's billing currency flows downstream into the procurement chain automatically. Approvers, mismatch resolvers and PDF templates all see amounts in the vendor's billing currency where appropriate — no manual conversion at any step.
How Vendor Management Fits into Procurement
Vendor management is not a standalone module — it is integrated into the procurement workflow. When a purchase order is created, the vendor's compliance status is visible: GSTIN validity, document expiry, TDS section, MSME classification. When a goods receipt reveals quantity or quality issues, the system generates a vendor debit note — linked to the PO, the GRN, and the vendor's performance record.
Over time, the vendor's delivery history, rejection rate, and debit note frequency build a performance profile. Procurement decisions — which vendor to use for the next PO — are informed by data from the same system, not by memory or informal feedback.
Further Reading
Vendor Document Expiry TrackingUrgency-based monitoring so certificates never lapse unnoticed.
GST ITC Reversed — Vendor GSTIN IssuesThe consequence of not tracking vendor GSTIN validity.
Vendor Debit Note ProcessFrom rejected goods to formal recovery with GST-compliant documentation.
Assess How This Applies to Your Organisation
Share a brief overview of your setup and we will evaluate how our services may apply.