GeM Seller Registration: Documents and Controls Before Government Orders
A GeM onboarding control covering authorised users, business credentials, bank and GST records, catalogue evidence and internal access.
Use the GST Registration Applicability Checker to apply these points to your figures or facts.
A GeM onboarding control covering authorised users, business credentials, bank and GST records, catalogue evidence and internal access. The objective is to convert a financing, collection or compliance issue into a cash impact, evidence file, accountable owner and dated next action.
GeM seller onboarding requires an authorised primary user and business-entity credentials that should match PAN, bank and GST records where applicable.
Catalogue, brand, OEM, reseller, country-of-origin and technical claims need supporting evidence under the relevant GeM rules.
Primary and secondary user access should be controlled because bids, prices, order acceptance and acknowledgements can bind the seller.
Former employees, shared mobile numbers and uncontrolled email access create procurement and fraud risk.
What the business should understand
- GeM seller onboarding requires an authorised primary user and business-entity credentials that should match PAN, bank and GST records where applicable.
- Catalogue, brand, OEM, reseller, country-of-origin and technical claims need supporting evidence under the relevant GeM rules.
- Primary and secondary user access should be controlled because bids, prices, order acceptance and acknowledgements can bind the seller.
- Former employees, shared mobile numbers and uncontrolled email access create procurement and fraud risk.
- Registration does not guarantee an order, qualification in every bid or prompt payment.
For the connected rule, example or next step, see Property Sale Tax: Documents Before Reporting Capital Gains.
The five-point review
| Check | What to examine |
|---|---|
| User access | Primary user, secondary users and authorisations. |
| Contract | Bid, order, GTC, STC and ATC. |
| Supply | Consignee, delivery, inspection and warranty. |
| Acceptance | Receipt, CRAC or equivalent evidence. |
| Payment | Invoice, deductions, due date and escalation. |
Practical example
A former employee remains the primary GeM user and accepts an order at an outdated price. The company is contractually exposed before management notices.
How to apply the framework
Start from the live legal and commercial record
Verify the legal entity, current Udyam status, customer or lender identity, contract, sanction, purchase order, invoice and portal record. A spreadsheet or certificate stored at incorporation does not prove that the enterprise, category, activity, buyer, facility or claim remains current. Match names, PAN, GSTIN, bank details, dates and authorised users before money moves.
Reconcile the operating evidence
Connect purchase order, delivery or service completion, acceptance, invoice, credit note, customer ledger, GST reporting and bank receipt. For a bank facility, connect the sanction to eligible inventory, receivables, creditors, insurance and monthly submissions. Differences should be explained through a written bridge rather than hidden in a round number.
Quantify cash before choosing the remedy
Show when cash leaves and when it is realistically expected to return. Include payroll, GST, TDS, debt service, critical suppliers and minimum operating cash. Compare a base case with customer delay, lower sales, margin compression or loss of drawing power. A profitable order can still be dangerous when tax, inventory and financing are funded months before collection.
Use the current portal, scheme and contract
New delayed-payment applications should follow the current MSME ODR workflow while Samadhaan remains relevant for monitoring, reference and legacy matters. Government credit guarantees, MUDRA categories, GeM orders, e-invoice rules and bank facilities do not create automatic approval or payment. The actual sanction, electronic contract, guarantee instrument or insurance policy wording controls the commercial exposure.
Close the loop with proof
Assign one owner, one deadline and one measurable result. Verify buyer acceptance, financier settlement, lender statement, portal conversion, signed restructuring, tax filing or actual bank credit. An application number, email promise, provisional bid, stock statement or unsigned settlement should not be reported as completed.
Implementation checkpoint
Before marking the issue closed, reconcile the final accounting entry, bank movement, GST or tax record, lender or customer ledger and supporting acknowledgement. Record the reference number, date, residual amount, next review date and unresolved exception. Preserve the actual policy wording or instrument terms wherever insurance, guarantee or contingent cover is involved.
Action checklist
- Verify portal users and roles.
- Read the full electronic contract.
- Validate catalogue and bid evidence.
- Control dispatch and consignee proof.
- Secure inspection and acceptance.
- Reconcile invoice, deduction and payment.
Evidence to keep
- Seller profile and user authorisation
- Bid and electronic order
- Delivery and inspection records
- CRAC or acceptance evidence
- Invoice, deduction and payment trail
Warning signs
- Former employee controls account
- Order accepted at wrong price
- Wrong consignee
- Acceptance evidence missing
- Payment follow-up lacks contract reference
Finin2min takeaway
MSME finance improves when every sale, invoice, tax payment, bank drawing and recovery action has traceable evidence, an owner and a cash date.
Frequently Asked Questions
Source and review trail
Use the current official instrument, portal or regulator publication before acting. This panel separates the category authority from page-specific references.
- Primary category
- Corporate Finance & CFO
- Official starting point
- www.gstcouncil.gov.in