Skip to main content
SearchEnquiry basket
OfficesIndia · UAE

Government procurement

How government departments and PSUs procure genuine software in India

The procurement route determines nearly everything about the purchase — what documentation is needed, how price is established, and what the department holds afterwards as proof of licence.

· 9 min read

Software procurement in the public sector fails in predictable ways, and almost none of them are about software. They are about the procurement route being chosen after the requirement has been written, rather than before.

This describes the routes available, what each needs, and the documentation a department should hold at the end.

The routes

Government e-Marketplace (GeM). The default channel for central and state government purchases. Sellers register, list against product categories, and buyers purchase either from a catalogue or through a bid. For standard software licences — an office suite, a design product, an operating system — GeM is usually the straightforward route, because the product is a defined item rather than a scope of work.

Direct purchase. Below a threshold set by the General Financial Rules, a department may purchase without a competitive process. Above it, a competitive route applies, and above a further threshold a formal bid or reverse auction is required. The thresholds are set by rule and have been amended, so confirm the current figures against the GFR and your own department's delegation of financial powers rather than against any article — including this one.

Tender. For larger or composite requirements, particularly where licences are bundled with implementation, migration or support. The specification does the work here: a tender written around one publisher's product names will either be challenged or will produce a single compliant bid.

Rate contract and existing framework agreements. Where a framework already covers the product, using it is usually faster and defensible.

What goes wrong, and when

The specification names a product instead of a requirement. "Supply Microsoft Office" invites a challenge. "Supply an office productivity suite providing the following, interoperable with existing .docx and .xlsx archives" survives one. Where a specific product genuinely is required — because of file-format compatibility with an existing archive, or certification of an existing process — the justification belongs in the file at the time, not reconstructed afterwards.

The licence model is not specified. A bid for "100 licences of a design product" will attract quotes for perpetual licences, one-year subscriptions and three-year subscriptions, which are not comparable. State the term, the licensing basis (named user, device, core) and whether support is included.

Named users are procured as devices. Most current design and productivity software is licensed to a person. A department buying by workstation count will either over-buy or find the licences unusable as deployed.

CALs are omitted from server purchases. A server bid priced on core licences alone is not a working server. See Windows Server 2025 licensing explained.

Renewal is nobody's line item. Subscriptions lapse. A perpetual purchase has no renewal; a subscription has one every year, and if it is not budgeted the software stops. This is the single most common cause of an avoidable procurement emergency.

What the department should hold afterwards

Proof of licence is not a product key. The file should contain:

  • The invoice, raised to the department's own name
  • The purchase order and the acceptance record
  • For volume licences, the agreement or enrolment number and access to the licensing portal
  • The licence term and the renewal date, recorded somewhere a person will look before it passes
  • The assignment record — which licences are deployed where, or to whom

An audit, a CAG query or a successor officer taking over will ask for these. Assembling them two years later from a publisher's records is possible and unpleasant.

Specifying so that competition is real

The practical test of a good software specification is whether two different suppliers could both comply and be compared. That means:

  • Functional requirements rather than product names, with a recorded justification where a product name is unavoidable
  • An explicit licence term and basis, so bids are comparable
  • Quantities by licence type, not by headcount
  • Support and deployment scoped separately from licences, or explicitly included
  • Compliance evidence requirements stated up front

Common questions

Can a department buy software directly from a publisher abroad? It can, and there are then questions about invoicing, GST and whether a local entity is required for the purchase to be processed. Settle them before the bid rather than at payment.

Does GeM guarantee the licence is genuine? GeM is a procurement channel, not a provenance check. The documentation above is what establishes genuineness — see how to buy genuine Microsoft licences in India.

What about academic licensing for government institutions? Academic programmes have eligibility criteria that an institution either meets or does not. A government department is not automatically eligible because it is public.

Can subscriptions be bought on a multi-year basis? Frequently yes, and it is often cheaper. Whether a department may commit across financial years is a question for its own financial rules.

Where to go next

The public-sector page covers how we work with departments and PSUs: government and PSU. For the GeM channel specifically, see GeM software supply. If you are writing a specification now, send us the draft — the licence basis and quantity lines are where we can be most useful, and they are the hardest to fix after bids are open.

More articles