Budget Heads for AI in a State Finance Bill

A State IT department stuffed GPU purchase, a cloud invoice, two SI work orders, a font licence, and a proposed language-desk hire into one token grant titled Emerging Technologies. Finance asked which object head. The file said 13. Office Expenses. The hire died. The AMC was forgotten at RE. The cloud invoice landed as a surprise in January. The GPUs arrived. The service did not.

This guide is for CIOs who must talk to finance controllers before the next budget cycle. It is not a chart of accounts for every State. States number demands differently. Treasuries argue. You will take this skeleton to your finance department and let them put the real codes on it.

AI does not need a glamorous new demand to be real. It needs the unglamorous heads that already pay for people, power, professional services, machinery, and maintenance. If those lines are empty, the model is a statue.

Not legal or budget advice. The Appropriation Act, your State financial rules, and the latest Government of India / CAG classification still win. Hedge live codes.

Stop putting a factory under stationery

A citizen agent is a small factory. It has labour, energy, plant, contractors, and a helpdesk. Stationery-like heads cannot hold a factory without starving something. When the year gets tight, the silent lines die first: AMC, markers, mystery-call budget, font renewals.

Write the factory as a set of lines that a treasury clerk already knows how to pay. Then, if politics wants a single 'AI mission' umbrella, keep the umbrella as a programme label, not as the only operable head.

A skeleton you can take to finance

We use purpose names, not your State's numbers. Finance will map them. If they refuse a mapping, that is information: you do not yet have a way to pay that part of the factory.

Purpose lines, not official codes. Confirm against your State list and any latest GoI classification.

Purpose	Typical home (talk to finance)	Dies if you hide it under
Named posts / outsourced desk / markers	Salaries or professional / office expenses as they direct	A one-time machine grant
GPU / server plant	Machinery and equipment / capital	Office expenses
Cloud / IndiaAI hours (if allowed)	Professional services or IT opex as they direct	Capital (you will not be able to pay the invoice)
Power / cooling share / diesel	Electricity / SDC chargeback	The GPU capital line
SI / integration work orders	Professional services / OC	AMC, or vice versa
AMC, support, font licences, eval refresh	Maintenance / OE — a recurring line	Year-one capital
Training of officers	Training head	Travel, where it will be cut

New service versus reappropriation

A new citizen channel is a new service in spirit even if finance can squeeze year one from an existing IT demand. Write it as a programme with outputs: languages staffed, tickets completed, packets exportable. Finance bills are political documents. A programme with outputs is easier to defend than a SKU.

Reappropriation from 'computer consumables' to a GPU is how you get a card and no operators. If you must start mid-year, still open the operate lines, even if they are small. A token operate line is a hook for RE. A missing line is a wall.

Centrally sponsored or IndiaAI-linked money, if any, will arrive with conditions. Do not mix it into salary without a rule. Do not assume it can pay the desk. Read the sanction.

What to show the House, and what to keep in the working note

The speech can say a citizen agent in four languages. The working note must say the desk roster, the power, and the AMC. MLAs will ask why a kiosk is dark. They will not ask about KV cache. Give the minister both papers.

Do not print a subsidy percentage in the budget speech. Print 'subject to IndiaAI / MeitY approval, see working note'. Speeches outlive RFEs.

Two budgets

Objections you will hear — and what to do with them

These are the lines that stall the file. Answer them in the room, then put the answer in the note. A spoken answer without paper will be forgotten by the next officer.

Finance will not open new heads for a pilot.

Then do not call it a pilot while staffing a public desk. Use existing operate heads with a programme label, or keep the pilot off the citizen queue.

We will hire on contract and pay from OC.

If finance allows it, write the year-two continuation. Contract desks that die every March are not fallback. They are an annual outage.

Power is already paid by the SDC.

Then get a chargeback line or a written absorption. Unwritten absorption dies when the SDC is asked to add two more tenants.

The Centre will fund the GPUs.

Even if a central sanction exists, read what it will not fund. Desks and AMC are the usual orphans.

A budget-cycle playbook

Start when the controller asks for proposals, not when the speech is being drafted.

1. Week 1: list the factory lines. Sit finance. Write their codes beside our purpose names. Hedge.
2. Week 2: separate capital from recurring. Open or request the recurring hooks even if small.
3. Week 3: attach the TCO skeleton and the language cost scopes. No frozen subsidy percentages.
4. Week 4: give the minister a speech paragraph and a working note. They are different documents.

File note you can paste

Subject: Budget mapping for the citizen-agent factory — working note.

Purposes and proposed heads are in the attached table as advised by [finance contact] on [date]. Live codes may differ; this is not a treasury instruction. Recurring operate lines are requested even where year-one amounts are token. IndiaAI or central sums, if any, will not be assumed to pay desks or AMC unless the sanction says so. This note is not budget advice.

Supplementary, surrender, and the March panic

If hours or AMC will land in Q4, write the supplementary story in Q2. A March rush to dump leftover capital into a third GPU is how idle clusters are born. Surrender unused operate money if the desk was never hired; do not convert it into a card to 'use the grant'.

If a central sanction arrives earmarked for compute, park it on the compute purpose and still fight for the State operate line. Mixing them to look fully funded is how the desk disappears in the next RE.

What we will not draft

Prcept AI will not invent a demand number for your State. We will sit with your controller and keep people and AMC on the page. We will refuse a proposal that only buys silicon.

If a competitor offers a single-line 'AI budget', ask them which head will pay the night desk in March.

This article is informational field guidance for Indian public institutions, not legal, language-policy, procurement, finance or engineering advice. Confirm against the live Gazette, Official Languages Act and Rules, your State's official-language law, MeitY / IndiaAI notices, GFR, GeM terms, DPDP text, departmental manuals and your counsel before you file it.

How to put this in the finance note

A P1 CIO/CTO searching “government AI budget allocation” needs a number a CFO can defend, not a GPU brand. “Budget Heads for AI in a State Finance Bill” belongs in a cost model with people, power, idle time, AMC and the cost of a failed pilot.

If the entire agent sits under 'office expenses — computer', you will starve the desk, the power, and the AMC. Map AI onto heads a State finance bill already has. Do not invent a mystery demand called Artificial Intelligence. IndiaAI subsidy, if you use it, is a live notice — not a permanent discount. On-prem TCO includes ops headcount. Do not invent Rs/hour. Cite the source of every rupee.

• Separate capex, opex, and one-time cleanup.
• Show utilisation, not just peak GPUs.
• Price the human fallback, not only inference.
• Date every tariff and subsidy assumption.

Close this loop before the next CAB

Put “Budget Heads for AI in a State Finance Bill” 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 P1 CIO/CTO, not “the vendor.”

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

What the next file must contain

“Budget Heads for AI in a State Finance Bill” earns a line in the noting only if a P1 CIO/CTO can attach proof of “government AI budget allocation.” A heading is not proof. A vendor slide is not proof. A workshop photograph is not proof.

Write three dated sentences: what was decided, who owns it after the next posting order, and when it will be re-checked. If you cannot write the three sentences, you are not ready to buy, to sell, or to go live.

Leave unsourced percentages out of the note. DPDP is not a blanket localisation statute. The November 2025 AI governance text is guidance, not an Act. CERT-In’s 28 April 2022 directions still set specified incident and log clocks. A PAC, when lawful, lives in GFR Rule 166.

• Name the designation that owns “government AI budget allocation.”
• Attach one artefact a stranger can open next year.
• Record the instrument you are actually using.
• Revisit when the model, the SI, the notice or the posting changes.