CapEx vs. OpEx: What the Difference Is and Why It Shapes Technology Decisions

Key Takeaways

• CapEx buys assets that provide benefit beyond the current period; it is capitalized and depreciated or amortized. OpEx is expensed as incurred.
• Both cost cash. The difference is timing: when the expense hits the income statement, and which line of the cash flow statement shows the payment.
• OpEx reduces EBITDA immediately; CapEx does not, because depreciation sits below EBITDA. That alone can bias choices.
• Cloud subscriptions are generally OpEx, but implementation costs follow specific rules that differ between US GAAP and IFRS.
• The classification is decided by accounting standards and your organization's policy, applied by finance and auditors, not by the project.
• Compare options on economics first, and classification second. A capability-based business case keeps the two in the right order.

What Is the Difference Between CapEx and OpEx?

The core test is whether the spending creates something that keeps providing benefit beyond the current accounting period.

When an organization buys a delivery truck, it gets a vehicle it will use for years. Accounting treats the purchase as an asset on the balance sheet and spreads its cost over the truck's useful life through depreciation. That is capital expenditure. The fuel, the driver's wages and the insurance are consumed as the truck runs. They are expensed in the period they are incurred. That is operating expenditure.

Neither choice changes how much cash leaves the bank. What changes is when the cost appears in the income statement, where it appears in the cash flow statement, and which budget in most organizations pays for it.

How Do You Tell Whether a Cost Is CapEx or OpEx?

Finance makes the call, using the accounting standards the organization reports under and its own capitalization policy. Knowing the logic still helps anyone writing a business case.

Three questions do most of the work. Does the spending create or improve an asset the organization controls? Will that asset provide economic benefit beyond the current period? And is the amount above the organization's capitalization threshold, the minimum below which even long-lived items are simply expensed for practicality?

The distinction between maintaining and improving matters. Repainting a building or patching software keeps an asset working as it was, so it is generally OpEx. Adding a floor or building a substantial new feature extends what the asset can do, so it may be CapEx.

People costs are not automatically OpEx. Under both major frameworks, costs directly attributable to creating an asset, such as the time of engineers building internally developed software during its development phase, can be capitalized when the relevant criteria are met. The rules for property, plant and equipment sit in ASC 360 under US GAAP and IAS 16 under IFRS; intangible assets, including software, in ASC 350 and IAS 38. Leases are a further special case: under ASC 842 and IFRS 16, most leases put a right-of-use asset and a lease liability on the balance sheet.

Software, Cloud and SaaS: Where It Gets Complicated

Technology spending is where the CapEx and OpEx line is hardest to see, and where it has moved most in the last decade.

Software bought outright, with a perpetual license, is generally capitalized and amortized. Software built in-house for internal use follows a staged approach under US GAAP (ASC 350-40): costs in the preliminary project stage are expensed, costs in the application development stage can be capitalized, and costs after the software is in use, such as training and maintenance, are expensed. IFRS reaches a similar place through IAS 38's distinction between research, which is expensed, and development, which is capitalized when specific criteria are met.

Cloud services moved a large share of technology spending to the operating side. A subscription to software the provider hosts and controls is generally a service, so the fee is OpEx as it is incurred. The harder question is what to do with the money spent getting a cloud service working: configuration, integration, data migration and testing.

US GAAP and IFRS answer that differently. Under ASU 2018-15, a customer in a cloud arrangement that is a service contract applies the same staged internal-use software guidance to its implementation costs. Qualifying costs are capitalized and then expensed over the term of the arrangement, presented alongside the subscription fees. Under IFRS, an April 2021 IFRS Interpretations Committee agenda decision concluded that configuration and customization costs in a software-as-a-service arrangement are generally expensed, unless they create a separate intangible asset the customer controls, with judgment needed about when they are expensed.

The practical consequence for planners: the same cloud program can show a different profile of expense in two subsidiaries that report under different frameworks. Ask finance which treatment applies before modeling it.

Why the Split Matters Beyond Accounting

If both cost the same cash, why does anyone outside finance care? Because the split changes how options look and who gets to decide.

Reported profit. OpEx reduces operating profit and EBITDA in the year it is spent. CapEx reduces them only through depreciation, spread over years, and EBITDA not at all. Where executive targets or lender covenants are set on EBITDA or operating margin, a subscription can look worse than a purchase that costs the same, and a purchase can look better than it is.

Budgets and approvals. Many organizations run separate capital and operating budgets, with different owners, different approval thresholds and different annual timetables. A capital request may need an investment committee; an operating increase may need a budget-holder's sign-off within an annual envelope. The route of least resistance can decide which option is proposed in the first place.

Flexibility. A capital purchase commits the money up front; walking away later does not return it. A subscription can usually be reduced or ended at renewal, which has real value when demand is uncertain, and that value does not appear in either classification.

Cash timing. A purchase consumes cash early. A subscription spreads it out. For an organization that is short of cash, or one that has cheap capital, that difference matters more than the accounting line.

A Worked Example: Buying vs. Subscribing

An illustrative example with invented, round figures, chosen to make the mechanics visible. Real implementation costs may be classified differently, as described above.

A company needs a planning platform for five years. Option 1 buys it: a $500,000 purchase of licenses and hardware at the start of year 1, depreciated in equal amounts over five years, plus support of $40,000 a year. Option 2 subscribes: $130,000 a year, plus $60,000 of implementation work in year 1, which in this example is expensed as incurred.

