GeM Seller Registration: Common Rejections

The most common GeM onboarding story in Indian AI is not a policy conspiracy. It is a private limited that changed its name, a GST certificate that still shows the old address, a cancelled cheque from a current account opened in the brand name, and a DPIIT letter issued to the founder's earlier LLP. The portal's KYC is a matching engine. Matching engines are unromantic.

This troubleshooting guide is for founders and ops leads who have a red status and a buyer who wants a listing last week. It is not official GeM support. Screens and required documents change. Read the live seller FAQ and the rejection remark. Then use the patterns below. Do not invent fee amounts or always 72 hours SLAs; those drift. If you are a buyer reading this, it will also tell you why the startup that demoed brilliantly is not yet a legal seller. Give them a document week. Do not invite them to a bid that requires a live GeM id they do not have.

The matching engine: one legal person, many spellings

Pick the legal entity that will invoice the government. Every other document must use that exact name, including Private Limited versus Pvt. Ltd. versus the old trading style. If you rebranded last year, either update every certificate or stop using the new brand on KYC fields. PAN, GSTIN, bank account, authorisation letter, board resolution, and the person who clicks OTP should form a closed loop. A director who left, a signatory who is only in the bank and not in MCA, or a GST login that belongs to the CA's intern, will fail in different weeks but they will fail. Addresses must be defensible. The GST principal place, the MCA registered office, and the address on the cancelled cheque letter may differ in real life. If they do, be ready with the current GST certificate and an explanation the console allows. A WeWork that is not on GST is a classic stall.

Read the remark. Most GeM is against startups threads are one of these eight rows.

Rejection remark (paraphrased)	Usual real cause	Fix that actually works
Name mismatch	Brand vs legal name; LLP vs Pvt Ltd; spelling	Use MCA exact name everywhere; reissue letters
GST not valid / cancelled / mismatch	Old GST, wrong state, composition issues, address	Download current GST certificate the same day you upload
Bank details mismatch	Cheque in brand name; space in IFSC; dormant account	Cancelled cheque of the entity current account; typed IFSC checked
Authorisation / board resolution	Unsigned, old director, no DIN, PDF of a photo	Fresh resolution, readable scan, person matches Aadhaar/PAN
OEM / brand authorisation	Letter for another entity or expired	Re-issue to the seller's exact legal name
DPIIT / Udyam not accepted	Expired, wrong entity, not claimed in the right field	Current certificate; do not claim if it is not yours
Document unreadable	Phone photo, cut-off PAN, passworded PDF	Flat scan, no password, all four corners
Already registered	Old attempt with another email / GST	Recover the old seller id; do not create a twin

Startup and MSE claims — useful, not magical

DPIIT recognition, via Startup India, can support certain relaxations — often EMD and some prior-experience or turnover relief — when the bid and the portal allow the claim and when the certificate is current and in the seller's name. It does not skip KYC. It does not skip isolation rows. It does not skip GST. Udyam registration similarly matters for MSE purchase preference on many GeM flows. Typical preference logic, described in GeM FAQs and the public procurement policy for MSEs, is a price-match window against L1 (commonly spoken of as L1 + 15%) and the possibility that a buyer involves more than one MSE. Confirm the live FAQ. Do not type 15% into a bid if the portal text that day says something else. And do not claim Udyam if you are not an MSE under the current definition. Upload current PDFs. A recognition letter from three years ago that nobody renewed is not a personality trait. It is a rejection.

The ops habit that clears faster than a consultant

Make one person the GeM owner — usually finance plus a founder, not a marketing intern. Keep a folder: MCA master data print, PAN, GST, cancelled cheque, resolution, DPIIT, Udyam, OEM letters. Re-download GST and Udyam the day you upload. If rejected, fix the remarked document only, unless the remark is name mismatch, in which case fix the system of names. Re-uploading the same photo is how you lose another week. Do not open a second seller account to try again. Twins create already registered loops that support tickets hate. Consultants can upload. They cannot invent a GST address. If a consultant promises a listing for a fee while your names still disagree, you are buying a second rejection. This article will not quote their fees; they change and they are not official.

1. Freeze the legal entity and its exact spelling.
2. Align PAN, GST, bank, resolution, certificates.
3. Upload readable, current, unpassworded PDFs.
4. Read the rejection remark; change that artefact.
5. Claim DPIIT/Udyam only with live, same-entity letters.
6. Then, and only then, start a catalogue (see the listing article).

