IT Service Financial Management and Performance Measurement
What this domain tests
Financial management of IT services - budgeting, accounting and charging - plus the performance measurement system that shows whether services deliver value. Items ask you to compute unit cost, choose an appraisal method, or pick the right performance perspective.
Core rules
- Three activities: budgeting (plan and control money), accounting (record what was spent and on what), charging (recover cost from consumers). Charging is optional; accounting is not.
- Cost classifications: direct versus indirect, fixed versus variable, capital versus operating expenditure. Total cost of ownership spans acquisition, operation, change and disposal.
- Appraisal methods: payback (time to recover), NPV (absolute value, discounted), IRR (rate of return). NPV is preferred when comparing investments of different sizes.
- Unit cost = total cost of a service ÷ volume of transactions. It is the basis for benchmarking, tariffs and improvement targets.
- Showback informs consumers of their consumption; chargeback actually bills them. Chargeback changes behaviour but adds administration and dispute handling.
- Performance: Balanced Scorecard perspectives (financial, customer, internal process, learning and growth), CSF/KPI trees, and external benchmarking.
Worked example
A service desk costs 3.6m per year (staff 2.4m, tooling 0.4m, overhead 0.8m) and handles 90,000 tickets. Unit cost = 40 per ticket. Automating password resets removes 18,000 tickets and 0.36m of staff time but adds 0.15m of tooling: new cost 3.39m ÷ 72,000 = 47.08 per ticket. Total spend fell while unit cost rose - so report both figures, and present the avoided headcount as the benefit in the business case rather than claiming a unit-cost saving.
Traps that cost marks
- Quoting total spend as unit cost, or forgetting to re-base volume after automation.
- Including sunk costs in the decision, or ignoring opportunity cost.
- Assuming chargeback is mandatory under ITIL or ISO/IEC 20000.
- Judging performance on availability alone while ignoring cost per transaction and satisfaction.
- Introducing charging without a prior showback cycle, then facing billing disputes.
Design choices
Publish the charging model one cycle before billing starts, keep it simple (per user, per transaction, tiered), reconcile it to the budget, and review tariffs annually alongside the service catalogue so prices and service definitions never diverge.