Showback or chargeback: how to allocate AI costs by team.
Showback reports each team's AI spend back to it. Chargeback bills it to the team's budget. When to use each, and the allocation rules that hold up.
- Topic
- AI cost
- Product
- Novie Control
- Format
- Guide
- Reading time
- 4 min
- Published
- 2 October 2026
- Updated
- 21 October 2026
Showback reports each team's AI spend back to it without moving money. Chargeback bills that spend to the team's own budget. Start with showback once every model call is attributed to a team and a project. Move a team to chargeback when its spend is material, the attribution is trusted, and the team controls the choices that drive its cost, such as which model it uses and how often its agents run.
AI cost allocation: showback and chargeback, defined.
Both are ways of making a shared bill visible to the people who caused it. Showback is a report: here is what your team spent on AI this month, against the budget you were given. Chargeback is an accounting entry: that amount is moved from a central budget to yours.
The words come from cloud cost management, where they have been used for a decade. They carry over to AI with one difference that matters: the cost of a model call depends on choices a team may not control, and on prices that change more often than cloud prices ever did.
TakeawayShowback is a report of what a team spent; chargeback moves that amount into the team's own budget.
Why AI makes the choice harder than cloud did.
- Spend arrives through shared credentials, so the first job is attribution, before any allocation is fair.
- Cost depends on the model chosen, the length of the prompt and how often an agent loops. A team charged for a model it did not choose will argue the bill, and it will be right.
- AI arrives inside products you already license, as features switched on by the vendor. Those costs sit in software budgets and never reach the AI line.
- Model prices move during the year. A charge calculated at January prices and settled in June needs a rule for which price applies.
The cost of getting it wrong is visible across the Tasman. In research for Elastic among more than 500 senior decision-makers at Australian organisations, published in June 2026, one in three had exceeded their AI budget in the last financial year. Thirty-two percent had paused, cancelled or wound back deployments because the output could not justify the cost, and 8 percent were tracking whether AI delivered revenue or savings.
The FinOps Foundation's guidance on AI token costs, published in June 2026, sets the order: showback to application and team owners first, chargeback later, where organisational maturity supports it.
The common mistake is to switch on chargeback because spend has grown, before anyone trusts the numbers. The first month of disputed bills costs more goodwill than the spend it was meant to curb.
TakeawayAI spend arrives through shared credentials, depends on choices a team may not control and on prices that move, so attribution has to be trusted before any bill is fair.
When to use which.
- Start with showback for every team, as soon as calls are attributed. It changes behaviour on its own when it arrives during the month, while there is still time to act on it.
- Move a team to chargeback when its AI spend is large enough to matter in its own budget, its attribution has matched the invoice for two or three months, and it chooses its own models and agents.
- Keep costs central where no team controls them: the platform, shared evaluation, experiments under a fixed cap, and agents that serve the whole company.
TakeawayShowback for every team as soon as calls are attributed; chargeback only when a team's spend is material, matched to the invoice for months and driven by its own choices.
Allocation rules that hold up.
- Allocate by the call, using the team, project and workflow recorded when the call ran. Headcount and revenue splits are guesses that teams learn to ignore.
- Charge the team that caused the call, which is often different from the team that owns the key.
- Split shared platform cost on measured usage, and say in advance what the measure is.
- Give experiments their own central line with a cap, so a team does not avoid a useful test because it would land on its budget.
- Fix the price rule: calls are costed at the price in force when they ran.
- Publish the rules before the first report. A rule written after a dispute looks like a ruling.
TakeawayAllocate by the call, charge the team that caused it, split shared cost on measured usage, cost at the price of the day, and publish the rules before the first report.
What actually changes behaviour.
Allocation tells a team what it spent. It does not stop the spend. Teams change what they do when the number arrives while the month is open, and when the budget they are measured against holds at a cap they can see coming. Chargeback without a cap moves an overrun from one budget to another. Showback with a cap, approved by a named person, usually prevents it.
TakeawayAllocation reports the spend; a cap the team can see coming, approved by a named person, is what prevents the overrun.
How Novie Control does it.
Novie ControlAvailable now
Full cost visibility.
See spend by team, workload and model, before the invoice arrives.
$5,440
spent this cycle.
Example figure.