Objections you will hear — and what to do with them

These are the lines that stall the file. Answer them in the room, then put the answer in the note. A spoken answer without paper will be forgotten by the next officer.

GeM rejects startups on purpose.

GeM rejects mismatched KYC on purpose. Startups with aligned papers get through every week. If you have aligned papers and a remark that is wrong, use official support — not a Twitter verdict.

Our CA will handle it next month.

Then do not promise a buyer a bid next week. GeM id is on the critical path. Put it on the same board as the product milestone.

We will bid as a partner's seller id.

Then the partner is the seller. Your isolation promises may not bind. If you are the product, be the seller or be a named OEM with letters. Borrowed ids are how money and liability separate.

A five-day KYC war room

1. Day 1: print MCA name, PAN, GST, bank, directors. Circle mismatches in red.
2. Day 2: re-issue whatever is red — cheque, resolution, letters.
3. Day 3: re-download GST, Udyam, DPIIT. Scan cleanly.
4. Day 4: upload; one owner clicks; no twins.
5. Day 5: if rejected, fix only the remarked item; file the remark in the war-room folder.

How this shows up in the file

Keep the rejection remarks. They are how you brief the next hire. Keep the final green screenshot and the entity name used. Catalogue work starts after green, not during red. Buyers: if a startup is red, do not write them into a bid that needs a seller id this fortnight unless you like corrigenda.

A pre-upload checklist on one page

MCA exact name. PAN. GST certificate downloaded today. Bank cancelled cheque of the entity. IFSC typed and checked. Board resolution dated this month, signatory matches. Aadhaar/PAN of the clicker. DPIIT current and same entity, or do not claim. Udyam current and same entity, or do not claim. OEM letters same name. No passworded PDFs. No phone photos with thumbs. No second seller id. One owner. If any box is unchecked, do not upload yet. Hope is not a document. Put this page on the wall of the war room. Consultants should initial it. If they will not, they are not ready to take your OTP.

Talking to official support without making it worse

When you raise a ticket, quote the remark, attach the new artefact, and state the legal name once. Do not attach a manifesto about startups. Do not open a parallel ticket with a different email. Do not change the GST mid-ticket unless that is the fix. Support is a matching engine with humans on top. Help the matcher.

After green, do not drift

When directors change, when you move office, when GST updates, when you convert again, reopen the folder. Stale KYC that was green last year becomes a listing freeze in the week of a bid. Calendar a semi-annual KYC review next to your tax calendar. Green is also when you start the catalogue, not when you start promising buyers a SKU. Sequence is KYC, listing, bid. Reversing it is how you write corrigenda for other people.

What the next noting must contain

“GeM Seller Registration: Common Rejections” belongs in a file, not only in a search result. A P5 GovTech Founder should be able to point at one artefact that proves “GeM registration rejected”: a packet capture, a processing schedule, a scored evaluation row, a dated notice, or a refusal rule. If the only evidence is a slide, you have a heading.

GeM does not reject you because you are a startup. It rejects you because PAN, GST, bank, address and the letterhead name are four different companies in a trench coat. DPDP 2023 does not define sovereign AI and does not write a blanket localisation rule for every model hop. CERT-In’s 28 April 2022 directions still set specified incident clocks and 180-day log retention in India for in-scope events. The November 2025 AI governance text is guidance, not a statute. A Proprietary Article Certificate, when it is lawful, lives in GFR Rule 166 — not Rule 161.

Write three dated sentences under C3 GeM & Procurement: what was decided, which designation owns it after the next posting order, and when it will be re-checked. Unsigned sentences are souvenirs. Dated sentences are controls.

• Name the designation that owns “GeM registration rejected”, plus a deputy.
• Attach one artefact a stranger can open next year.
• Name the instrument you are actually using — Act, direction, GFR clause, GeM term, or guideline paragraph.
• Leave unsourced percentages, GMV slides and house forecasts out of the noting.
• Revisit when the model, the SI, the notice, the region or the posting changes.

This article is informational field guidance, not legal or procurement advice. GeM screens, fees and queues change. Confirm on gem.gov.in and current FAQs before you act.