TBM, ITFM or FP&A: who should own IT cost?

In brief

ITFM is the function, TBM the method, FP&A the enterprise planning team. How their remits differ, where they collide, and our view on who should own IT cost.

Steve Elliott

Steve Elliott · · 6 min read


On this page
  1. How do TBM, ITFM and FP&A differ?
  2. What does each typically own?
  3. Where do TBM, ITFM and FP&A collide?
  4. Where should IT finance report?
  5. Who should own IT cost? Our view
  6. Sources

In our view, none of the three should own all of IT cost. FP&A should own the enterprise's number for IT, the ITFM function should own the model and the explanation behind that number, and TBM is the method ITFM uses to build the model, not a rival owner.

The confusion is understandable. All three touch budgets, forecasts and variance, and the bodies that describe them draw the lines differently. When the split is left unsettled, it can show up as two IT forecasts in the same meeting.

How do TBM, ITFM and FP&A differ?

The short version: ITFM is a discipline and, in most large companies, a team. TBM is a framework and taxonomy that sits inside or beside it. FP&A is the enterprise's planning function, and IT is one of many areas it covers.

ITFMTBMFP&A
What it isDiscipline and function for IT budgeting, forecasting, costing and cost recoveryFramework, taxonomy and practices for measuring the cost and value of technologyEnterprise function for planning, budgeting, forecasting and financial analysis
ScopeTechnology spendTechnology spend, modeled through to the consumers who use itThe whole enterprise; IT is one cost area
Who describes itGartner and the FinOps Foundation, among othersTBM CouncilAFP, which runs the FP&A certification
Typical homeIT finance, in the CFO's or the CIO's organizationA TBM office, IT finance, a PMO or a value management officeOffice of the CFO
Signature outputIT budget, IT forecast, chargebackCost model by cost pool, tower, solution and consumerAnnual operating plan, rolling forecast, board reporting

TBM. The TBM Council defines TBM as "a strategic discipline for managing the value of technology across the enterprise." Its framework rests on five foundations: data, tools, methods, roles and change leadership. Its taxonomy organizes technology spend, resources and services across every layer of the enterprise. The Council lists ITFM as a related practice for budgeting, forecasting and planning, and says TBM elevates it by applying the taxonomy and framework.

ITFM. The FinOps Foundation's guidance on how the disciplines intersect puts it plainly: "TBM is an IT Financial Management (ITFM) discipline." Its 2026 framework lists ITFM among disciplines that are adjacent to and increasingly converged with FinOps, and describes ITFM as focused on the financial structures that account for how technology investment is reported and charged back to the general ledger. Gartner's market definition of ITFM software names budgeting, forecasting, cost allocation, investment analysis and value realization.

FP&A. The Association for Financial Professionals defines FP&A as "the function within the Office of the CFO that supports strategic decision-making." It does that through integrated planning, budgeting and forecasting, performance management and financial analysis. AFP's certification site says that in corporate FP&A, professionals typically report to the CFO and work alongside accounting and treasury.

Read together, the definitions imply a rough nesting. FP&A plans the enterprise. ITFM plans and accounts for technology inside that plan. TBM gives ITFM a standard model. The bodies differ on emphasis: the TBM Council presents TBM as the strategic frame that lifts ITFM, while the FinOps Foundation files TBM under ITFM.

What does each typically own?

The split below is our description of a common pattern, not a standard. Real organizations vary.

WorkFP&AITFMWhere TBM fits
IT budgetSets IT's envelope inside the annual operating planBuilds the bottom-up detail by cost center, vendor, project and headcountCost pools give the budget a standard structure
ForecastCarries IT as a line in the enterprise forecastForecasts IT monthly from contracts, renewals, projects and hiringLittle direct role
Cost modelRarely builds oneBuilds and maintains itThe taxonomy defines its layers
AllocationsAllocates corporate overhead to business unitsAllocates IT cost to services and consumersTowers, solutions and cost drivers
Chargeback and showbackSigns off on the effect on business unit P&LsSets rates and produces the bill of ITThe consumer layer
VarianceExplains IT's variance to the enterpriseExplains the drivers behind itShows which towers and services moved

In most companies we'd expect capitalization to sit with the controller and accounting rather than FP&A, with ITFM supplying the project and labor data. Changes such as ASU 2025-06 affect the data it has to collect. Confirm capitalization treatment with your auditors.

Where do TBM, ITFM and FP&A collide?

In our view, four places cause most of the friction.

  • Two forecasts. Take an illustrative company whose FP&A team forecasts IT at $180 million for the year, from run rate and the plan. ITFM's bottom-up forecast, built from contracts, renewals and open roles, says $186 million. Both are defensible. If the CFO sees both, the $6 million gap becomes the meeting.
  • Two allocations. FP&A often allocates IT to business units as corporate overhead, by revenue or headcount. ITFM charges back by consumption. If both run without a rule for which one wins, business units can see two different costs for the same IT services, or pay for some twice.
  • Two structures. FP&A's view follows the chart of accounts and cost centers. A TBM model follows cost pools, towers and solutions. Without a maintained mapping between them, the totals stop reconciling and each side questions the other's numbers.
  • A fourth voice in planning. The FinOps Framework 2026 added an Executive Strategy Alignment capability. Its multi-year investment strategy area uses FinOps cost and usage data, together with IT finance data, to support enterprise budgeting, P&L ownership and governance of long-term vendor commitments. In our view that brings FinOps into planning work FP&A and ITFM already do, which needs agreed decision rights. We cover that overlap in TBM vs FinOps.

