When should IT move from showback to chargeback?
In brief
Chargeback changes behavior only where consumers control demand and cost falls when they cut it. A worked example, failure modes and a readiness checklist.
Steve Elliott · · 7 min read
On this page
Move to chargeback only for services where the consumer can change demand and the provider's cost actually falls when they do. For services that are mostly fixed cost, a charge moves money between budgets without changing what the company spends, and in our view it tends to produce disputes rather than savings.
That makes chargeback a service-by-service decision, not an organization-wide maturity step. For definitions, see our glossary entry on chargeback vs showback.
Is chargeback the next step after showback?
Not necessarily. The FinOps Foundation's Invoicing & Chargeback capability defines chargeback as the formal posting of expenses to official accounting budgets. Showback can be used at any level of detail and involves no formal posting. The Foundation says showback is always required in a FinOps practice, but "Chargeback is not always required in every organization." It says neither should be considered more mature than the other, and that where costs fall to a single cost center or an easily allocated set, the cost and burden of official chargeback may be unwarranted.
Neither TBM Council source we reviewed ranks one above the other. The Council's practice lead's guide says the Consumer layer of the TBM Taxonomy is what you use to "operationalize defensible showback or chargeback models." Its allocation guidance lists internal chargeback requirements as one trigger for moving from direct or fixed allocations toward consumption-based and more advanced drivers.
In our view, the useful question isn't whether the organization is mature enough for chargeback. It's for which services a real charge would change a decision someone can actually make.
When does chargeback change behavior?
We think IT chargeback earns its overhead only when four conditions hold for a given service. In our view, three out of four is where disputes start.
- The consumer can change demand. A business unit can delete storage, release licenses or shut down cloud instances. It can't opt out of the security operations center or the ERP it is required to use. In a 2022 talk at the Joint IT & Software Cost Forum (IT-CAST), Technomics cost analyst Alex Thibault, then staffed at DHS headquarters, argued that itemized, consumption-based bills make customers more price-sensitive and push them to right-size, for example by dropping unused devices and over-provisioned storage.
- Unit rates are trusted. The consumer has to believe the rate reflects cost and be able to see how it was built. The TBM Council's allocation checklist includes questions such as: can you trace every dollar from source to consumer, explain the rule to a non-technical person in 30 seconds, and defend it to an auditor or the CFO?
- Drivers are stable and measurable. The driver, whether gigabytes, instances, tickets or seats, should come from data the consumer recognizes and can check. The TBM Council lists hard-coded flat percentages and missing usage data among the red flags of poor allocation.
- Finance systems can book internal transfers. The FinOps Foundation lists general ledger requirements as inputs to chargeback: chart of accounts, cost centers, business unit and location codes. Its most advanced stage has chargeback automated into finance systems. Its early stage runs on spreadsheets and manual journals, which in our view makes the internal bill a workload of its own.
What happens to a unit rate when a consumer cuts usage?
In our view, this is where chargeback programs most often lose credibility. The numbers below are illustrative, not from any organization.
Take an internal storage service that costs $1.2 million a year. Of that, $840,000 is fixed for the year: staff, array depreciation, data center space and support contracts. The other $360,000 is variable and scales with capacity used. Consumers use 1,000 TB, so the average unit cost is $1,200 per TB per year. Business unit A uses 300 TB and is charged $360,000.
Unit A deletes 100 TB. Here is what happens under three rate designs.
| Rate design | Unit A's charge | Other units' charges (700 TB) | What the company saves |
|---|---|---|---|
| Average rate, recalculated after the cut | Falls $101,333, to $258,667 | Rise $65,333, to $905,333 | $36,000 |
| Average rate, fixed for the year | Falls $120,000, to $240,000 | Unchanged at $840,000 | $36,000, and IT under-recovers $84,000 |
| Two-part rate: fixed share set at budget time, plus $360 per TB | Falls $36,000, to $324,000 | Unchanged at $840,000 | $36,000 |
Only $36,000 goes away when 100 TB does, because only the variable part of the cost scales with use. Under a recalculated average rate, unit A is told it saved nearly three times what the company saved, and other units pay the entire difference, $65,333, without changing anything they do. Under a fixed annual rate, the gap lands on IT as an $84,000 shortfall at year end. The fixed cost can fall later, at the next array refresh, but only if someone acts on the lower demand. Of the three, the two-part rate is the only design where the consumer's saving equals the company's.
The same pattern shows up in public-sector cost recovery. GAO's 2019 review of Defense-wide working capital funds found Army and Navy customers "confused about why declines in their use" of the Defense Finance and Accounting Service's services had not reduced their costs. GAO found customers lacked visibility into what drove their costs, including how indirect costs were allocated. It recommended that DFAS, the Defense Information Systems Agency and the Defense Logistics Agency give customers more complete information on their rate-setting methods, including the costs in their rates and how they are calculated. For DFAS and DISA, that included how changes in workload affect a customer's overall costs. DOD concurred, and GAO has closed the recommendations as implemented.
How does chargeback backfire?
These are the failure modes we think matter most. They are our reading of how the incentives work, not survey findings.
- Gaming the driver. Charge per seat and teams share accounts. Charge per ticket and people stop raising tickets and message an engineer directly. Effort goes into working the driver rather than reducing the cost.
- Shadow IT. If the internal rate looks higher than a SaaS subscription on a corporate card, some teams will buy outside. The internal rate often carries enterprise security review, support and integration that the card price leaves out. Fixed costs then spread over fewer consumers, and the rate rises again.
- Disputes. Every charge is a budget hit someone can contest. Without a published rate method and a dispute process with a deadline, finance spends the close arguing about allocations.
- Internal billing overhead. The FinOps Foundation notes that cloud provider invoices usually arrive 3 to 12 days after month end, so chargeback often runs on estimates, with true-up journal entries later and a correction process for changes after close. That is monthly work that produces no new service.
- Penalizing shared services. Charging for security, architecture or a shared data team discourages use the enterprise wants. In our view, services that exist for enterprise reasons should be funded centrally and shown, not charged.
What are the options between showback and chargeback?
| Option | How it works | Where it fits |
|---|---|---|
| Showback only | Consumers see their allocated cost; no money moves | Fixed, mandatory or enterprise-wide services |
| Showback with targets | Consumers see cost against an agreed target, reviewed in budget meetings; no money moves | Services with early data or soft drivers |
| Partial chargeback of variable services | Charge services where use drives cost, such as cloud, storage, licenses and devices; show the rest | A sensible starting point for most organizations, in our view |
| Two-part rate | A fixed share set at budget time, plus a variable rate per unit | Capacity services where consumers commit in advance |
| Full chargeback | All IT cost recovered through rates | Shared services run as a business, or funds required to recover their costs |
Full recovery is normal in some settings. GAO's 2016 review of the FAA and Treasury franchise funds, which sell shared services to other agencies, found both had operated on a self-sufficient basis, recovering all operating expenses over the prior six years, and shared price sheets with customers.
For most enterprise IT functions, we think partial chargeback of variable services is the right default. It puts a real price on the costs consumers can cut, and the fixed versus variable split in your cost model tells you where to draw the line. Showback with targets keeps the rest of the bill in front of the people who shape demand, which, as we argue in why IT cost transparency projects stall, is the part we think many programs miss.
Is your organization ready for chargeback?
Run this checklist for each service you plan to charge, not for IT as a whole.
- A named consumer controls demand. They agree they can change it.
- You know the fixed and variable split. The rate design reflects it, so a consumer's saving isn't overstated.
- The rate method is published. It shows the costs included, how they are calculated and how a change in workload affects a consumer's charge, the three items GAO asked DFAS and DISA to disclose.
- The driver has survived showback. In our view, a few months of showback without material disputes is the minimum.
- Finance can post charges to cost centers each month. The estimate and true-up process is agreed with accounting.
- There is a dispute process. It has an owner and a deadline.
- Year-end under- or over-recovery has an owner. Someone decides in advance who absorbs it.
- Charges stay inside one legal entity, or tax has reviewed them. Charges between legal entities can have transfer-pricing and other tax consequences. Confirm the treatment with your tax and accounting advisers.
In our view, chargeback works best when the charge sits next to the decision it is meant to change, with the demand plan, the budget and the service owner's capacity plan in one operating model.
Sources
- FinOps Foundation, Invoicing & Chargeback, FinOps Framework capability page (no date shown; accessed November 2026)
- TBM Council, The TBM Practice Lead's Guide to the TBM Taxonomy, May 1, 2026
- TBM Council, TBM Modeling Allocation Methods, published July 16, 2025, updated September 4, 2025
- GAO, Defense Management: Defense-Wide Working Capital Fund Agencies Apply Most Key Operating Principles but Should Improve Pricing Transparency (GAO-20-65), November 1, 2019
- GAO, Revolving Funds: Additional Pricing and Performance Information for FAA and Treasury Funds Could Enhance Agency Decisions on Shared Services (GAO-16-477), May 10, 2016
- Alex Thibault, Technomics, Data-Driven IT Service Chargeback Modeling, presented at IT-CAST, September 15, 2022
Frequently asked questions
Is chargeback more mature than showback?
No. The FinOps Foundation says neither is more mature than the other. It treats showback as always required in a FinOps practice and chargeback as dependent on organizational accounting policies. Where costs fall to a single cost center or an easily allocated set, it says official chargeback may not be worth the burden. In our view, the choice should be made service by service.
Which IT services should be charged back first?
In our view, start with services where consumption drives cost and the consumer controls consumption: public cloud, storage, devices and per-seat software licenses. Keep fixed, mandatory and enterprise-wide services such as security and core infrastructure on showback, so a business unit isn't charged for something it can't reduce and the shared service isn't discouraged.
Why didn't our IT charge fall when we used less?
Usually because most of the service's cost is fixed for the year. When usage falls, the provider's costs fall only by the variable part, so a recalculated rate rises and recovers the fixed cost from everyone. GAO found the same confusion among Army and Navy customers of a Defense working capital fund, and recommended clearer disclosure of rate methods.
Does chargeback reduce what the company spends?
Not by itself. Chargeback moves cost between budgets, so the enterprise total is unchanged until consumers cut demand and the provider removes the cost behind it. Savings come from the variable part of a service right away and from fixed capacity only at the next contract, refresh or staffing decision. Charges between legal entities may also have tax effects; confirm with advisers.
Steve Elliott
Published November 22, 2026
More on TBM & IT Financial Management
Cost pools, towers, showback, unit cost.
Keep reading
How business relationship managers should use TBM data
BRMs sit closest to business demand, so they should do more than receive TBM reports. How BRMs can use the bill of IT, intake and value reviews instead.
TBM, ITFM or FP&A: who should own IT cost?
ITFM is the function, TBM the method, FP&A the enterprise planning team. How their remits differ, where they collide, and our view on who should own IT cost.
Cost center or product P&L: where technology cost should land
Should technology run as a cost center, a shared-services recharge or inside product P&Ls? What each model does to behavior, plus a worked margin example.
On the TBM Council's numbers, tokens are 4.5–15% of AI cost. What that means for your budget
The TBM Council puts labor at 50–70% of AI project cost. On its numbers, tokens are 4.5–15% of the total. What the figures show and what to budget for.