GFR Rule 161 and Proprietary Article Certificates

A section officer in a line ministry printed a one-page note last monsoon. The subject line said Proprietary Article Certificate under GFR Rule 161. The annexure was a vendor letter. Finance asked, quietly, which rule they meant. The file stalled for eleven days while three officers argued about a number.

They were arguing about the wrong number. In the General Financial Rules, 2017, Rule 161 is Advertised Tender Enquiry. The Proprietary Article Certificate lives in the note to Rule 166, Single Tender Enquiry. The title of this article repeats a search phrase that has misled more than one committee. The rest of the article corrects it.

This is not legal advice. GFR is a Ministry of Finance instrument for the Central Government and the bodies that adopt it. States have their own codes. Always read the live compilation on doe.gov.in and the bid you are actually running. What follows is a working map for procurement officers, DDOs and PAC committees who buy agentic software for Indian institutions.

Why Rule 161 keeps getting blamed for PAC

Rule numbers travel faster than rule text. Older GFR editions put advertised tender at a different value. Training decks compress four tender types onto one slide. GeM PAC buying sits next to Rule 149 in buyer circulars. Somewhere in that pile, 161 became a nickname for any exception to open competition. It is a bad nickname.

Open the current compilation. Rule 161 tells you when invitation to tenders by advertisement is the default, and that the enquiry should appear on GeM and on the Central Public Procurement Portal. It is a competition rule. It is the opposite of a single-source certificate.

Rule 166 tells you when procurement from a single source may be resorted to. The note under that rule sets out the PAC form the Ministry or Department must provide before buying from a single source under 166(i) or 166(iii). If your file is about a proprietary article, you are in 166. Write 166.

GFR 2017 tender types that get mixed in AI files

Rule	What it actually is	What a sloppy note pretends it is	What the file should say
149	GeM as the channel for common-use goods and services available on GeM, with price-reasonableness and no-splitting duties	A blanket PAC permission	Name the GeM route. If you leave GeM, write the reason.
161	Advertised Tender Enquiry for higher-value goods, published on GeM and CPPP	The PAC rule	Use it when you are advertising. Do not cite it for single source.
162	Limited Tender Enquiry to known sources	A quiet PAC	List why limited rather than advertised. Name the sources.
166	Single Tender Enquiry, with a PAC form for 166(i) and 166(iii)	An emergency stamp anyone can sign	Quote the limb. Attach the PAC form. Record finance concurrence.

What Rule 166 actually allows

Single source is not a mood. GFR lists three circumstances. They are narrower than a product manager's uniqueness slide.

1. 166(i): it is in the knowledge of the user department that only a particular firm is the manufacturer of the required goods.
2. 166(ii): in a case of emergency the required goods must be purchased from a particular source, with reasons recorded and competent-authority approval.
3. 166(iii): for standardisation of machinery or spare parts so they remain compatible with existing equipment, on the advice of a competent technical expert and with competent-authority approval, the item is bought only from a selected firm.

The PAC form in the note is required before procuring from a single source under 166(i) and 166(iii). Emergency under 166(ii) is a different limb. It still needs recorded reasons and approval. It is not a licence to skip the file because the secretary saw a demo on Tuesday.

The form itself is spare. The indented goods are manufactured by a named firm. No other make or model is acceptable, for reasons the department writes. Finance wing concurrence has been obtained. Competent-authority approval has been obtained. That is the whole certificate. Vendors love to pad it with adjectives. Adjectives are not reasons.

What a PAC is not

• It is not a vendor entitlement. The buyer issues it.
• It is not a way to avoid GeM when the item is available on GeM. Rule 149 still frames common-use buying.
• It is not a finding that the quoted rate is reasonable. Rate reasonableness is a separate duty.
• It is not a finding that the architecture is sovereign, air-gapped, or DPDP-safe.
• It is not a standing order for three years of renewals unless the file says so and the facts still hold.

How a PAC committee should sit

AI software is a bad fit for 166(i)

Rule 166(i) speaks of a manufacturer of required goods. Software licensing, subscription, and on-prem installation sit awkwardly in that sentence. Departments still use the limb, because the GFR chapter on goods is the nearest hook and because GeM PAC buying exists as a buyer workflow. Honesty requires you to say what you are certifying.

If the required article is a specific named product that only one firm can supply, and no other make or model will do, write why. Interoperability with a locked protocol, a statutory certification that only one product holds, or a court-ordered system of record can be reasons. A nicer demo, a relationship with a former secretary, or a claim that the model is Indian are not reasons.

Agentic platforms are, as a class, substitutable at the capability layer. Several Indian firms will run retrieval, tool-calling and workflow agents inside a state data centre. What is not substitutable is a particular integration already paid for, a particular certification, or a particular dataset the institution already owns. Certify the constraint. Do not certify the slogan.

PAC buying on GeM does not erase competition duty

GeM lets a buyer mark PAC and limit a bid to a brand or OEM in defined cases. That workflow is not a private treaty. Buyer circulars and the GeM terms have long said that PAC procurements need extra diligence on price reasonableness, read with Rule 149. Bidding above a threshold can still apply. Confirm the live GeM buyer manual on gem.gov.in before you brief the committee. Screens change. The duty to justify does not.

