GeM Transaction Fees: What You Actually Pay

A founder in Pune won her first GeM bid for an on-prem helpdesk agent. She had priced the year at a number that already made her CFO wince. Then the platform invoice arrived. She had modelled a percentage she copied from a 2023 LinkedIn carousel. The live policy was different. The margin she had promised the board was a rounding error.

GeM transaction charges are real, they are usually seller-side, and they change. This article tells you how to read the revenue policy, how to put the cost into a government rate card, and what happens if you ignore the invoice. It will not stamp a percentage as the law of the land. Anyone who does that in 2026 is writing a stale brochure.

This is not legal or tax advice. Open gem.gov.in, find the current revenue policy in the policies or manuals section, and work off that PDF. If your accountant needs a number for a model, date the number and put a review trigger on it.

What you are actually paying for

GeM is a public marketplace with a private-looking checkout. The Government of India did not build it as a free noticeboard. The revenue policy is how the platform funds itself: typically a transaction charge on completed orders, sometimes an annual or milestone charge, sometimes caution money at registration, sometimes charges that vary by order value.

Historically, GeM has used slabs. Orders below a threshold have at times attracted no transaction charge. Mid-value orders have attracted a percentage. Very large orders have been capped. In 2024 the platform publicly described a cut in percentages and a much lower cap than the previous regime. Those headlines were true on the day they were issued. They are not a statute. They are a policy GeM can revise.

So the only safe sentence in a board note is: we will apply the GeM revenue policy in force on the order date, currently [title, version, date of PDF], and we will re-read it at each bid. Anything more precise belongs in an appendix with a screenshot of the policy header.

Cost lines founders confuse with each other

Line	Who usually pays	When it hits	Where to confirm
Transaction charge on a completed order	Seller / service provider	After the order, on policy slabs	Current GeM revenue policy PDF
Caution money or similar registration deposit	Seller, with possible MSE treatment	At or after registration	Seller registration help and revenue policy
Bid security / EMD	Bidder, often exempt for MSE and DPIIT startups if documents are current	At bid, if the bid asks	The bid + GFR Rule 170 + Startup India notes
Performance security	Winner, sometimes reduced for MSE/startup if the bid says so	At contract	The bid and contract
Incident-driven moratorium for unpaid charges	Seller	After a missed platform invoice	GeM Incident FAQs and IM policy

How to read the revenue policy without fooling yourself

1. Download the file from gem.gov.in, not from a consultant's Drive folder.
2. Write the version number and effective date on the first page of your pricing model.
3. Find the definition of order value. Inclusive of tax or exclusive changes the rupee.
4. Find the slabs, the cap if any, and any category exceptions. Services and goods have not always been treated identically.
5. Find the invoice trigger: CRAC, payment, or another event. Cash-flow timing is not the same as fee liability.
6. Find the failure mode: what GeM does if you do not pay.
7. Set a calendar reminder to re-download the PDF before every bid above a size you care about.

If a salesperson tells you GeM is free for startups, ask them to highlight the clause. Startup India material is clear about EMD, prior experience and prior turnover relaxations. It is not a substitute for the revenue policy.

Two rooms where the fee is decided

Unpaid charges become an incident

GeM's public incident FAQs are blunt. An incident raised for non-payment of transaction charges or AMC within the timelines in the revenue policy is treated as a temporary moratorium. The FAQ language has described that moratorium as lasting for a stated period or until the payment is made. Read the live FAQ and the Incident Management policy for the current period and process.

A moratorium is not a debate club. You cannot bid your way out of an unpaid platform invoice. If your finance team is slow, treat the GeM invoice like PFMS in reverse: a blocking item. Assign an owner. Pay from a dedicated ledger. Do not wait for the customer to pay you first unless the policy's trigger is actually receipt of payment.

Pricing an agent contract after you know the fee exists

On-prem agent deals have lumpy value. A first-year integration can be large. A second-year support renewal can be small. Slabs and caps, if the live policy has them, will treat those years differently. Model each year. Do not amortise the platform fee in your head and forget it in year two.

• Put the live policy version in the bid workings.
• State internally whether you will absorb a mid-contract policy change.
• Do not tell the buyer that GeM fee changes are their problem unless the contract says so.
• If you use a reseller or an implementation partner, decide who pays GeM before the bid, in writing.
• Keep the payment proof. Incident responses live on documents.

Objections from the sales floor

We will look expensive if we load the fee. You will look insolvent if you do not. Government buyers compare landed price. They do not award extra marks for a founder who forgot the marketplace exists.

The last policy cut fees, so we can ignore them. A cut is not a zero. A cap is not a waiver. Read the slab that applies to your order value.

We are MSE, we pay nothing on GeM. MSE benefits are about EMD, tender fees in many bids, purchase preference and payment discipline under MSME rules. Platform revenue is a different instrument. Claim what the revenue policy actually gives you.

A worked pricing model, without locking a percentage

Suppose the live policy, on the day you download it, has a zero slab under a threshold, a percentage slab in the middle, and a rupee cap at the top. Your year-one on-prem install sits in the middle. Your year-two support renewal sits under the threshold. Your optional three-year enterprise expansion sits at the cap. Those three years are three different platform-cost stories. A single blended percentage in the head will mis-price at least one of them.

Build the sheet with four columns: contractual value as the policy defines it, assumed platform charge under the dated PDF, net to the company, and a sensitivity if the slab moves by a revision. You do not need to predict the revision. You need to know whether a revision kills the bid. If it does, the bid/no-bid note should say so.

Tax treatment is a conversation with your accountant, not with this article. GST on the government invoice and the GeM charge are easy to mash in a founder spreadsheet. Mash them and you will either under-quote or fight a DDO about a line that was never a statutory levy on the buyer. Keep the government rate all-inclusive. Keep the platform charge as an internal cost of sales. Date both.

Partners complicate the sheet. If an implementation SI is the GeM seller and you are a named specialist, decide in the consortium paper who pays GeM. If both of you assume the other will pay, the incident for non-payment will still land on the registered seller id. That id is a company asset. Treat unpaid platform invoices as a board item, the way you would treat a defaulted TDS.

A one-week playbook before the next bid

• Day 1: download the current revenue policy and incident FAQ pages. Save PDFs with the date.
• Day 2: rebuild the rate model with an explicit GeM-charge line and a dated assumption.
• Day 3: ask accounts who owns the GeM invoice and what happens if CRAC slips.
• Day 4: decide the floor net of charges. Write it in the bid/no-bid note.
• Day 5: brief sales that all-inclusive means all-inclusive.
• Day 6–7: clear any unpaid GeM dues before you upload the next offer.

Internal file note for the bid folder

GeM charges for this bid are modelled on the revenue policy downloaded from gem.gov.in on [date], version [x]. Order value is taken as [tax-inclusive / exclusive] per that document. The quoted price to the buyer is all-inclusive. The platform charge is not shown as a statutory levy on the buyer. If the policy changes before award, we will re-run the floor test. Unpaid platform invoices will be treated as a bid blocker.

Prcept AI prices on-prem work as an all-inclusive government rate. We re-read GeM's revenue policy when it moves. Demand the same dated assumption from any seller who tells you the marketplace is free.