Two ways to make internal costs visible
When a central team serves several business units, someone has to decide who pays for it. There are three broad answers. The cost can sit in a central budget with no allocation at all. It can be reported to each unit without actually moving any money, which is called showback. Or it can be billed to each unit, so that money moves between internal budgets, which is called chargeback.
The difference is whether the number has consequences. Under showback, a unit sees a statement saying, in effect, “you used this much, which would cost this much.” Under chargeback, that amount is deducted from the unit’s budget or added to its costs.
Both approaches rely on the same groundwork: knowing what the service costs to run, what units it delivers, and who consumed them. Without that, any figure shown or billed will be argued about.
How showback works
In showback, the service team measures usage and attaches a cost to it, then circulates a regular report. Nothing is invoiced. The aim is awareness.
Advantages
- It is simple to introduce, because no accounting entries or budget transfers are needed.
- It starts a useful conversation about demand without creating immediate conflict.
- It lets the service team test its cost model and fix errors before money depends on it.
- It carries less risk of units avoiding the service to dodge a charge.
Disadvantages
- With no financial consequence, some units may ignore the reports.
- It may do little to change behavior, so demand can keep growing unchecked.
- Reports can be dismissed as theoretical if units doubt the figures.
How chargeback works
In chargeback, the service team prices its output and bills customers, either per unit consumed or through a fixed periodic fee. The money is a real transfer within the organization’s books.
Advantages
- Units have a financial reason to think about what they request.
- Costs land on the units that cause them, which many people regard as fairer than spreading them evenly.
- The service team gets a clearer signal about demand, and can see which offerings are valued.
- It encourages the service to explain and justify its costs.
Disadvantages
- It needs more administration, including accurate usage tracking, billing and dispute handling.
- Units may cut back on useful services to save budget, even when the organization as a whole would benefit from their use.
- Arguments about rates, allocation rules and disputed charges can take considerable time.
- It can make the relationship between the central team and its customers feel adversarial.
- If rates are poorly set, they can create odd incentives or hide inefficiency.
A simple illustration
The numbers below are invented to show the arithmetic only.
Suppose a central payroll team costs 120,000 a year to run and processes 12,000 payslips in total across three business units.
| Unit | Payslips | Share of total |
|---|---|---|
| North | 6,000 | 50% |
| South | 4,000 | one third, about 33% |
| West | 2,000 | one sixth, about 17% |
The cost per payslip is 120,000 divided by 12,000, which is 10. Under a usage-based approach, North would be shown or charged 60,000, South 40,000 and West 20,000. These three amounts add up to the full 120,000.
Under showback, each unit receives a report with its figure and nothing else changes. Under chargeback, the amounts move into the units’ budgets. An alternative would be to split the 120,000 equally, giving each unit 40,000, which would be simpler but would make West pay twice what its usage suggests and North pay less.
This also highlights a practical problem: much of the team’s cost is fixed. If West were to leave the service, the team would not become one sixth cheaper. The remaining units might simply face a higher cost per payslip, which is a common source of friction.
Choosing an approach
There is no universally better option. Some points that usually matter:
- Maturity of the service. A newly formed team with uncertain cost data often fits showback better, since mistakes in the early figures do not hurt anyone.
- Nature of the work. Services where demand varies widely and can be controlled by customers suit usage-based charging more than those where demand is set by the business, such as statutory processing.
- Quality of measurement. Charging requires trusted, auditable usage data. If this does not yet exist, charging is premature.
- Organizational culture. Where units already work with internal budgets and transfers, chargeback may feel natural. Where it would be new, it may feel punitive.
- Purpose. If the goal is cost awareness, showback may do. If the goal is to influence demand or to make units fund what they use, chargeback is closer.
Many organizations start with showback for a period, then move selected services to chargeback once rates and data are trusted. Others never move, and that is a reasonable result.
Practical safeguards
Whichever approach is used, a few habits help:
- Keep the rules simple enough to explain in a couple of sentences. A model nobody understands will not be trusted.
- Publish the rates and method so units can check them.
- Separate fixed from variable costs where possible, and be open about how fixed costs are shared.
- Record a performance baseline before charging begins, so later changes in demand can be judged against something.
- Review periodically, since volumes and costs shift.
- Watch for side effects, such as units sidestepping the service or avoiding legitimate use because of the price.
The reporting itself can be linked to an internal service catalog, so that each line on a statement maps to something the customer recognizes. Questions about what a function contributes beyond its cost, and how to judge it fairly, are covered under internal function value. Any cost allocation method should also be agreed with finance staff and reviewed by suitably qualified accounting professionals, since internal charging can have tax and reporting implications in some organizations.