Insights
Who owns AI spend, and who books it to the general ledger
Finance owns the amount and the journal entry, IT owns the systems that create the spend, and the business unit 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. An agent that researches leads is a Sales expense, and an agent that drafts contracts is a Legal expense.
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
- Attribution at the source. Every usage record carries agent identity and a cost object. This is a platform requirement finance imposes on IT.
- A budget per agent or per cost center, approved by the business owner, with alerts routed to that owner, not to IT.
- A monthly statement per owner, followed by chargeback entries once attribution is trusted.
- 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 |
FAQ
Who owns the AI spend number? Finance owns the amount and the journal entry that books it.
Who owns the systems that create the spend? IT owns the platform, the provider contracts, and the controls on those systems.
Who owns the budget? The business unit whose agents did the work owns the budget and the variance.
Why does AI spend look like an IT cost? The contract and the invoice usually sit with IT. The work the agent did still belongs to the department that asked for it.
Related
How to do chargeback for AI usage and book it to the general ledger · How to account for AI agent spend in the general ledger
Not sure which of your AI costs are being booked? Run the free Agent Spend Assessment.
Onaro Meridian is FinOps for agentic AI: the system of record that attributes, controls and books what AI agents spend.

Brian Diamond
Brian Diamond is a fractional Chief AI Officer and founder of Onaro. He has spent 30 years running infrastructure operations and founded LANStatus, a Connecticut managed services provider and Microsoft partner, in 2001. He holds a Chief AI Officer certification and writes the CAIO Brief on AI leadership for finance and operations.