Requesting Updates to a Registered Vendor Profile

Already-approved vendors don't need to re-register from scratch when their details change. Instead, they use the Registration Form Update Request tab, click New Registration Form Update Request, select what needs updating, attach supporting documents, and submit for review.

Show Image The Registration Form Update Request screen, showing a list of update requests with their Reason, Detailes To Be Updated, Status, Requester, Supporting Documents, and Approval Remark.

Full step-by-step process:

1. Go to Vendor Registration & Approval → Registration Form Update Request.
2. Click + New Registration Form Update Request.
3. Enter a clear Reason for Updation — for example, "Change in name," "Request for bank details and PAN details update," or "Update Registered Address."
4. Select the specific detail category to update using the tag selector — options include Company Details, Contact Person, Registered Address, Bank Details, and GST Details. You can select more than one if multiple things changed together.
5. Attach any supporting documents required for verification (e.g., a new GST certificate, a cancelled cheque for bank changes, or an updated address proof).
6. Submit — the request appears in the list with status Active, pending review.
7. Track the request in the same list — once reviewed, its status changes to Approved or Rejected, along with an Approval Remark from the reviewer.

Real examples from the update request log:

• "CHANGE" under Contact Person → Approved with remark "OK."
• "Request for bank details and pan details update" under Bank Details + GST Details → Approved with remark "okay you can update."
• "change for test" under Company Details → Rejected (no remark given, indicating insufficient justification).
• "TEST 2" under Company Details → Approved with remark "OK," showing even test-labeled requests are still formally reviewed, not auto-approved.

Why this workflow exists instead of direct editing: Vendor master data — especially bank details and GST — directly affects payments and tax compliance. By routing every change through a reviewed request with mandatory supporting documentation, the portal prevents unauthorized or fraudulent changes to sensitive vendor information.

The full lifecycle of a request, end to end:

1. Draft/creation — vendor fills the New Registration Form Update Request form.
2. Active — submitted and sitting in the reviewer's queue.
3. Under review — reviewer opens it, checks reason and documents.
4. Decision — Approved (vendor master data is updated) or Rejected (data stays as-is, reason logged).
5. Closed — visible permanently in the history list for audit purposes.

Frequently Asked Questions

How long does an update request typically take to review? 

This depends on your organization's internal SLA, but requests with clear reasons and complete supporting documents are generally reviewed faster.

Can I withdraw an update request after submitting it? 

If it's still in Active status, contact your internal approver — once a decision (Approved/Rejected) is recorded, the request is considered closed.

What happens if my update request is rejected? 

Review the Approval Remark (if provided) for the reason, correct the issue — often a missing document or unclear justification — and submit a new request.

Can I update multiple detail categories in a single request? 

Yes, the "Detailes To Be Updated" field supports multiple tags (e.g., both Bank Details and GST Details) in one request if the changes are related.

Do I need to attach a document for every type of update? 

It's strongly recommended for any sensitive change (bank details, GST, company name), even if not strictly enforced for minor changes like a contact person's phone number.

Is there a way to see all my past update requests, both approved and rejected? 

Yes — the Registration Form Update Request screen maintains a full running list of every request you've submitted, along with its final status and remark.