Cost allocation is the lowest-glamour part of software cost management and one of the highest-leverage. The chargeback model determines whether business units consume software like a free good or like a budgeted line item. The wrong model produces shelfware and sprawl; the right model produces self-correcting demand. This guide walks through the allocation patterns we have seen work — and the ones that quietly fail.
The most reliable predictor of software shelfware and SaaS sprawl inside an enterprise is the absence of a working chargeback model. When IT carries software cost centrally and business units consume without seeing the bill, demand expands to fill the budget. When business units pay for what they consume — through a transparent, predictable allocation — demand self-corrects. This is the simplest, most-replicated finding in the FinOps literature, and it applies equally to traditional licensing and cloud.
The allocation driver is the metric the chargeback is based on. The driver determines what behaviour the model incentivises. Five drivers are common, with very different consequences.
Allocate by business-unit headcount. Simple, defensible, easy to maintain. The right driver for productivity tools (Microsoft 365, Zoom, Slack). Wrong for capability that is consumed unevenly across the workforce (Salesforce, Tableau, design tools).
Allocate by users entitled in the business unit. The right driver for capability with variable per-user adoption. Self-correcting because business units have an incentive to reclaim entitlements from leavers.
Allocate by units consumed — compute hours, transactions, queries. The right driver for cloud and consumption-based platforms. The driver with the strongest demand-shaping effect; also the hardest to forecast for business-unit budgeting.
Allocate by business-unit revenue. Simple but blunt — does not reflect actual software use, only the unit's contribution to the cost base. Often used as a fallback when other drivers are not measurable.
Most enterprises end up with a hybrid: headcount for productivity tools, named-user for business applications, consumption for cloud, revenue for shared infrastructure. The hybrid is operationally more complex but produces the cleanest demand signals.
We design chargeback frameworks buyer-side. No platform commissions.
The single most important design choice in any chargeback model is the visibility of the bill to the business-unit P&L owner. A chargeback that flows through corporate-allocation noise is functionally a tax and is ignored. A chargeback that lands as a discrete monthly line on the BU P&L, with month-over-month variance commentary, produces immediate demand discipline. The difference is governance, not finance.
The CFOs who have made the transparency switch consistently report a one-time 6-14% reduction in BU-driven SaaS and cloud demand inside ninety days. The reduction is not a saving in any one renewal; it is a permanent change in the consumption trajectory. The compounding effect across budget cycles is material. Pairing the chargeback discipline with a structured license cost reduction programme means the demand signal compounds against a falling baseline rather than a fixed one.
The governance patterns — including chargeback and allocation — that hold software cost programmes across multi-year cycles.
The most common allocation errors we see in CFO clients: (1) allocation lag — last quarter's actuals billed in the current quarter, removing the behavioural signal; (2) over-aggregation — multiple capabilities rolled into one chargeback line, hiding the demand drivers; (3) under-allocation — IT absorbs the variance between forecast and actual, removing the BU incentive to forecast accurately; (4) one-size driver — using headcount for capability that is not headcount-driven; (5) shared-services fudging — moving capability into shared services to escape allocation pressure.
We design chargeback frameworks buyer-side. No platform commissions, no vendor partnerships.
Weekly compliance intelligence for IT leaders.