Over the five years, the cash cost is almost identical: $700,000 to buy, $710,000 to subscribe. The total expense recognized over the whole period is the same as the cash in each case. What differs is timing and which numbers carry the cost. In year 1, buying uses far more cash, but subscribing reduces operating profit more, and it reduces EBITDA by $150,000 more. Across the five years, buying never reduces EBITDA by more than its support fees, because the purchase reaches the income statement only as depreciation, below the EBITDA line.

Neither option is better from this table alone. The choice should rest on what the table leaves out: how long the platform will really be needed, how much flexibility is worth, which option better supports the capability the business is trying to improve, and the cost of capital, which a discounted business case would include.

CapEx and OpEx Through a Business Architecture Lens

Business architecture does not decide how a cost is classified. It makes sure the classification does not decide what the organization invests in.

Start from the capability, not the budget line. A capability-based investment plan asks which business capabilities the strategy needs improved, by how much, and what the realistic options for improving each one are: build, buy, subscribe, partner or change the process. Only then does it ask how each option would be classified and funded. Done in that order, the capital and operating budgets become constraints to manage rather than criteria for choosing.

Separate running the business from changing it. Many organizations already track spending on keeping current capabilities running separately from spending on changing them. Mapping both to capabilities shows which capabilities absorb most of the run cost, which are being invested in, and where the run cost of a recently changed capability did not fall as the business case promised.

Count the whole cost of a capability. Moving a capability's supporting systems to the cloud shifts cost from depreciation to subscription, but it can also shift effort from an infrastructure team to vendor management, and from upgrades to continuous change. A capability-level view of total cost of ownership catches costs that move between budgets rather than disappearing.

Make the business case neutral. Compare options on discounted cash flows and on how far each moves the capabilities that matter; show the CapEx and OpEx profile of each so finance can plan; and say explicitly if a budget constraint is driving the recommendation.

Tools and further reading

• Business Case Builder (free) — Tag each cost as capital or operating, and compare options on NPV and payback regardless of budget line.
• Business case: how to write one — Options, costs, benefits and risks, compared fairly.
• Make vs. buy vs. partner — Choosing how to deliver a capability before deciding how to fund it.
• ERP system — One of the largest technology investments, and a common CapEx versus OpEx decision.

Common Mistakes

Most problems come from treating the classification as a property of the option, rather than a consequence of it.

• Choosing by budget line. Picking the option that fits whichever budget has room, without comparing the options on their merits.
• Comparing EBITDA instead of cash. A purchase can flatter EBITDA for years while costing more over its life once the cost of capital is included.
• Assuming cloud means no capital cost. Implementation, data migration and integration can be substantial, and their treatment depends on the reporting framework.
• Assuming people are always OpEx. Qualifying development work can be capitalized; leaving it out understates the asset and overstates the expense.
• Forgetting the exit. A purchased asset may have years of depreciation left when the business no longer needs it; a subscription may carry a notice period or minimum term.
• Classifying without finance. Business cases that guess the treatment are corrected later, and the corrected numbers can change which option wins.

Frequently Asked Questions

What is the difference between CapEx and OpEx?

CapEx is spending on assets that provide benefit over several periods, such as equipment or owned software; it is recorded as an asset and depreciated or amortized over time. OpEx is the cost of running the business, such as salaries, rent and subscriptions, and is expensed in the period it is incurred.

Is SaaS CapEx or OpEx?

SaaS subscription fees are generally OpEx, because the customer is paying for a service rather than acquiring an asset it controls. Implementation costs are treated differently under US GAAP, where qualifying costs can be capitalized and expensed over the contract term, and IFRS, where configuration and customization costs are generally expensed unless they create an asset the customer controls.

Are salaries CapEx or OpEx?

Usually OpEx. But the portion of salaries directly attributable to building an asset, such as engineers developing internal-use software during its development phase, can be capitalized when the relevant accounting criteria are met.

Which is better, CapEx or OpEx?

Neither. CapEx commits cash up front and spreads the expense over time; OpEx spreads cash and expense together and usually offers more flexibility. The better option is the one with better economics and a better fit for the capability being improved; the classification follows from the choice.

How does CapEx vs. OpEx affect EBITDA?

OpEx reduces EBITDA in full in the period it is incurred. CapEx does not reduce EBITDA directly, because the related depreciation and amortization are excluded from it. That is why moving from purchased systems to subscriptions can reduce EBITDA even when total cost stays the same.

What are examples of CapEx and OpEx?

CapEx: buildings, machinery, vehicles, servers, perpetual software licenses and qualifying software development. OpEx: salaries, rent, utilities, maintenance and support, cloud and SaaS subscriptions, training and travel.

Who decides whether a cost is CapEx or OpEx?

The finance function, applying the accounting framework the organization reports under and its own capitalization policy, with auditors reviewing the result. A project team can explain the facts of an arrangement, but should not choose its classification.

Why does the cloud shift spending from CapEx to OpEx?

Because instead of buying and owning servers and licenses, which are assets, the organization pays a provider for a service as it uses it, which is an operating expense.

Pro Tips

• Show every option's CapEx and OpEx profile by year in the business case, alongside its NPV, so finance can plan funding without the profile deciding the choice.
• Ask finance for the capitalization threshold and the useful lives it uses for software and hardware before modeling depreciation.
• For cloud programs, ask finance which implementation costs will be capitalized under your reporting framework; it can change year 1 materially.
• When a recommendation depends on which budget has room, say so in the business case. Hidden budget constraints produce choices nobody can explain later.
• Track run and change spending by business capability. It shows where a cloud move really reduced cost and where it only moved it.