# Who owns AI spend, finance or IT?

Published 2026-10-05 · Brian Diamond

Track: finops

Segment: controller

**Finance owns the number, IT owns the platform, and the department whose agents did the work owns the budget.** AI spend gets mislabeled as an IT cost because the contract sits with IT and the invoice lands in the IT account. But an agent that researches leads is a Sales expense, and an agent that drafts contracts is a Legal expense. The ownership model that works splits three roles cleanly.

## The three roles

| Role | Owner | Responsible for |
| --- | --- | --- |
| Platform | IT or the AI platform team | Provider contracts, gateways, security, rate negotiation, the central clearing account |
| Budget and consumption | The business unit running the agent | Approving agents, setting their budgets, answering for variance on their P&L |
| Record and control | Finance (controller) | Accrual, allocation, chargeback, the GL entries, the audit trail, the policy |

Where this breaks is when one role tries to do another's job: IT allocating cost by headcount because it has no attribution data, or finance refusing to book spend until an invoice arrives, or a business unit running agents against a budget nobody set.

## Why the IT-owns-it default fails

Cloud infrastructure was reasonably an IT cost because the consumers were IT systems. Agents consume on behalf of departments. If IT absorbs the spend:

- Department owners have no incentive to control usage they never see.
- The AI budget becomes a single line that the CFO can only cut or grow, not steer.
- IT gets blamed for a cost it did not generate.

If finance tries to own it alone, it has the authority but not the data: it cannot see which agent did what for whom.

## What finance should insist on

1. **Attribution at the source.** Every usage record carries agent identity and a cost object. This is a platform requirement finance imposes on IT.
2. **A budget per agent or per cost center,** approved by the business owner, with alerts routed to that owner, not to IT.
3. **A monthly statement per owner,** followed by chargeback entries once attribution is trusted.
4. **One policy document** covering accounts, accrual threshold, allocation rules for shared agents, and the treatment of agent-initiated purchases.

## A simple RACI

| Activity | Finance | IT / Platform | Business unit |
| --- | --- | --- | --- |
| Negotiate provider contracts | C | R/A | I |
| Capture usage with attribution | A | R | C |
| Set agent budgets | C | I | R/A |
| Approve new agents | I | C | R/A |
| Accrue and allocate at close | R/A | C | I |
| Issue statements and chargeback | R/A | I | C |
| Respond to variance | C | I | R/A |
| Maintain the audit trail | R/A | R | I |

## Related

[How do I do chargeback for AI usage?](https://www.onaro.io/blog/how-to-do-chargeback-for-ai-usage) · [How do I account for AI agent spend in the general ledger?](https://www.onaro.io/blog/how-to-account-for-ai-agent-spend-in-the-general-ledger)

Onaro Meridian is [FinOps for agentic AI](https://www.onaro.io/finops-for-agentic-ai): the system of record that attributes, controls and books what AI agents spend.

Canonical: https://www.onaro.io/blog/who-owns-ai-spend-finance-or-it