Managing an IT Department Budget: Capex, Opex and Cloud Costs

Running an IT department means owning a budget whose rules you did not write. Finance decides what counts as a capital purchase, how it is depreciated, and when a cost shows up on the income statement. Yet those rules shape what gets approved, when, and how your spending looks to the CFO.

You do not need to become an accountant. You do need to understand the basics well enough to plan sensibly, avoid year-end surprises and speak your finance partners' language. This guide covers capital versus operating spending, how cloud subscriptions and software projects are treated, and a practical way to build and run the budget.

One caution up front: this is general background, not accounting or tax advice. Your organization's capitalization policy and your controller's judgment govern how any specific cost is treated.

Capex and opex in plain language

Capital expenditure (capex) is spending on something that will provide value for more than a year, such as servers, network gear or a major software build. It is recorded as an asset and expensed gradually through depreciation (for physical assets) or amortization (for intangible ones such as software). Operating expenditure (opex) is expensed in the period it is incurred: salaries, support contracts, most subscriptions, repairs.

The IRS's depreciation guide, Publication 946, reflects the same idea for tax purposes: "You can depreciate most types of tangible property (except land)," and the property must be "expected to last more than 1 year."

Why it matters to you:

• Many organizations approve capital and operating budgets through different processes and calendars.
• A large capital purchase spreads its expense over several years, while the same amount in subscriptions hits this year's operating results.
• Moving from owned hardware to cloud services often shifts spending from capex to opex, which changes how your budget looks even if total cost is similar.

Thresholds: your policy versus the tax rules

Most organizations set a capitalization threshold, a dollar amount below which items are simply expensed. That internal policy can differ from tax rules, and book and tax treatment can diverge.

On the tax side, the IRS de minimis safe harbor lets businesses that elect it deduct items costing up to $2,500 per invoice or item, or up to $5,000 if they have an applicable financial statement (such as audited financials). The election is made each year with the tax return. Publication 946 also says that when computer software can be depreciated, it uses "the straight line method over a useful life of 36 months," and that the maximum section 179 expense deduction for tax years beginning in 2026 is $2,560,000, reduced when qualifying purchases exceed $4,090,000. Those are finance's decisions, but knowing they exist helps you ask the right questions about timing.

Cloud and SaaS: subscriptions and implementation costs

Under US accounting standards (GAAP), FASB's Accounting Standards Update 2018-15 summarizes the treatment of cloud arrangements: if a cloud computing arrangement does not include a software license, it is a service contract, which "generally means that the fees associated with the hosting element (service) of the arrangement are expensed as incurred."

Implementation costs are different. ASU 2018-15 aligned them with the rules for internal-use software, so some setup costs for a cloud service can be capitalized and then expensed over the term of the arrangement. Costs such as training and certain data conversion costs cannot be capitalized.

Organizations reporting under IFRS face a different answer. In a 2021 agenda decision, the IFRS Interpretations Committee observed that a customer in a software as a service arrangement "often would not recognise an intangible asset" for configuration or customization, because it does not control the software being configured.

The practical lesson: before a large SaaS rollout, sit down with finance, agree how costs will be classified, and track implementation spending by activity (configuration, data migration, training) so it can be treated correctly.

Internal software development is changing

If your team builds software for internal use, a new standard affects you. ASU 2025-06, issued in September 2025, removes the old "project stages" from US GAAP's internal-use software rules. Capitalization starts when management "has authorized and committed to funding the software project" and it is "probable that the project will be completed and the software will be used to perform the function intended." Entities must consider whether there is "significant development uncertainty," for example from novel or unproven features.

The amendments are effective for annual reporting periods beginning after December 15, 2027, with early adoption permitted. For your team, the takeaway is that documentation matters: funding approvals, requirements and how uncertainty was resolved may all affect what can be capitalized.

Building the budget: start from inventories

A credible IT budget is built from facts you can show, not last year's number plus a percentage.

1. Contracts: list every recurring contract with its cost, term, renewal date and expected price change at renewal.
2. Assets: list hardware and major software with purchase dates and planned replacement cycles.
3. People: salaries, benefits, planned hires, contractors and training.
4. Projects: new initiatives, each with a short business case and an estimate of one-time and ongoing costs.
5. Contingency: a modest, explicit reserve for unplanned needs, agreed with finance rather than hidden in other lines.

Many leaders group the result into "run" (keeping current services going) and "change" (improvements and new capabilities), which makes trade-off conversations clearer.

Watch for refresh waves. For example, imagine a company that bought 200 laptops in a single year. If it never staggered replacements, it will face one large refresh bill every few years instead of a steady annual amount. Spreading replacements evens out both the budget and the workload.

Running the budget during the year

• Review actual spending against budget with finance every month, and explain variances before anyone asks.
• Keep a rolling forecast for the rest of the year so surprises surface early.
• Check license usage before renewals and remove unused seats.
• Track cloud consumption and set alerts, since usage-based costs can grow quietly.
• When priorities change mid-year, document the trade-off: what you are funding instead and what is being deferred.

Talking about money with finance

Finance leaders respond to options, total cost and timing. Present multi-year total cost of ownership, not just the first-year price. Show how a proposal affects capex, opex and cash. Offer two or three options with clear consequences rather than a single take-it-or-leave-it request. And invite finance into planning early; a controller who helped shape the budget will defend it with you.

Key takeaways

• Capex is spread over the asset's useful life; opex hits the period it is spent. Your organization's policy decides the line.
• Cloud subscriptions are generally expensed, but some implementation costs may be capitalized under US GAAP; agree treatment before big rollouts.
• ASU 2025-06 changes when internal-use software costs can be capitalized, effective for annual periods beginning after December 15, 2027.
• Build the budget from contract, asset, people and project inventories, plus an explicit contingency.
• Review variances monthly and present finance with options, total cost and timing.

Sources

• Internal Revenue Service, Publication 946: How To Depreciate Property (for 2025 returns)
• Internal Revenue Service, Tangible Property Final Regulations
• Financial Accounting Standards Board, ASU 2018-15: Customer's Accounting for Implementation Costs Incurred in a Cloud Computing Arrangement That Is a Service Contract (August 2018)
• Financial Accounting Standards Board, ASU 2025-06: Targeted Improvements to the Accounting for Internal-Use Software (September 2025)
• IFRS Foundation, Configuration or Customisation Costs in a Cloud Computing Arrangement (IAS 38), agenda decision (March 2021)