Payment Timelines on GeM, With Real Data

Every week a founder asks for the real number: how many days after go-live does GeM pay. They want a study. We will not write a fake one. We do not have a statistically honest private dataset of GeM payments, and we will not borrow someone else's undocumented average.

What we do have is a process that is public, and a set of clocks that buyers are told to meet. Payment time is the sum of those clocks plus the days nobody owns. This is a data study of structure, not of a fabricated mean. If you need a national aggregate, take it from an official GeM or expenditure dashboard and write the access date in your board pack.

This is not legal advice and not a promise of your next credit.

The chain, in order

1. Contract and delivery period start.
2. You deliver or go live against the acceptance test.
3. Consignee records receipt. On goods, this is often a PRC with a short published clock.
4. Consignee accepts. On GeM this is the CRAC, the Consignee Receipt cum Acceptance Certificate. Buyer help has long spoken of a ten-day style clock after delivery or receipt, sometimes with auto-generation if silent. Confirm live.
5. Invoice / bill is processed on the portal against that acceptance.
6. The paying authority pushes payment, often through PFMS or a CPSE treasury.
7. Money arrives in the registered bank account. GeM transaction charges, if due, are a separate seller-side event.

If you measure days from go-live to cash, you are measuring at least four organisations: you, the consignee, the DDO or paying authority, and the platform. A single average hides which one stalled.

Where days actually go (qualitative, not a study)

Stage	What good looks like	What we hear anecdotally	Owner
Your delivery evidence	Same week as go-live	Weeks, because nobody wrote an acceptance test	Seller + indentor
PRC / receipt	Hours to a couple of days	Consignee on leave	Consignee
CRAC / acceptance	Inside the published GeM clock	Software arguments; CRAC withheld as leverage	Consignee / buyer
Bill pass	Days after a clean CRAC	Missing GST fields, wrong bank, missing sanction	DDO / accounts
PFMS / treasury	A short queue when the bill is clean	Budget not there; PFMS mapping stale	Paying authority

Name the people. Consignee is a role, not a building. If the GeM contract lists a consignee who has never seen the acceptance test, you have already scheduled a delay. Kickoff should include that human, the DDO or bill officer, and the seller's evidence owner. Forty minutes in week one saves a quarter of mail.

Why software is slower than chairs

A chair is accepted when it exists. An agent is accepted when a test that someone forgot to write has been argued. CRAC then becomes a negotiation. Auto-CRAC, if it fires, can pay you for a stack the CISO never signed. Manual CRAC, if it never fires, can starve you for a stack that has been in production for months.

Write the acceptance test into the bid. Name the person who will click CRAC. Put a weekly joint review in the first thirty days. Those three sentences move more cash than a reminder mail in month four.

Two clocks, neither of them a national average

How to use official data, if it exists

• Look on gem.gov.in for buyer or seller dashboards and annual reports that mention payment.
• Look on expenditure and PFMS public notes for bill-cycle commentary.
• Date every figure. Last year's dashboard is not this year's cash.
• Do not average your five invoices and call it India.
• Do not cite a consultant's mean without a method.

Objections from people who want a number

Just say 45 days. Sometimes it is. Sometimes it is 12. Sometimes it is 180. A fake 45 will get a founder killed in a cash plan.

GeM promised prompt payment. GeM can shorten the middle of the chain. It cannot print a treasury balance or invent a consignee.

We will escalate on Twitter. Escalate on the portal, with a complete bill, to the primary buyer. Public heat is a last instrument, not a collection strategy.

How to age a receivable without inventing India

Your board does not need a national mean. It needs your five open GeM contracts split by stage. Not yet delivered. Delivered, no PRC. PRC, no CRAC. CRAC, no bill. Bill, no credit. Each stage has an owner who is not you. Calling the wrong owner is how weeks disappear.

Software acceptance tests should be binary enough that a consignee who is not a machine-learning engineer can click. Workflow X returns an export in format Y. Inference packets do not leave the named VLAN, as shown by the proxy log of date Z. Training flag is off, as shown by the config hash. If your test requires a seminar, you have not written a test. You have written a workshop. Workshops do not generate CRAC.

When you do cite a public figure, cite it like a grown-up. GeM annual report, page, year. A ministry dashboard, accessed on a date. DoE or PFMS note, circular number. If you cannot name the document, you do not have a figure. Founder group-chats that say everyone waits ninety days are not a dataset. They are a mood. Moods are allowed in a risk register. They are not allowed in a priced working-capital model unless you label them as assumptions you chose.

MSME interest claims, if you pursue them, need a complete accepted bill and a calendar. They are a later instrument. They will not make this Friday's salaries. Design the contract so Friday does not depend on a litigation hobby.

Playbook for a payable software contract

• At bid: name acceptance tests and the CRAC owner.
• At kickoff: confirm bank details, GST and PFMS mapping.
• At go-live: deliver the evidence pack the same day.
• At plus seven days: if no CRAC, write on the portal and to the primary buyer.
• At plus the published clock: treat silence as a contract event, not as rudeness.
• Monthly: age your GeM receivables by stage, not as one blob.

File note for the payment chase

Delivery / go-live: [date], evidence at [link or folio]. PRC: [date or pending]. CRAC: [date or pending]. Invoice on GeM: [date or blocked because]. Paying authority: [name]. Official dashboard figure used in the board pack, if any: [source, date, value]. No unofficial average is relied upon.

Prcept AI writes acceptance tests into the offer so CRAC is a click, not a trial. If a seller cannot tell you who will accept, they have not sold a payable contract.

How a buyer or seller should act on this

Treat “Payment Timelines on GeM, With Real Data” as an operating problem, not a thought piece. A P5 Founder who searches “GeM payment timeline” is usually one bid, one CRAC, or one rejection away from a cash event. The file that wins is the one with dates, document names and a named officer — not a paragraph that restates GeM’s homepage.

There is no honest private dataset here of average GeM delay. There is a machine: delivery, PRC, CRAC, bill, PFMS. Manage that machine. Cite official dashboards for aggregates. That is why this data study ends in artefacts: screenshots of the live portal term, the clause you invoked, and the date you last checked it. GeM, GFR notes and state portals move. A citation without a date is folklore.

Confirm the live GeM FAQ, the current revenue policy and the bid text before you copy any number from a blog — including this one. If the portal and this article disagree, the portal wins. Put the printout in the file.

• Write the purpose of the buy in one sentence a DDO will sign.
• Name the route: catalogue, custom bid, bid, RA, CPPP, or state portal.
• Attach the exemption or preference documents you will actually upload (Udyam, DPIIT, MII, OEM).
• Record who can accept the consignee receipt and who raises the bill.
• Do not invent a category, a PAC, or a price-reasonableness story after L1 is public.

Close this loop before the next CAB

Put “Payment Timelines on GeM, With Real Data” on the next change-advisory or bid-opening agenda as a single line item with an owner. If it cannot earn a line item, it will not earn a control. The owner should be a P5 Founder, not “the vendor.”

Revisit the item when the model, the GeM term, the region, or the SI changes. “GeM payment timeline” is not a one-time workshop. It is a watch item. Date the last check. Unsigned watch items are souvenirs.