Showback and chargeback are the two standard ways to allocate shared IT costs to the teams that generate them, and the difference comes down to one thing: whether money moves. Showback reports each team's share of the cost without billing anyone. Chargeback actually transfers that share onto each team's budget. Same data, same allocation math, very different organizational contract.
This guide covers both models in full: what each one is, a side-by-side comparison, a worked example with real numbers, a decision framework for choosing between them, where the practice came from, and the questions teams ask most often.
The difference in one line
Showback shows a team what it consumes without moving money. Chargeback moves the money onto the team's budget. Showback informs; chargeback holds accountable.
What is showback?
Showback (sometimes written as IT showback) is the practice of measuring each team's consumption of shared IT resources and reporting the cost of that consumption back to them on a regular cadence, as information, not as an invoice. The central budget keeps paying the vendors. Teams receive a statement: here is what you used, here is what it cost, here is the trend.
Because nothing is billed, showback is low-stakes by design. Teams can review their consumption, question the methodology, and correct mapping errors while the only consequence is a conversation. That safety is not a weakness; it is the mechanism. Showback is how allocation data earns trust, and visibility alone often changes behavior, because a team that sees its own idle seats and heavy usage tends to clean them up without being told. We wrote a full implementation guide in what IT showback is and how to implement it.
What is chargeback?
Chargeback takes the same attribution and makes it financially real: each team's share of the cost is transferred to that team's budget, usually as an internal journal entry each period. The central function stops being the payer of record economically: it becomes a pass-through, and the cost lands where the consumption happened.
Chargeback changes incentives in a way showback cannot, because a team spending its own budget behaves differently from a team spending a central pool. It also demands much more of the organization: accurate attribution, a legible method, finance processes for internal transfers, and a dispute channel, because now every mapping error is somebody's money. We covered the build in detail in building a chargeback model for AI coding tools.
Showback vs chargeback: side-by-side
- Money movement. Showback: none; central budget pays, teams see statements. Chargeback: internal transfers move each team's share onto its budget.
- Primary goal. Showback: visibility, awareness, and trust in the numbers. Chargeback: accountability and cost ownership.
- What it demands. Showback: consumption data, an attribution map, published allocation rules. Chargeback: all of that, plus finance integration, budget-holder agreement, and a formal dispute process.
- Risk if the data is wrong. Showback: an awkward conversation and a correction. Chargeback: a billing dispute that can stall the whole program.
- Behavioral effect. Showback: meaningful; visibility prompts voluntary cleanup. Chargeback: stronger; budget ownership disciplines consumption decisions.
- Organizational readiness. Showback: works from day one, even with imperfect data. Chargeback: requires trusted data and a culture prepared for internal billing.
A worked example: one shared bill, two treatments
Say a company spends $60,000 a month on a shared engineering platform and tooling stack, consumed by three groups. Metered usage attributes 45% to the Payments group, 35% to Platform, and 20% to Mobile.
Under showback, the central engineering budget pays the $60,000. Each month, Payments receives a statement for $27,000, Platform for $21,000, Mobile for $12,000, alongside seat counts, usage trends, and per-developer figures. No budget moves. Within a quarter, the statements do their work: Payments notices its number includes 30 seats with no activity at $39 each ($1,170 a month of pure waste) and releases them. Nobody mandated it; the report made the waste visible to the people who could act.
Under chargeback, the same three numbers become internal transfers: $27,000, $21,000, and $12,000 land on the three groups' budgets, and the central line nets toward zero. Now the incentive is structural. When Payments plans next quarter's headcount, the tooling cost of each new hire is in its own budget math, and when a vendor raises prices, the conversation happens in three budget reviews, not one.
The example also shows why sequencing matters: if the company had started with chargeback and the 45/35/20 split contained a mapping error, the first month's transfers would have triggered a dispute about the methodology. Running showback first surfaces those errors while they are cheap.
A decision framework: which model, when
Five questions determine which model fits right now:
- Is the attribution trusted yet? If teams have not seen and challenged the numbers, start with showback. Chargeback on untrusted data fails predictably.
- What problem are you solving? If the problem is that nobody knows what anything costs, showback solves it. If the problem is that teams know and do not care because the money is not theirs, that is the chargeback signal.
- Can finance operate it? Chargeback needs internal billing machinery and a dispute process. If that does not exist, showback delivers most of the value with none of the overhead.
- Is the spend material per team? Cross-charging trivial amounts costs more in process than it returns in discipline. Show small costs; charge material ones.
- Will the culture bear it? Internal billing changes how teams relate to a central function. Some organizations want that contract; others get the behavior they need from visibility alone.
The general sequence holds: lead with showback, and graduate to chargeback the specific costs where ownership, not just awareness, is what the organization needs.
From mainframe chargeback to cloud, SaaS, and AI
Chargeback is older than most of the tools it now governs. It originated in the mainframe era, when computing was a single scarce machine and data center teams metered CPU time, storage, and print volume to bill departments for their share. Mainframe chargeback worked because the resource was centralized and the metering was exact. The mechanics are still in production today, and we walked through them in mainframe chargeback and showback.
Every era since has stretched the model. Distributed computing scattered the resources. SaaS scattered the vendors, each with its own console and its own definition of a seat. Cloud made consumption granular and elastic, and made FinOps a discipline. The newest strain is AI tooling, where costs are metered in credits, tokens, and premium requests that no two vendors define alike, and where adoption spreads bottom-up, ahead of any budget process. The principles have not changed since the mainframe days: meter consumption, attribute it, make someone accountable. What changed is that the metering and attribution now have to be assembled from a dozen disagreeing sources, which is why modern showback and chargeback programs live or die on data normalization, not on accounting.
Showback and chargeback for AI coding spend
AI coding assistants are currently the sharpest version of this problem. The assistants engineering teams connect (GitHub Copilot, Cursor, Claude, and whatever they adopt next) bill in different units on different cycles, mix seat licenses with metered usage, and change pricing often. That makes AI showback (running the showback loop on AI tool consumption) both more valuable and more demanding than classic IT showback: more valuable because the spend is variable and growing, more demanding because the normalization layer has to reconcile seats, credits, and tokens before any team-level statement means anything. The groundwork is the same either way: collect every vendor's data, reconcile identities, normalize definitions, and we laid it out step by step in how to track AI code assistant spend across every vendor. That foundation is exactly what Olumia provides for finance teams: read-only connections to each assistant's admin data, normalized into per-team statements, forecasts, and chargeback-ready allocations.
Showback and chargeback FAQ
What is IT showback?
IT showback is reporting each team's consumption of shared IT resources, and the cost of that consumption, without billing them. It is a visibility practice: the central budget keeps paying, and teams see regular statements of their share. See our full guide to IT showback.
What is the difference between chargeback and showback?
Chargeback moves money; showback does not. Both allocate shared costs to consuming teams using the same attribution, but showback delivers the result as information while chargeback delivers it as an internal transfer against each team's budget.
Do you have to run showback before chargeback?
It is not mandatory, but it is the sequence that works. Showback builds trust in the attribution while the stakes are low; chargeback introduced before that trust exists tends to collapse into disputes about the numbers rather than conversations about the spend.
What does IT showback and chargeback software do?
Showback and chargeback software automates the loop that spreadsheets cannot sustain: it ingests cost and usage data from every vendor and platform in scope, maps consumption to teams and cost centers, normalizes definitions across sources, applies allocation rules, and produces per-team statements, and, for chargeback, feeds the resulting allocations into finance systems. The category spans cloud cost tools, IT financial management suites, and specialized layers for newer spend categories like AI coding assistants. We set out the evaluation criteria in detail in what to look for in IT showback and chargeback software.
What is AI showback?
AI showback applies the showback model to AI tool spend: measuring each team's consumption of AI assistants and services (seats, credits, tokens, requests), normalizing it across vendors, and reporting each team's share of the cost without internal billing. It is the recommended starting point for governing AI spend because the pricing models are new and the data needs a trust-building period before anyone charges on it.
Is chargeback worth it for small organizations?
Usually not at first. Below a certain spend, the process cost of internal billing outweighs the discipline it buys. Small organizations typically get what they need from showback: visibility, waste cleanup, and defensible budgeting, with chargeback reserved for the point where team-level spend becomes material.
What is IT showback and chargeback management?
IT showback and chargeback management is the operating practice around the two models rather than the reporting itself. It covers who owns the allocation rules, how often statements go out, how disputes are raised and resolved, how the attribution map is kept current as teams reorganize, and how specific cost categories graduate from showback to chargeback over time. Most programs fail on management rather than on math: the first statements are accurate, then a reorg breaks the team mapping and nobody owns fixing it. Naming an owner and a review cadence is what separates a program that compounds from one that quietly stops being trusted.
How do showback and chargeback work at enterprise scale?
The models are identical at any size; the hard parts change. At enterprise scale the attribution map has to survive constant reorganization, so allocation is usually keyed to cost centers from the finance or HR system of record rather than to team names. Data volume forces automation, because manual reconciliation stops being viable somewhere around a few thousand users and a handful of vendors. The dispute process becomes formal, with a published methodology, a stated correction window, and a named owner per business unit. Large organizations also tend to run both models at once: chargeback for material, well-understood costs, and showback for everything new, with categories moving across as the data earns trust.
How do you do chargeback and showback for AVD (Azure Virtual Desktop)?
Pooled virtual desktop environments break the usual tagging approach, because a tag attaches to the session host VM rather than to the person using it, and in a pooled host pool many users share the same VM. Resource tags will tell you what a host pool cost; they will not tell you which department consumed it.
The workable pattern has three parts. Use Azure Cost Management, with tags on host pools, storage, and shared infrastructure, for the cost side. Use session data, from Azure Virtual Desktop Insights or your broker connection logs, as the usage driver, typically session hours per user. Then join user to department through your directory. Each department is charged its share of session hours applied to the pooled cost, plus any dedicated personal host pools attributed directly. Start this as showback: session-hour allocation always looks unfair to somebody the first time they see it, and you want that argument to happen before money moves.
What is an IT showback model, and what does one look like?
An IT showback model is the specific rule set that turns raw consumption into each team reported share: the cost pools in scope, the allocation driver for each pool, the mapping from consumption to teams, and the reporting cadence. A simple worked example: the collaboration and productivity pool is allocated by headcount, the compute pool by metered CPU hours, and the AI tooling pool by assigned seats plus metered usage. Every month each team receives a statement carrying those three lines, its share of each, and the trend.
Publishing the model matters as much as computing it. A team that can see why it was allocated a number will argue about the driver, which is a productive argument that improves the model. A team that only sees the number argues about the whole program.
What is an IT chargeback model?
An IT chargeback model is the same rule set with money attached: the same cost pools, drivers, and mapping, plus a rate structure and the finance mechanics for moving amounts onto team budgets. The extra decisions are pricing ones. Teams can be charged actual cost, a fixed internal rate set at the start of the year, or a rate that includes an overhead uplift for running the shared service. Fixed internal rates make budgeting predictable for consuming teams but leave the central function absorbing the variance; actual-cost pass-through does the reverse. Most organizations choose predictability for stable costs and pass-through for volatile ones like cloud and AI usage.
What is cloud showback?
Cloud showback applies the model to cloud infrastructure spend: attributing each team share of compute, storage, data transfer, and managed services, then reporting it back without internal billing. It is the most mature version of the practice, because cloud billing data is granular, tagged, and available through native cost tools, which is why FinOps grew up around it. The unsolved parts are the shared ones. Untagged resources, shared clusters, support charges, commitment discounts, and reserved-capacity amortization all have to be allocated by a rule rather than read off the bill. Those same shared-cost problems are what make AI tooling spend hard, one layer up.
The takeaway
Showback shows; chargeback charges. Showback earns confidence in the data and starts changing behavior at low stakes. Chargeback converts that confidence into ownership. Lead with showback, publish the method, let disputes make the data good, then charge back the costs where ownership matters. The sequence is not optional; it is what separates allocation programs that stick from ones that collapse into arguments about the numbers.
Top comments (0)