Where should IT finance report?

Three reporting lines are common. In our view, each fits a different situation.

  1. In central finance, under the CFO. ITFM sits within FP&A or the controller's group. This fits when the priority is cost control and finance credibility, when most IT spend is run cost, and when central planning is strong. The risk is distance from engineering and portfolio decisions, so the cost model becomes a reporting exercise.
  2. In the CIO's organization. ITFM reports to the CIO or a technology CFO. This fits when technology spend is large, funded by product or value stream, and decisions move fast. The TBM Council, discussing where to place a TBM program, notes that putting it in IT finance or the CIO organization gives immediate access to cost data but may reinforce IT-centric perceptions without finance and business collaboration.
  3. Hybrid, with a finance business partner. The IT finance lead reports on a solid line to the CFO's organization and sits on the CIO's leadership team as a finance business partner. In our view this fits most large enterprises with a material IT budget. The risk is two bosses with different priorities, so it works only when each line's decision rights are written down.

The TBM Council's adoption guidance lists the locations organizations typically choose for a TBM program: a dedicated TBM office, a value management office, IT finance or the CIO organization, an enterprise PMO or planning office, or a data or analytics office. It does not list central FP&A as a separate option. It names the CFO, alongside the CIO and COO, as a common executive sponsor, and recommends a steering committee of senior leaders from IT, finance and the business. The Council adds that success depends on cross-functional visibility wherever the program sits.

Who should own IT cost? Our view

This section is our view, not a finding from any of the sources above.

FP&A owns the number. IT's envelope in the annual plan and IT's line in the enterprise forecast belong to FP&A, because FP&A answers for the whole P&L and has to trade IT off against everything else.

ITFM owns everything beneath it. The cost model, allocations to services, chargeback rates, the bottom-up forecast and the explanation of variance belong to ITFM. ITFM's forecast should be the input to FP&A's IT line, not a competitor to it. One forecast, two levels of detail.

TBM is the method, not an owner. Where a TBM office exists, we think it works best as part of ITFM, so the model and the people accountable for the IT budget are the same team. The TBM Council argues that a dedicated office signals executive commitment and cross-functional neutrality. We think keeping the model with the people accountable for the IT budget matters more.

Report hybrid, with the solid line to finance. A chargeback rate is an internal price. In our view the person who sets it should not report only to the organization that collects it, and keeping ITFM in the CFO's chain means the reconciliation to FP&A happens inside one line of authority. The dotted line to the CIO keeps the model close to the portfolio and sourcing decisions it is meant to inform.

We would move ITFM into the CIO's organization where technology is run as product lines with their own P&Ls, and fold it into central FP&A where IT is small and mostly run cost.

A simple test tells you whether ownership is settled. Ask FP&A and ITFM for last month's IT actuals and this year's IT forecast. If the totals differ, someone still has to decide who owns the number.

That test is really about the operating model: cost, plan and funding decisions should reason from the same figures, whichever team holds the pen.

Sources

Frequently asked questions

Is TBM the same as ITFM?

No. ITFM is the function that budgets, forecasts and accounts for technology spend. TBM is a framework and taxonomy, stewarded by the TBM Council, that gives ITFM a standard cost model. The two bodies frame the relationship differently: the FinOps Foundation calls TBM an ITFM discipline, while the TBM Council describes TBM as elevating ITFM.

Should IT finance report to the CFO or the CIO?

It depends on how technology is funded. In our view a hybrid works best for most large enterprises: a solid line to the CFO's organization and a seat on the CIO's leadership team as a finance business partner. We think a CIO reporting line suits product-funded technology with its own P&Ls, and central finance suits small, mostly run-cost IT.

Does FP&A own the IT budget?

Often FP&A sets IT's envelope in the annual operating plan and carries IT as a line in the enterprise forecast, while ITFM builds the detail underneath, by vendor, project, headcount and service. In our view FP&A should own the top-line number and use ITFM's bottom-up forecast as its input, so there is only one IT forecast.

Who should own IT chargeback?

In our view ITFM should set chargeback rates and produce the bill of IT, because it owns the cost model and the cost drivers behind them. FP&A should approve how charges land on business unit P&Ls and make sure they replace, rather than add to, any corporate overhead allocation of IT cost.

Free playbooks

In-depth guides for product and operations leaders.

Browse the playbooks
Steve Elliott

Steve Elliott

Published November 22, 2026

More on TBM & IT Financial Management

Cost pools, towers, showback, unit cost.