IT Chargeback vs Showback: Models, Methods, and Examples

IT chargeback is a way to allocate the cost of IT services, hardware, and software to the business units that use them. Think of it as an internal economic model: IT tracks what each group consumes, then "charges back" that cost as a line item in the group's budget.

IT showback tracks the same costs but stops short of billing. That is the core difference in chargeback vs showback: chargeback moves cost onto the consuming department's budget, while showback reports the cost without moving any money. Showback makes departments aware. Chargeback makes them accountable.

Both models centralize spend visibility, and both have always been hard to run because the data work is manual and the reports are hard to keep accurate. It's hardest with SaaS and AI tools. Apps get bought on corporate cards, shared across teams, and billed on seats or on usage that changes every month.

Chargeback vs Showback: Key Differences

Chargeback and showback start from the same data. What changes is what happens after the report goes out.

Most teams don't have to pick one forever. Many start with showback to build trust in the data, then move to chargeback once the numbers are defensible. Some stay on showback permanently, and that's fine: if visibility alone changes how teams buy and use software, there's no need to add billing overhead. For a closer look at the billing mechanics, read our full explainer on how IT chargebacks work.

Why IT Uses Chargeback and Showback Models

The spread of SaaS tools has created new challenges for IT, and keeping their costs under control is one of the biggest.

Often IT owns and pays for a tool that many other departments use. In other cases, one department buys a core tool and other departments start using it too. When those departments have no visibility into the cost, nobody is accountable for it, and the tools start to look free.

Take Box as an example. The company picks it for file sharing. IT buys it and budgets for it, while every employee in the company uses it.

Or take CRM software. Sales uses and pays for Salesforce. Then Customer Support and Marketing decide to use Salesforce as well. Who owns the Salesforce budget now? Should Sales pay for the seats other departments use?

This is where IT chargeback and showback help. A chargeback report shows what each department should be charged for the IT resources it consumes. That visibility creates accountability. Departments make sure the services they pay for are actually used, which cuts wasted and underused licenses and weeds out duplicate tools.

IT Chargeback Models and Methods

An IT chargeback model is the set of rules that decides how a cost gets split. The methods range from rough estimates to metered precision. These are the most common:

• High-level allocation: Split the cost by a generic key such as headcount or revenue. It's simple to run, but it says little about who actually uses what.
• Low-level allocation: Split the cost by IT-related drivers such as the number of users, devices, or accounts in each department. It's closer to real consumption without full metering.
• Measured resource usage: Charge for actual consumption, such as compute hours, storage, or API calls. It's the most precise method and needs the best data.
• Tiered flat rate: Set a few usage tiers with a fixed price for each. Departments know what to expect, and heavy users pay more.
• Negotiated flat rate: IT and a department agree on a fixed charge for a set of services over a period. It's predictable, but it drifts from reality if usage changes.
• Service-based pricing: Publish a priced service catalog (a laptop bundle, a CRM seat, a support tier) and charge departments for what they order from it.

Allocation Strategies for SaaS Apps

SaaS apps don't all bill the same way, so no single strategy fits every app. These four cover most of what you'll see:

1. Bottom-up (cost per license): Use this when different license types cost different amounts. Each department is charged for the specific licenses its people hold.
2. Bottom-up (cost per user): Use this when you pay the same price per user regardless of license type. You enter one cost per user, and each department pays for its users.
3. Top-down (from expenses): Use this for apps that aren't charged per seat. The app's expenses are spread across its users, which gives you a cost per user to roll up by department.
4. Top-down (from contracts): Use this when the contract is the best record of what an app costs. The contract value is split across the people and teams using the app.

IT Chargeback Model Examples

Here is how those strategies play out on the kinds of tools most companies share.

Salesforce Shared by Sales, Support, and Marketing

Sales bought Salesforce, but Support and Marketing now use it too, and each team holds a different mix of license types. A bottom-up chargeback by cost per license charges each department for the exact licenses its people hold, so Sales stops paying for everyone else's seats.

Box or Another Company-Wide Tool

IT buys a file-sharing tool like Box for the whole company at one price per user. A bottom-up chargeback by cost per user charges every department for its own users. Even if you stay on showback, each department sees what its share of a "free" tool really costs.

Firewall, Network, and Cloud Infrastructure

