Cost Centre Allocation for AI Spend

The first invoice sat in suspense for four months because IT thought the plants would pay and the plants thought 'digital transformation' was a corporate head. The statutory auditor asked what benefit had accrued to whom. Nobody wanted the asset on their register because nobody wanted the AMC next year. The model was fine. The cost centre was imaginary.

This guide is for CIOs and CFOs who have to put agent spend on a living CPSE chart of accounts. It is not a costing standard. Your finance manual, your ERP cost objects, and DPE capital-versus-revenue habits decide the final booking. The field lesson is narrower: decide the split before the GRN, write a chargeback for hubs, and do not hide sovereignty hardware inside a software PO.

Auditors follow money. A purpose that cannot name a cost centre is a purpose nobody owns. Ownership is the actual control.

Not accounting advice. Ask your CFO's team how this company books intangible assets and plant IT.

Four buckets that should not mix

Platform: the shared runtime, the corporate licence, the packet schema, the evaluation set. Usually a corporate IT or digital cost centre. Plant use: the local appliance, the local champion's time, the plant-specific corpus work. AMS hours: the incumbent SI's change windows, which belong with the estate they touch. Sovereignty hardware: GPUs, air-gap kit, extra storage — capital or a clearly labelled revenue hire, not a line item called 'AI'.

Mixing the four in one PO is how you cannot retire a plant's box without a corporate argument, and cannot challenge a vendor invoice without a plant argument.

Name the payer. Suspense is a finding waiting for a year-end.

Bucket	Typical payer	Fail if
Shared platform	Corporate IT / digital	Each plant is invoiced a mystery share with no MoU
Plant purpose	The plant or SBU that gets the cycle-time benefit	Corporate pays forever for a local closing desk
AMS / estate hours	The budget that already pays the SI	Unpaid SI hours become a silent stall
Isolation hardware	Whoever required the isolation — often the data owner	A GPU with no asset tag and no AMC owner

Chargeback without a PhD

Simple keys survive: a flat share for hub use, a per-site appliance cost, a per-purpose licence if the vendor actually bills that way. Do not invent a token-based chargeback in year one. Token economics will become a second project and a second fight.

Write the MoU between corporate and the SBU. Verbal 'we will settle at year-end' is how year-end becomes a para about related-party-like internal disputes. Internal they may be. Ugly they still are.

Capital, revenue, and the AMC that nobody booked

A three-year subscription is usually revenue. A box you will hold for five years may be capital. A hybrid 'appliance included in SaaS' is how assets vanish. Ask finance before the tender, not after the GRN. The companion notes on AMC versus subscription in the tender cluster apply.

Book the AMC or the subscription renewal in the same cost centre that wanted the benefit. Orphans become surprise corporate hits, and CFOs have memories.

What CAG will ask

Who benefited, who paid, whether the split matched the note, and whether a GPU is on an asset register. If the board note said plant productivity and the invoices all sit in corporate hospitality-adjacent heads, you have a story problem. Align the story and the ledger.

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.

Digital is a corporate mission, so corporate pays.

Missions are speeches. Cost centres are controls. If a plant wants the cycle time, the plant should see a number. Corporate can still fund a share.

We will use one 'AI' internal order for everything.

Then you cannot kill a failed purpose without killing the platform. One internal order per purpose, plus a platform head. Two extra codes now save a year of argument.

Tokens are the fair way to charge.

Not in year one in a PSU. You do not yet know the noise. Use sites and purposes. Revisit tokens when you have a year of boring logs.

Hardware on the vendor's rental keeps our balance sheet clean.

It also keeps your isolation story on someone else's truck. Finance and CISO should both initial that trade. Do not hide it as a convenience.

A four-week allocation playbook

Do this with finance in the room. IT cannot invent cost objects alone.

1. Week 1: list platform, plant purposes, AMS hours, hardware. Map each to a living cost object or write the new one.
2. Week 2: draft hub and corporate-share MoUs. Kill the suspense plan.
3. Week 3: decide capital versus revenue with finance. Align the tender's commercial schedule to that decision.
4. Week 4: freeze PO rules — no cost centre, no PO. Brief plants so the first invoice is not a surprise.

How this shows up in the file

Subject: Cost objects for the agent programme — platform, purpose, AMS, hardware.

Platform spend books to (code). Each live purpose books to the benefiting SBU (list). AMS hours book to the estate that is touched. Isolation hardware is tagged and has an AMC owner. Hub sites charge (rule). POs without these objects will not be processed.

This note is not accounting advice. The finance manual prevails.

This article is informational field guidance for Indian public sector undertakings and their vendors, not legal, audit, labour, energy-regulatory, banking-regulatory or procurement advice. Confirm the live circular, DPE guideline, CVC instruction, sector regulator text, purchase manual and your counsel before you file it.

How this clears vigilance and the board

A P1 CIO/CTO in a PSU will meet CVC-shaped questions even when there is no special 'AI circular'. “Cost Centre Allocation for AI Spend” has to survive a technical committee, a cost centre, and a union conversation if jobs appear threatened.

If the GPU is corporate but the purpose is the refinery's closing, the refinery's cost centre needs a line. Suspense is not a strategy. CAG can read suspense. OT networks stay off-limits. Navratna autonomy speeds buying; it does not waive DPDP or data classification. IREPS is not GeM. RBI-shaped rules still localise payment data.

• Classify data before the POC.
• Keep agents off OT.
• Write the board memo with residual risk.
• Engage unions on retrieval vs replacement.

Close this loop before the next CAB

Put “Cost Centre Allocation for AI Spend” 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. “cost centre IT allocation PSU” is not a one-time workshop. It is a watch item. Date the last check. Unsigned watch items are souvenirs.

What must be true before you file this

If “Cost Centre Allocation for AI Spend” is only a heading, it will not survive a file inspection. A P1 CIO/CTO should be able to attach one artefact that proves “cost centre IT allocation PSU”: a log export, a clause, a scored row, a dated notice, or a refusal rule.

Write three dated sentences: what was decided, who owns it, and when it will be re-checked. Unsigned sentences are souvenirs. Dated sentences are controls.

• Name the owner of “cost centre IT allocation PSU” inside the institution.
• Attach one artefact a stranger can open next year.
• Revisit when the model, the notice, or the SI changes.
• Do not treat a vendor slide as evidence.

One more artefact before you close the file

Add a one-page owner map: who runs this after the vendor leaves, who can stop it, and where the logs live. If those three names are missing, the project is still a demo.

Date the page. File it next to the contract. That is the difference between a blog you read and a control you can audit.

What the next file must contain

“Cost Centre Allocation for AI Spend” earns a line in the noting only if a P1 CIO/CTO can attach proof of “cost centre IT allocation PSU.” 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 “cost centre IT allocation PSU.”
• 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.