Delegation of Financial Powers vs AI Agents

A deputy secretary in a central ministry asked whether the new procurement agent could 'place orders up to the GeM limit automatically, since the model is conservative'. The DDO asked a smaller question: under which serial of the ministry's delegation does the model sit. There was no serial. There was a demo. The DDO refused to operate a system that could create a payable she would have to own.

The Delegation of Financial Powers Rules, 2024, framed by the Ministry of Finance, Department of Expenditure, replaced the 1978 Rules and came into force on 1 April 2024. They distribute financial powers to posts, with annexures and later amendments — including a revised Annexure-I below Rule 8 issued in 2026. They do not distribute powers to software. If your agent can create a sanction, a bill, a refund or a purchase order, it is exercising a power it does not have, unless a competent human exercises that power in the system of record.

Explainer for DPOs, DDOs and programme owners. 16 August 2026. Not legal advice. Confirm the live DoE compilation and, if you are not Central, your state code.

The rule in one sentence

An agent cannot spend, or commit the government to spend, beyond — or instead of — the delegation held by the officer who is asked to own the act. Speed is not a delegation. Accuracy is not a delegation. A PAC is not a delegation. A model card is not a delegation.

GFR 2017 still governs how you buy. DFPR 2024 governs who may incur. GeM governs a channel. The agent is none of those instruments. It is a clerk who types fast. Clerks do not get a higher limit because they type faster.

Map the tools to the serials

If a tool can land on a serial, a human who holds that serial must click.

Agent temptation	Financial object	Who must act
Auto-create a GeM cart and place	Purchase	Officer with the relevant purchase delegation
Draft a sanction and submit	Sanction	Competent authority on the serial
Recommend a refund and trigger it	Refund / payment	DDO / PAO path as your rules require
Raise a contingent bill	Contingent expenditure	DDO, not the model
Book travel above the entitled class	Travel	The post that may relax, if anyone may
Announce that money is approved	Commitment / public assertion	Treat as spending-adjacent; human only

Write this map as an annex to the AI register for every money-class row. Internal audit should pick a sample and ask the DDO to show the human click. If the click is missing, the row is a finding, not a feature.

What a DDO can safely allow

Drafting a bill from structured fields the officer already entered. Checking arithmetic. Retrieving the last purchase price. Listing missing vouchers. Refusing to submit. Those are clerk tasks. The DDO remains the DDO.

What a DDO should not allow: stored credentials for the bill portal, unattended submission, a service account that looks like her, or a rule that 'below fifty thousand the bot may go'. Fifty thousand is still a serial. The serial names a post.

Two DDOs

Objections

A vendor says other ministries auto-approve below a threshold. Answer: ask for the serial and the CAG-surviving sample. Thresholds still name humans.

A programme officer says DFPR is Central-only so we are free. Answer: you have a state code. Quote it. Freedom is not the residual.

IT says the human click is friction. Answer: friction is the control. Remove it and you have spent without a post.

Leadership wants the agent named as a drawing officer. Answer: no.

A four-week playbook

• Week 1: put the live DFPR 2024 compilation (or state code) on the file. List serials that money-class workflows could touch.
• Week 2: strip submit/place/pay tools from every agent account. Prove it.
• Week 3: write the tool-to-serial annex. DDO initials it.
• Week 4: sample five drafts. Confirm a human click in the system of record. Brief the secretary with the one sentence.

File note you can paste

Subject: Financial powers and software agents.

DFPR 2024 (in force 1 April 2024, replacing DFPR 1978), or the state delegation that applies to this office, vests financial powers in posts. A software agent is not a post and shall not sanction, place, pay, refund or otherwise commit public money. It may draft. A competent officer shall act in the system of record. Stored credentials that impersonate a DDO or competent authority are prohibited.

The CIO and DDO will maintain a tool-to-serial map for every money-class row. This note is not legal advice. The live DoE or state compilation governs.

How to brief finance in one page

Line one: the agent drafts; it cannot submit, place or pay. Line two: here is the tool-to-serial map initialled by the DDO. Line three: here is the test that a payment tool is refused. Line four: here is the sample of five human clicks in the system of record. Line five: no stored DDO credentials. If finance wants a sixth line, they want a serial for software. There is not one. Stop.

Autonomous finance as a slide is a request to rewrite DFPR without the Ministry of Finance. Treat it that way in the noting. You may still automate arithmetic, last-purchase retrieval and missing-voucher lists. You may not automate the will to spend. Those two sentences keep a DDO employed and a CAG para unwritten.

State corporations and societies sometimes live under a board resolution rather than DFPR 2024. Find the instrument. Quote it. The principle does not change: the resolution names posts or committees, not models. If someone proposes to name the model, that is a rewrite of the instrument, with all the formality that implies — not a config flag.

GeM placement is still a financial act. A cart that becomes an order has spent, or has committed to spend. The agent may fill fields. The officer who holds the purchase serial places. If GeM offers APIs that place without a person, do not give the agent that scope. APIs do not create posts.

• Rotate any secret that ever looked like a DDO.
• Sample night-time orders monthly. Humans sleep. Service accounts do not.
• When DFPR annexures change — they do — re-read the map the same week.

Informational explainer. Always open the current DFPR compilation on doe.gov.in or your state finance department's page before you cite a serial.

How this survives CAG, RTI or the Board

“Delegation of Financial Powers vs AI Agents” is not a workshop slide. A P6 Compliance/DPO will have to reconstruct a decision after the officer who clicked approve has been transferred. Write the artefact that lets a stranger replay the case: the log fields, the approval, the override, the register row.

The Delegation of Financial Powers Rules, 2024 did not create a new post called the model. If a human may not spend it, the agent may not spend it. If a human may spend only to a limit, the agent does not get a higher limit by being fast. India AI Governance Guidelines (November 2025) are guidelines, not a statute. DPDP still allocates fiduciary duty. Delegation of Financial Powers still allocates who may spend. Do not hide those instruments behind the word governance.

If you cannot show who acted, on which purpose, with which data class, and who could have refused, you do not have accountability. You have a chatbot with a charter PDF.

• Name the owner of “delegation of powers AI” inside the department, not the vendor.
• Keep CERT-In-relevant logs in India for the required period.
• Store overrides with a reason an auditor can read.
• Put the workflow on the AI register before it touches a citizen.

Close this loop before the next CAB

Put “Delegation of Financial Powers vs AI Agents” 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 P6 Compliance/DPO, not “the vendor.”

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