A PAC bid that one seller can see is still a public act. The specification, the PAC note, and the rate reasonableness paragraph will be on the file when someone asks why the other three Indian platforms were locked out. Write those pages as if they will be read.

Objections you will hear in the room

The vendor says only we can do air-gapped Hindi agents. Answer: name two other DPIIT-recognised firms that install on-prem. If you cannot name them, you have not market-researched. If you can, 166(i) is already in trouble.

The user department says we already trained officers on this UI. Answer: training is not standardisation of machinery under 166(iii). Retraining cost can go into a total-cost note. It does not make the article proprietary.

Finance says just cite 161, everyone does. Answer: everyone doing it is how files fail. Cite 166 or do not claim PAC.

Leadership says the minister wants this vendor. Answer: a ministerial preference is not a GFR limb. If the facts support 166, write the facts. If they do not, run 161 properly and let the preferred vendor win on a scored bid.

Rule 149 is still in the room

Even a perfectly cited Rule 166 PAC does not delete Rule 149. If the article is a common-use good or service available on GeM, the default channel is GeM. PAC buying on GeM is a buyer workflow inside that channel. Leaving GeM because a vendor prefers a private treaty is a second decision, with its own sentence on the file.

Write the two decisions on two lines. Line one: are we on single source, and under which limb of 166. Line two: are we on GeM, and if not, why the article is not available there. Committees that merge the lines produce notes that say PAC so we went offline. That sentence is how a later auditor begins.

Price reasonableness is the third line. Competition is the usual proof. PAC removes competition, so the proof must become a method. Last purchase price, a failed alternative quote, a modular rate card, an independent estimate. Pick one and name it. Do not let the PAC form do that job. The PAC form asks why no other make is acceptable. It does not ask whether the rate is sane.

A PAC committee checklist that fits on one folio

1. Is the citation Rule 166, not Rule 161.
2. Which limb: (i) sole manufacturer, (ii) emergency, (iii) standardisation or compatibility.
3. If (i) or (iii), is the GFR PAC form filled in the GFR words, not a vendor brochure.
4. If (ii), are reasons and competent-authority approval on the file, and is the duration short.
5. Has someone who is not the indentor listed substitutes from GeM and CPPP.
6. Do the reasons exclude those substitutes with nouns, not adjectives.
7. Is the article limited, with a review or sunset date.
8. Is finance concurrence on the same file as the certificate.
9. Is a price-reasonableness paragraph attached as a separate page.
10. Is the GeM or off-GeM choice written as its own sentence.

If any of the first four items fail, do not meet. Send the paper back. A committee that edits a wrong citation in the room will still sign a wrong citation if the clock is loud. Editing belongs to the indentor. Signing belongs to people who have a clean page.

Keep the market scan opposite the PAC for at least the life of the contract plus the audit cycle you actually face. When a new officer inherits the file, the scan is how they learn that the committee was not captured. Without it, the next renewal looks like a habit.

A four-week playbook before anyone signs a PAC

• Week 1: open the live GFR compilation on doe.gov.in. Print Rule 161 and Rule 166 onto the first folio. Write one sentence: we are not using 161 for this certificate.
• Week 2: market scan. List at least three capable suppliers, including GeM category search and CPPP recent awards. If three exist, stop the PAC path unless 166(iii) compatibility is real.
• Week 3: draft the PAC form in the GFR language. Reasons must exclude other makes. Attach the technical expert note for 166(iii). Attach finance concurrence.
• Week 4: write the price-reasonableness paragraph as a separate page. Then choose the channel: GeM PAC bid, or a documented departure from GeM if the item is not available there.

File note you can paste

Subject: Correction of rule citation and test for Single Tender Enquiry.

Reference is invited to the draft PAC placed on the file citing GFR Rule 161. Rule 161 of GFR 2017 governs Advertised Tender Enquiry. Proprietary Article Certificate is provided for in the note to Rule 166 (Single Tender Enquiry), applicable to 166(i) and 166(iii). The draft is returned for recasting.

Indentors may confirm, with evidence: (a) that only the named firm manufactures the required article, or (b) that standardisation or compatibility with existing equipment so requires, on the written advice of a competent technical expert. Emergency under 166(ii), if claimed, needs recorded reasons and competent-authority approval and is not a PAC under the note to 166(i)/(iii).

A market scan of GeM and CPPP is placed opposite. Price reasonableness will be recorded separately before any contract is placed. This note is an internal aid. It is not legal advice.

What we will not ask you to do

Prcept AI sells on-prem and air-gapped agents to Indian institutions. We are DPIIT recognised. We do not train on customer data. None of that is a PAC. If a committee can name substitutes, they should compete us. If they cannot, they should write the real constraint — usually residency, air-gap, or a locked integration — and still test the rate. A vendor who hands you a ready-made Rule 161 PAC is handing you a citation error. Send it back.

Do not use PAC to evade advertised tender or GeM competition. The certificate is a buyer document with a narrow GFR basis. Wrong rule, wrong limb, or a vendor-authored reason is how a software buy becomes a vigilance file.