TBM Cost Pools

Cost Pools and Sub Cost Pools represent the finance view of technology spend in the TBM model.

Use Cost Pools to classify what the organization pays for before that spend is allocated into towers, solutions, and consumers. This gives Finance, IT, FinOps, and business stakeholders a consistent starting point for cost transparency and accountability.

Cost Pools help turn raw financial data into a governed technology cost structure.

What Cost Pools help you do

Use Cost Pools to:

• Categorize technology spend by financial cost type

• Separate operating and capital spend where required

• Standardize spend classification across accounts, vendors, and cost centers

• Prepare spend for downstream tower and solution allocation

• Improve cost transparency reporting

• Support showback, chargeback, planning, forecasting, and analytics

• Identify spend that is not mapped or requires finance review

Cost Pools are the first major TBM layer. Accurate classification here improves every downstream view.

How Cost Pools fit the TBM model

Cost Pools sit at the finance foundation of the TBM model.

They answer the question: What type of technology cost is this?

The typical flow is:

1. Financial data is loaded from source systems

2. Spend is mapped to Cost Pools and Sub Cost Pools

3. Cost Pool spend is allocated into Towers and Sub Towers

4. Tower spend is connected to Solutions and Consumers where the model supports it

5. The results become available in Cost Transparency, Analytics, showback, chargeback, and planning workflows

This structure helps teams move from accounting data to technology and business views of spend.

Cost Pool structure

Cost Pools are organized into two levels.

Sub Cost Pools give teams more precision while preserving the higher-level cost structure needed for reporting and allocation.

Operating expense Cost Pools

Operating expense categories represent technology costs that are usually expensed during the current financial period.

Common OPEX Cost Pools include:

Use the most specific category available before defaulting spend to Other.

Capital expense Cost Pools

Capital expense categories represent technology costs that are capitalized and recognized over time according to finance policy.

Common CAPEX Cost Pools include:

Capitalization treatment depends on the organization's finance policy. Yarken uses the Cost Pool structure to support reporting once that financial classification is available.

Cost Pools and Sub Cost Pools

Sub Cost Pools provide the detail needed for accurate reporting and allocation.

Examples include:

• Internal employee wages, benefits, and expenses

• External contractor fees and related expenses

• Managed services and external consulting

• Public cloud provider services

• Software licenses, maintenance, and support

• Data center space, power, and co-location

• Voice, data network, and mobile charges

Use Sub Cost Pools to preserve finance detail while keeping reporting consistent at the Cost Pool level.

Relationship with Towers

Cost Pools explain what was purchased or paid for.

Towers explain which technology function the spend supports.

For example:

• Software spend may support Application, Platform, Security, or End User towers

• Outside Services may support Delivery, Compute, Network, or IT Management towers

• Facilities & Power may support Data Center towers

• Telecom may support Network or End User services

This relationship helps teams move from financial classification into technology service delivery views.

Relationship with Cost Transparency and Cost Explorer

Cost Pools are visible across Cost Transparency dashboards and Cost Explorer.

Use Cost Transparency to review Cost Pool spend, variance, and trends.

Use Cost Explorer to validate how Cost Pool spend flows into downstream TBM layers and to identify spend that remains unmapped or partially allocated.

Recommended practices

Use these practices when working with Cost Pools:

• Map spend to the most accurate Cost Pool and Sub Cost Pool available

• Keep OPEX and CAPEX treatment aligned with finance policy

• Use Other only when no better classification exists

• Review large unmapped or miscellaneous balances regularly

• Validate Cost Pool mapping before reviewing downstream Tower or Solution reports

• Keep mapping rules consistent across periods

• Coordinate classification decisions with Finance and TBM owners

• Use Cost Explorer to confirm allocation outcomes

Good Cost Pool discipline improves trust in the full TBM model.

Common use cases

Cost Pools are commonly used for:

• Finance view of IT spend

• Cost transparency reporting

• Month-end classification review

• Allocation into Towers

• OPEX and CAPEX reporting

• Budget and forecast analysis

• Showback and chargeback preparation

• Executive reporting on technology cost structure

Troubleshooting Cost Pool results

If Cost Pool results do not look correct, check:

• Whether source financial data has been loaded for the selected period

• Whether account, vendor, or cost center mappings are complete

• Whether spend has been assigned to the correct Cost Pool and Sub Cost Pool

• Whether OPEX and CAPEX values are classified correctly

• Whether large balances are sitting in Other or unmapped categories

• Whether downstream Tower allocations depend on incomplete Cost Pool mapping

If totals still do not match expectations, compare Cost Pool reporting against source spend and allocation rules.

Next step

• TBM Towers

Related content

• Technology Business Management

• TBM Taxonomy

• Cost Transparency Overview

• Cost Pool Spend

• Cost Explorer