SaaS Chargeback vs Showback: Which Model Is Right for Your Organisation?

Centralised IT budgets create a fundamental accountability problem: the teams consuming the most SaaS have no financial incentive to optimise their usage, because the cost is absorbed elsewhere. Chargeback and showback are two approaches to changing that dynamic.

Showback

Showback allocates costs to business units for visibility only — no actual budget transfer occurs. The Engineering team sees that they account for £45,000 of the annual SaaS bill; Sales sees their £32,000. This visibility creates awareness and often motivates voluntary optimisation without the administrative overhead of actual cost transfers.

Chargeback

Chargeback transfers actual costs to departmental budgets. If Engineering uses £45,000 of SaaS, £45,000 comes out of their budget. This creates the strongest accountability signal — department heads who see real budget impact have the strongest incentive to manage utilisation. The challenge is the administrative overhead and the occasional conflict over allocation methodology.

Which to Choose

Start with showback. It creates the visibility and accountability conversations without the political complexity of actual budget transfers. After two to three reporting cycles, if behavioural change isn't happening, consider moving to full chargeback for the largest cost centres.

Building the Allocation Methodology

Before implementing either chargeback or showback, you need a robust allocation methodology that departments will accept as fair. The cleanest approach for most organisations is seat-based allocation: allocate each tool's cost in proportion to each department's share of active seats. This is objective, calculable from your SaaS management data, and intuitively fair — departments that use a tool more pay more for it.

Some tools are used by the whole organisation regardless of department — email, communication platforms, company-wide productivity software. For these, allocate by headcount (each department's share of total employees) rather than by tool-specific usage. Document your methodology for each category and publish it so departments understand how their allocation is calculated before they receive their first chargeback or showback report.

Communicating Showback Results

The value of showback depends entirely on how the results are communicated and discussed. A PDF report emailed to department heads monthly is unlikely to drive meaningful behaviour change. A brief monthly review meeting — even 20 minutes, even virtual — where IT or Finance walks through each department's spend, highlights changes from prior month, and invites questions creates genuine engagement with the data.

Frame showback conversations as collaborative — the goal is to help department heads understand their costs and find optimisation opportunities together, not to hold them accountable for spending money. The shift to a more accountability-focused conversation happens naturally as leaders become comfortable with the data; forcing it too early creates defensiveness rather than partnership.

Tracking Behavioural Change

The ultimate measure of a chargeback or showback programme's success is behavioural change: are business units making better software purchasing decisions? Metrics to track include: the percentage of new tool requests that come through the formal procurement process (versus being discovered as shadow IT after the fact), the rate of voluntary licence reductions from department heads who identify unused seats in their reports, and the year-over-year change in per-employee SaaS spend by department. Positive trends in these metrics confirm that financial visibility is translating into better decisions.