Firewalls, network infrastructure, and cloud computing aren't billed per seat, and there's no clean list of users. A top-down split by percentage is the practical choice: IT agrees on each department's share, applies it to the total cost, and revisits the split as the business changes.

AI Tools Like ChatGPT or Claude

AI tools are often billed on usage rather than seats, and spend can swing sharply from month to month. Allocate top-down from expenses: take what the company spent on the tool and spread it across the people using it. Start with showback here. Usage is volatile, and teams need time to understand their numbers before those numbers hit their budgets.

How to Implement an IT Chargeback Process

A chargeback program succeeds or fails on whether budget owners trust the numbers. These six steps build that trust before any money moves.

1. Build a complete app and cost inventory. List every app the company pays for and what it costs, including shadow IT bought outside of IT. You can't allocate a cost you can't see.
2. Map every user to a department, cost center, or division. Pull this from the HR system so the mapping stays current as people join, move, and leave.
3. Pick an allocation strategy per app. Match each app to how it's billed: per license type, per user, from expenses, or from contracts.
4. Start with showback and let budget owners review. Share the reports without moving money. Let department heads question the numbers and fix the mapping where it's wrong.
5. Set a dispute window, then move to chargeback. Give budget owners a fixed period to challenge charges each cycle. Once disputes are rare, start billing.
6. Review on a regular cadence and act on what you find. Chargeback reports surface unused licenses, duplicate tools, and apps nobody owns. The savings come from acting on them.

Common Challenges

Gathering data. Most IT teams already struggle to know who uses which tool and which department each person belongs to. Shadow IT apps with overlapping capabilities make it harder. Building an up-to-date chargeback report by hand often fails because the effort doesn't seem worth the return.

And the complexity keeps growing. According to Gartner, “Through 2027, organizations that fail to attain centralized visibility and coordinate SaaS life cycles will overspend on SaaS by at least 25% due to incorrect and unnecessary entitlements and not rationalizing overlapping tools and instances.”

[Read the 2026 Gartner Magic Quadrant for SaaS Management Platforms]

Without a SaaS Management Platform, gathering chargeback data is a long, manual process, and that alone keeps many companies from starting.

Ensuring accurate data. Chargeback puts a cost next to each department's name, so expect pushback. If the data is wrong, stakeholders stop trusting the report, and the whole process stalls.

Choosing the right strategy per app. Different apps need different allocation strategies. Forcing one method onto every app produces charges that don't match how the app is billed, and those are the charges budget owners dispute first.

IT Showback and Chargeback Software

Spreadsheets work for a handful of apps. Past that, you need software that keeps the data current. Look for:

• Automatic discovery of apps and users, so the inventory includes tools bought outside of IT.
• Direct integrations for license data, so user and license counts come from the apps themselves rather than from manual exports.
• A choice of strategy per app, because a per-license CRM and a usage-billed AI tool shouldn't be split the same way.
• Rollups by department, cost center, or division, to match how your finance team already reports.
• Recalculation as data changes, so reports reflect who has access today, not last quarter.
• Exportable reports that budget owners and finance can review and reconcile.

IT Chargeback and Showback with Torii

Torii's Cost Allocation report breaks each app's cost down by department, cost center, or division, so you can see how much every part of the business spends on software.

1. Four allocation strategies: Choose bottom-up by cost per license, bottom-up by cost per user, top-down from expenses, or top-down from contracts for each app.
2. Real users, not estimates: For integrated apps, Torii pulls the current users with access through its direct integrations.
3. Always current: Every day, after Torii finishes syncing your integrations, it recalculates all allocations using the latest data.
4. One report or one app: See the consolidated report under Expenses > Cost Allocation, or open an app's Cost Allocation tab to configure and review a single app.

Chargeback works best as part of a wider SaaS governance program, where the same data that assigns costs also drives decisions about which apps to keep, consolidate, or cut.

Conclusion

IT chargeback and showback both create accountability for software costs across departments and business units. Showback gives teams visibility. Chargeback adds budget impact. Many companies start with the first and grow into the second as their data earns trust.

The hard part has always been the data: finding every app, mapping every user, and keeping the numbers current. With Torii, allocations recalculate every day from your latest integration data, so your team can spend its time acting on what the reports reveal.