Mistakes Vendors Make While Filing UVAM Application

Using Trade Name Instead of PAN Legal Name

This is the number one UVAM rejection reason.

What vendors do:

• Enter brand name or shop name

• Ignore PAN database spelling

What the system checks:

• PAN legal name (character-to-character match)

Aadhaar of Unauthorized Person Used

Common scenario:

• Employee Aadhaar used

• Accountant’s Aadhaar used

• Relative’s Aadhaar used “for convenience”

Compliance rule:

Only the legally authorized person can authenticate:

• Proprietor

• Partner

• Director / authorized signatory

Using the wrong Aadhaar immediately flags the account as high risk.

Bank Account Not Matching Entity Type

High-risk mistakes:

• Personal savings account for company/LLP

• Joint bank account

• Account in trade name instead of PAN name

System expectation:

• Proprietorship → proprietor’s account (PAN-matched)

• Company/LLP → entity current account

Impact:

Even if UVAM gets approved temporarily, payments can get blocked later.

Ignoring Authorization Documentation

Many vendors upload documents but fail to prove authority.

Common lapses:

• No board resolution

• Vague authorization letters

• Missing signature or date

Compliance expectation:

GeM must know who can legally bind the entity in Government contracts.

Missing authority = manual rejection.

GST–PAN Mismatch Ignored

Typical issues:

• GST amended, PAN not aligned

• GST suspended or inactive

• Address mismatch between GST and PAN

UVAM cross-checks GST data in real time.

Misconception:

“GST is optional, so UVAM won’t check it.”

➡ Incorrect. If GST exists, it must match.

Uploading Poor-Quality or Edited Documents

Seen frequently:

• Blurred scans

• Cropped PAN or Aadhaar

• Screenshots instead of PDFs

• Edited or masked documents

Audit risk:

Poor-quality documents raise tampering suspicion and lead to rejection.

Repeated Edits During Verification

Some vendors keep editing data while UVAM is under verification.

What happens:

• Each edit resets the verification cycle

• Status remains “Under Review” indefinitely

Compliance logic:

UVAM works on a freeze-and-verify model.

Assuming UVAM Is a One-Time Formality

Dangerous assumption:

“Once approved, no need to worry again.”

Reality:

• Bank change

• Director change

• GST amendment

• Constitution change

➡ All require re-validation.

Ignoring updates can lead to sudden payment blockage.

Believing in “Fast-Track” or “Influence” Claims

Reality check:

• UVAM is system-driven

• No manual override exists

• No GeM official can bypass checks

Paying for “guaranteed approval” often results in wrong filings and future suspension.

Compliance Summary Table