Cost center or product P&L: where technology cost should land
In brief
Should technology run as a cost center, a shared-services recharge or inside product P&Ls? What each model does to behavior, plus a worked margin example.
Steve Elliott · · 7 min read
On this page
- What are the three ways to account for technology?
- What does each model do to behavior?
- Which technology costs belong in a product P&L?
- What does finance need to make the attribution credible?
- Illustrative example: one product's margin with and without technology
- Is product technology cost the same as COGS?
- Where should you start?
- Sources
In our view, the technology that runs a digital product belongs in that product's P&L, and enterprise-wide technology belongs in a cost center that is shown back, not charged. Full shared-services recovery, where IT bills out every dollar to break even, tends to start arguments about rates rather than decisions about products.
The choice changes who answers for technology spend and what margin leaders see. It is also separate from where costs sit in your published income statement. A management P&L and the cost of revenue line in your financial statements answer different questions, and mixing them up causes confusion.
What are the three ways to account for technology?
OpenStax's managerial accounting text gives the vocabulary. In a cost center, a manager answers only for costs. In a profit center, the manager answers for revenues and costs. In an investment center, the manager also answers for the capital the segment uses.
Technology organizations usually run one of three models, or a mix. The failure modes in the table are our reading:
| Cost center | Shared-services recovery | Product P&L attribution | |
|---|---|---|---|
| Who answers for technology cost | The CIO, against budget | The CIO, against a break-even target | Product or business-unit owners, for what they consume |
| What business leaders see | Nothing, or a showback report | An internal bill at a rate | Technology cost inside product margin |
| What it rewards | Spending less than budget | Recovering every dollar | Margin per product |
| Typical failure | Technology looks free to consumers | Disputes over rates and drivers | Owners charged for costs they can't change |
| What finance needs | A budget and variance reporting | A service catalog, rates and true-ups | Products in the cost model, tested drivers, consumption data |
Payroll systems and the corporate network rarely belong in a product's margin. A customer-facing app's cloud bill usually does.
What does each model do to behavior?
Cost center. ACCA's performance management examiners note that cost center performance is commonly measured through variance analysis, which focuses on short-term cost minimization and may conflict with quality or delivery time. We'd add that consumers see no price, so demand has no brake except the CIO's budget.
Shared-services recovery. Charging business units a rate gives demand a price, which is the case for chargeback over showback. The trouble is the break-even target. Much of a shared service's cost is fixed in the short run. When one consumer cuts usage, the rate for everyone else rises, and the finance team can spend the year defending rates instead of discussing what to buy.
Product P&L attribution. The product owner sees technology as part of what it costs to serve customers, and can trade it against price, features and volume. It only works if the owner can influence what lands in the P&L. ACCA states the controllability principle plainly: when judging a manager, "we should only consider costs and revenues under the control of that manager." Its example is depreciation on divisional machinery, which a profit center manager can't control because they don't control the investment.
For technology, if a product owner's P&L carries amortization of software they never decided to build, or a security allocation they can't change, the number is traceable to the product but not controllable by its owner. ACCA's article makes the same split: divisional depreciation is left out of controllable profit but included as a traceable cost of the division. We think the product P&L should show both, labeled separately.
Which technology costs belong in a product P&L?
We use three tests:
- Does the customer consume it as part of the product? Hosting, the product's own software and the support that keeps it running pass. The finance system does not.
- Is there a driver that measures consumption? Tagged cloud spend, tickets and time do. A headcount split for a product with no staff does not.
- Can the owner change it? If not, show it below a controllable margin line rather than inside it.
Costs that pass all three go into product margin. Costs that pass the first two but not the third sit below it. Everything else stays in the cost center and is shown back by business unit.
What does finance need to make the attribution credible?
Expect product owners to challenge the number the first time it cuts their margin. Credibility comes from the cost model, not the presentation.
- Products in the model. TBM Taxonomy 5.0 renamed the Business layer the Consumer layer and added value streams, products, portfolios and digital services, according to the TBM Council's migration guide. Legacy business-unit mappings move to business unit, product or value stream. Without that layer, product P&L attribution is a spreadsheet exercise outside the cost model.
- No shortcuts. The guide says "no rules skip layers," so cost moves from cost pools through towers and solutions to consumers. Exceptions, such as shared services, should be rare, documented and justified. A cost that jumps straight from the ledger to a product is the one an owner is most likely to dispute.
- Drivers based on consumption. The TBM Council lists weak cost drivers and "50/50" flat splits among the causes of low-quality data. At the Consumer layer it suggests transparent drivers such as headcount, device counts, tickets or cloud consumption.
- A coverage measure. The Council recommends measuring the share of total IT spend fully mapped to consumers. Publish it next to the product margins so owners know how much of the total they are seeing.
Illustrative example: one product's margin with and without technology
The numbers below are made up. Take a subscription product with $40 million in annual revenue and 500,000 subscribers. Today technology sits in a central cost center, and the product P&L shows only non-technology delivery costs: payment processing, licensed content and customer service agents.
| $ millions | Technology in a cost center | Technology attributed |
|---|---|---|
| Revenue | 40.0 | 40.0 |
| Non-technology delivery costs | (12.0) | (12.0) |
| Cloud hosting (tagged to the product) | n/a | (4.4) |
| Application support and site reliability (tickets and time) | n/a | (2.1) |
| Amortization of capitalized product software | n/a | (3.0) |
| Product margin before shared allocations | 28.0 (70.0%) | 18.5 (46.3%) |
| Shared services: identity, network, security (by driver) | n/a | (1.5) |
| Product margin after technology | 28.0 (70.0%) | 17.0 (42.5%) |
First, the product's margin falls from 70% to 42.5%. A pricing or promotion decision made on the first number would rest on a margin the product doesn't earn. Second, technology works out to $22 per subscriber a year, and if the $4.4 million in hosting grows with subscribers, as we assume here, it behaves as a variable cost, not part of central overhead. Third, $4.4 million is tagged directly, $5.1 million is traced by tickets, time and build decisions, and only $1.5 million is an allocation of shared costs. That last line is where any argument with the product owner should be.
The amortization line raises the controllability question. If the product owner approved the build, that $3.0 million belongs in their margin, and the product starts to look like an investment center. If a central portfolio board made the call, we would show it below a controllable margin line.
Is product technology cost the same as COGS?
No. Product margin in a management P&L is an internal construct. Cost of goods sold, or cost of revenue, is an external reporting classification governed by GAAP and, for SEC registrants, Regulation S-X. The two can overlap, but one doesn't decide the other.
What the sources say:
- Regulation S-X asks registrants to state costs applicable to revenues separately, including cost of tangible goods sold and cost of services.
- For example, Okta puts hosting and support in cost of revenue. Its fiscal 2026 10-K says cost of subscription revenue mainly covers hosting its services and providing support, and also includes amortization of capitalized internal-use software. Okta also allocates certain IT, security and facilities costs to all departments by headcount, so shared costs appear in both cost of revenue and operating expense.
- Software to be sold. ASC 985-20 says amortization of capitalized software production costs is "charged to cost of sales or a similar expense category," as quoted in KPMG's February 2026 handbook.
- Cloud implementation costs. Under ASC 350-40, amortization of capitalized implementation costs for a hosting arrangement goes in the same income statement line as the hosting fees, per the same KPMG handbook.
- Internal-use software gets little line-item direction. KPMG notes that ASC 350-40 doesn't prescribe financial statement presentation, and that practice varies on whether the expense is shown as depreciation or amortization. BDO adds that where the standards are silent, general presentation principles apply.
- If depreciation and amortization are excluded from cost of sales, SEC Staff Accounting Bulletin Topic 11.B says the caption should say so, for example "exclusive of depreciation shown separately below."
The timing of capitalization is changing too, which moves cost between opex and amortization. Our post on ASU 2025-06 covers that. These are classification questions for your controller, not choices for the cost model. Confirm how they apply to you with your accounting advisers and auditor.
Where should you start?
- Pick one digital product whose revenue is reported and whose owner can change consumption.
- Tag its hosting and support costs, and name the capitalized software it amortizes.
- Map it in the Consumer layer and route its costs through towers and solutions.
- Show its margin both ways, with controllable and allocated technology on separate lines.
- Agree with the controller how the management view reconciles to cost of revenue.
In our view, this is where an operating model earns its keep: when a product's funding decision, its technology consumption and its margin sit in one view, the owner can see what the product costs to run before deciding to grow it.
Sources
- TBM Council, Update Your TBM Model with a New Taxonomy Version, July 16, 2025, updated September 4, 2025
- TBM Council, Technology Business Management (TBM) Taxonomy, version 5.0.1 released July 18, 2025
- TBM Council, Addressing Model Fallout and Data Quality at All Levels of the TBM Model, August 20, 2025, updated April 2, 2026
- Franklin, Graybeal and Cooper, Principles of Accounting, Volume 2: Managerial Accounting, OpenStax, 9.3 Describe the Types of Responsibility Centers, February 14, 2019
- ACCA, Decentralisation and the need for performance measurement, Performance Management examining team
- US Code of Federal Regulations, 17 CFR 210.5-03, Income statements (Regulation S-X)
- SEC, Staff Accounting Bulletin Topic 11: Miscellaneous Disclosure, Topic 11.B
- KPMG, Software and website costs Handbook: US GAAP, February 2026
- BDO, Accounting for Software Costs, July 16, 2026
- Okta, Inc., Form 10-K for the fiscal year ended January 31, 2026
Frequently asked questions
Should IT be a cost center or a profit center?
In our view, mostly neither in pure form. Technology that runs a digital product belongs in that product's P&L, judged on margin. Enterprise-wide technology, such as finance systems and the corporate network, fits a cost center shown back to business units. Running all of IT as a break-even recharge tends to shift attention from product decisions to internal rate disputes.
What is the difference between product margin and gross margin?
Product margin is a management view: it can include any cost finance chooses to attribute, including allocated shared services. Gross margin in published statements follows GAAP and, for SEC registrants, Regulation S-X, which requires cost of tangible goods sold and cost of services to be stated separately. The two can overlap, for example for hosting and support, but are built for different readers and needn't match.
Where does capitalized software amortization go in a product P&L?
In our view, it belongs in the product's P&L if the product owner decided to build the software, since the investment is then theirs to answer for. If a central board decided, show it below a controllable margin line. For external reporting, a separate question, ASC 985-20 places amortization of software to be sold in cost of sales or a similar category.
What does the TBM Consumer layer add for product costing?
According to the TBM Council's migration guide for Taxonomy 5.0, the Business layer was renamed the Consumer layer and now includes value streams, products, portfolios and digital services. The TBM Council says costs should pass through cost pools, towers and solutions before reaching consumers, using consumption-based drivers, with the share of IT spend mapped to consumers measured and reported.
Steve Elliott
Published November 22, 2026
More on TBM & IT Financial Management
Cost pools, towers, showback, unit cost.
Keep reading
TBM in health systems: technology cost on margins this thin
About 43% of hospitals in Kaufman Hall's sample run at a loss. How TBM helps health systems cost the EHR, defend cyber spend and price IT into service lines.
TBM, ITFM or FP&A: who should own IT cost?
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.
TBM vs FinOps: where one ends and the other begins
TBM models the full cost of technology from the ledger; FinOps brings usage data and accountability to spend as it happens. How they differ and overlap now.
Why IT cost transparency projects stall
Many IT cost transparency projects don't fail outright. They publish a model and little changes. Why that happens, and how to restart around one decision.